fiatjaf on Nostr: The Nostr strategy from the start was to have many clients -- none of which are the ...

The Nostr strategy from the start was to have many clients -- none of which are the "official" client -- such that the threat of one client hardcoding banlists is mitigated. Of course that could always happen and is probably the hardest part, but assuming a relatively diverse ecosystem of apps it gets harder for one app to comply with such ban requests as there will always be alternatives for users to jump to (and with different clients having different approaches to Nostr it makes sense for users to experiment with more than one as time goes by even if none censor). Also no country has ever tried to force web browsers into compliance, and Nostr client are just like web browsers, so we have that on our side.

Censoring relays, either by DNS or by asking the relays directly, absolutely doesn't work because it's in the direct interest of the person being censored to move to other relays and all clients, as long as they're doing Nostr right (i.e. implementing the "outbox model" for basic feeds), will find that person. See https://how-nostr-works.pages.dev/#/outbox for an example.

Media server censorship is solved by Blossom the same way the outbox model solves relay censorship. You signal that your media is in another server, clients can adapt and use that.