The controversy landed this week in a relay thread that’s now circulating through developer channels. The accusation is blunt: “Nip09 is not implemented by most clients. It’s only relay implementations that are saving everybody by deleting records. Clients generally never delete records, it keeps showing until the user reinstalls the app”. For a protocol that sells itself on user control, that sentence is a quiet detonation.

The Catalyst: A Standard Nobody Follows

NIP-09 is Nostr’s Event Deletion Request standard. A user signs a kind 5 event that references a note they want removed, and relays that support the standard should stop serving the original event. The word “should” matters. The NIP is deliberately written as a request, not a guarantee. But the fresh allegation is that the client side is the real problem. Most clients, according to the thread, simply don’t purge deleted events from their local caches. The note disappears from your view only when you reinstall the app and the cache is rebuilt from relays that may or may not have honored the deletion.

The practical effect is ugly. A user deletes a note, sees it vanish, and assumes the job is done. But the note may still be sitting in the client’s database, and it may still be propagating through relay infrastructure that never received or never honored the kind 5 request. “NIP-09 deletion requests do not prove erasure,” a September analysis warned, and the current client behavior is making that warning look prophetic.

The Developer Blind Spot

In my experience covering protocol governance, this is the kind of gap that emerges when incentives drift away from the stated mission. Relays have a clearer incentive to honor NIP-09 because storage costs money. Clients have less pressure. A client that silently caches everything can show faster load times and smoother scrolling. A client that aggressively purges local data risks user complaints about missing notes. So the client ecosystem, taken as a whole, has drifted toward retention by default and deletion as a best-effort afterthought.

I think this is the most damaging kind of technical debt because it’s invisible to the user until it matters. You don’t notice a missing deletion protocol until you post something you regret, or until someone else posts something about you that you want gone. And by then, the replication has already happened. The outbox model debate from September was loud because it was about architecture. This NIP-09 gap is quieter, but it cuts at the same nerve. Nostr’s sovereignty story depends on users being able to make meaningful choices about their data. A delete button that doesn’t actually delete is worse than no delete button at all, because it creates a false sense of control.

The Culture War Nobody Asked For

The deletion gap is colliding with a separate controversy that broke this week around Bridgy Fed. The bridge service had Nostr and Farcaster support “nearly ready,” but the team decided not to launch it, citing “the organizational side of things (edit, and of values too)”. The comment thread immediately filled with speculation about Nostr’s culture. One commenter asked, “What’s up with the culture on Nostr?” and suggested the decision might be about not wanting to “accept conservatives”.

I’m not going to pretend I know the internal reasoning at Bridgy Fed. But the timing is telling. Nostr’s public narrative is about openness and censorship resistance. Its internal development culture, meanwhile, is being described by participants as fragmented and visionless. “Nostr, as a sum of its developers and visionaries, had this for a while. It doesn’t have it anymore,” one long-time participant wrote in the same relay thread that surfaced the NIP-09 problem. That’s the kind of quote that sticks.

BEAR and BULLISH Scenarios

BEARISH: The deletion gap persists because clients have no economic incentive to fix it. Users who assume deletion works continue to post sensitive content, and the protocol’s privacy reputation erodes with each high-profile failure. The culture-war noise around Bridgy Fed discourages bridge-builders from integrating, and Nostr remains a walled garden of ideological insiders.

BULLISH: Relays are already doing the heavy lifting by honoring NIP-09 and purging records. If a few major clients ship proper local cache purging in the next quarter, the gap closes without a protocol change. The Bridgy Fed decision, while controversial, forces a public conversation about values that Nostr has avoided for too long. A crisis of identity can produce clarity.

Summary

The NIP-09 client gap is the freshest self-inflicted wound in Nostr’s data sovereignty story. Relays are honoring deletion requests, but most clients are not, so users get a false sense of erasure. The Bridgy Fed controversy is a separate but related signal: Nostr’s development culture is being questioned from the inside and the outside at the same time. Until clients treat deletion as a first-class feature rather than a cosmetic convenience, every “deleted” note carries an asterisk. The protocol doesn’t need another NIP. It needs the people building clients to finish the ones that already exist.