Community

Governance

Moderation Without One King

Nostr does not remove moderation. It moves moderation into clients, relays, communities, lists and public signals you can inspect or leave.

A focused table discussion about standards, membership and project rules.

Moderation

The question is not whether moderation exists.

Every social network moderates. The honest question is where the power sits, who can inspect it and whether you can leave without losing your identity. Nostr is interesting because it splits moderation across layers instead of giving one company the whole lever.

A relay may refuse spam. A client may hide violent images or phishing links. A community may enforce room rules. A person may mute accounts, follow a web-of-trust list or ignore reports from issuers they do not trust. None of those choices is neutral. The difference is that the choice can be visible and replaceable.

Relay policy is infrastructure governance

Relays are allowed to say no. That matters. A relay that accepts every event without rate limits quickly becomes expensive and abusive. A relay that rejects too aggressively can erase important edge cases from its own view of the network. The governance question is whether the policy is legible: what kinds are accepted, whether authentication is required, how reports are handled and whether an operator can be contacted.

This is where NIP-11 metadata, relay policies and operator reputation become more than technical footnotes. If you depend on a relay for community memory, publishing or moderation, the operator's choices shape your experience. Nostr keeps your key portable, but a bad relay choice can still make a room feel broken.

A governance scene where documentation and accountability keep trust legible.
A Nostr badge and membership status visual for reputation and public context.
A focused table discussion about standards, membership and project rules.
A governance team working through operational decisions.
Project and partner discussion connected to a governance layer.

Client moderation is product governance

A client turns signed events into a living surface. It decides ranking, hiding, muting, previews, search, reports, warning labels and default relay sets. Two clients can read the same network and feel like different cities. That is power, and it should be treated as power.

The healthier pattern is transparency. Tell people when a post is hidden by local settings, by a mute list, by a report threshold or by a community rule. Give enough context to change the setting, inspect the source or open the event elsewhere. Do not turn open-protocol data into a new black box.

Public conflict needs friction

Open networks create public feuds faster than they create institutions. Screenshots travel, accusations harden and people demand instant verdicts. Nostr can make that worse if clients reward spectacle without context. It can make it better if reports, labels, replies, badges and community rules stay attached to the actual events.

A good governance page does not launder gossip into certainty. It distinguishes between an event, a claim about an event, a report, a label, a moderator action and a community decision. That sounds fussy until someone's reputation, safety or livelihood is on the line.

A focused table discussion about standards, membership and project rules.
A governance team working through operational decisions.
Project and partner discussion connected to a governance layer.
Partners discussing standards and project execution.
Members preparing a public decision with rules, records and accountability.

Exit is necessary, not sufficient

The ability to switch clients or relays is a real freedom, but it is not a complete safety system. People still need moderation tools, abuse filters, block lists, trusted relays, community norms and legal routes when harm becomes serious. Nostr's promise is not a world without judgment. It is a world where judgment is not monopolized by one company account.

Sources