Trust, Moderation and the Fight Over Who Gets Seen
Nostr does not remove moderation. It moves the fight into clients, relays, lists, filters, web-of-trust systems and social judgment. That makes people more responsible for what they choose to see.
There is no moderation vacuum
People sometimes describe Nostr as if it has no moderation. That is not accurate. Nostr has no single moderation center. The difference is enormous. A platform can hide a post, suspend an account or tune an algorithm from one control room. Nostr spreads visibility choices across relays, clients, lists, user mutes, web-of-trust signals, paid relays, communities and indexing services. Moderation still exists. It is just harder to point at one boss.
This changes the People story. A person on Nostr may be visible in one client and buried in another. A relay may accept an event while another refuses it. A list may make a community usable for one group and exclusionary for another. A spam wave can turn a beautiful theory into a miserable product. The human question is not whether the network is free. It is how freedom is made livable.
Trust becomes social infrastructure
In a key-based network, identity is only the beginning. Trust comes from repeated public behavior, recognizable work, vouches, lists, conference presence, public evidence and the clients that choose which signals to surface. Web-of-trust ideas appear because people need shortcuts that are harder to game than follower counts. Mute lists and follow lists matter because they turn personal judgment into usable navigation.
The danger is that trust systems can harden into invisible gates. A newcomer may be real but unknown. A pseudonymous builder may have strong work but weak social proof. A critic may be muted for being annoying rather than wrong. The community has to keep asking whether trust tools help readers or simply protect insiders from discomfort.
Relays have politics even when they look technical
A relay is infrastructure, but relay policy is social power. What a relay accepts, stores, deletes, rate-limits or charges for affects who can speak and who can be found. Paid relays can reduce spam and create accountability. They can also raise barriers. Open relays can feel welcoming and become unusable. Specialized relays can create context and also fragment the room.
That is why relay operators belong near People. They may not seek public attention, but their decisions shape the community. A serious People map treats them as more than server admins. They are stewards of visibility.
The hard cases define the culture
Every open social network eventually faces abuse, impersonation, harassment, scams, political extremity, spam, coordinated attention games and boring bad behavior. Nostr faces those problems without a single company safety team. That can be liberating for people escaping censorship. It can be exhausting for people who just want a readable public space.
The community is still deciding how to answer. Some builders favor user control and web-of-trust. Some lean on relay policy. Some want better client defaults. Some want stronger community spaces. Some fear any moderation layer that becomes a disguised platform. These disagreements are not side drama. They are the civic life of the protocol.
Nostr has no king, so trust becomes a product problem
Nostr's moderation story is often misunderstood. The absence of a single platform moderator does not remove moderation. It moves the work into clients, relays, lists, communities, web-of-trust systems and personal choices. That makes trust a product problem and a People problem. Somebody has to decide which signals matter, which defaults protect users and which controls are visible enough to be used.
Coracle is one of the clearest examples because Hodlbod's work keeps returning to relay awareness, web-of-trust thinking and the idea that users should see more of the social machinery. wot.nostr.net and related relay experiments show another side: trust can be encoded into infrastructure, but then the reader has to ask who curates the graph and what kind of abuse the model catches or misses.
This is more interesting than the shallow question "does Nostr have moderation?" It has many moderation layers, and the argument is about where power should sit.
Spam, follows and mute lists are cultural architecture
A follow list is not just a list. A mute list is not just a preference. A relay policy is not just server configuration. In an open social network, those small choices become cultural architecture. They decide whether a new reader sees thoughtful conversation or spam, whether a creator can be found, whether a public figure gets impersonated, whether communities can protect themselves and whether client makers become accidental editors of public life.
The People map should name the people and projects working on that architecture without pretending there is one final answer. Some people want strong personal controls. Some want relay-level policy. Some want web-of-trust filtering. Some want paid relays. Some want open firehose clients and user responsibility. Nostr is alive because these approaches are being tested in public.
Trust and moderation are not cleanup work after the protocol. They are part of the protocol's social body.
What readers need from this debate
A reader does not need a perfect theory of moderation. They need to understand where visibility decisions happen and who is making them. If a person is prominent because a client surfaces them, that matters. If a relay keeps a community usable, that matters. If a list shapes discovery, that matters. If a critic exposes a weak trust model, that matters too.
The People hub becomes useful when it shows the people behind the trust layer: builders, relay operators, list makers, moderators, critics, educators and users who keep asking what kind of public square Nostr is becoming.
Sources worth opening
- NIP-51 - Lists, including public and private lists that shape discovery and curation.
- NIP-65 - Relay list metadata, important when checking whether an account is reachable.
- Nostr.org - Official protocol entry point and mental model for clients, relays and user-controlled identity.
- nostr.band - Search and discovery surface used for public account, profile and event lookup.
- Coracle - Relay-aware web client and social reading surface.
- Nostr Design - Community design resource for keys, relays, onboarding and product experience.
- ActivityPub W3C Recommendation - Reference point for comparing Nostr with federated social networking.
- Mastodon documentation - Product and server model reference for Mastodon.
- Coracle GitHub - Repository context for Coracle, relay management, web of trust and privacy protection.
- OpenSats Coracle project page - Funding and project context for Hodlbod, Coracle, relay management and web of trust.
- wot.nostr.net - Web-of-trust relay example powered by Khatru and Bitvora.





