Participation carries obligations
A node operator chooses to participate. Participation requires performing the work assigned under the protocol and meeting its requirements for availability, software compatibility, and integrity. The role does not grant permission to substitute the operator’s personal content preferences for those requirements.
Refusing required work or tampering with records is a failure to meet those obligations. The protocol’s evidence and accountability mechanisms determine consequences for standing, future assignments, and credits.
Avoid dependence on one operator
Bigfoot is designed to distribute service across participants and reassign eligible work when an assigned participant fails. A broad population of capable operators reduces dependence on any particular machine. Maintaining availability and enforcing the rules are necessary for that design to work in practice.
An operator’s ability to stop running software is not editorial authority over the public network. The relevant question is whether the remaining participants can carry out the required work according to the protocol.
Network rules and personal choices
A record must meet the protocol’s requirements. Those checks do not establish that its information is true or that its author is trustworthy. Content appearing through Bigfoot does not imply endorsement by Soliton Group LLC.
Readers can decide what to read and how to evaluate it. Choosing a personal view is different from altering records or refusing duties assigned to a network operator. Keeping those responsibilities separate supports a shared public record without requiring one editorial view for everyone.