Nostr itself doesn't, but popular clients implementing opt-out filters labeled as merely "spam filters" and then arguing in bad faith when called out on it sends a message a supposedly "censorship-resistant" protocol shouldn't be advocating for.

There's a reason I'm not using Amethyst anymore, as I also ceased using it during the Onyx fork era.

Reply to this note

Please Login to reply.

Discussion

But this is highlighting the censorship resistance of Nostr. If one client does something you don't like or one relay does something you don't like, you have a plethora of other choices. X does not have different choices to post signal.me links. That's the difference. I know you get that.

A decentralized design is better than a wholly centralized one, definitely. The issue arises when it morphs into a cat and mouse game; ambivalent clients and/or relays starting to censor what they consider "undesired" users, others gradually becoming more restrictive, etc.

Nostr client and relay maintainers seem hellbent on doing everything wrong with the fediverse, but on a far worse scale. The point isn't that you can't fuck off and use something else, but pondering how long until you'll no longer be able to do that.

I didn't leave the fediverse just to end up with an experience worse than it.

some clients are going to be better and more popular than thoughts. and it's absolutely possible that those more popular clients may do things that you do not like or approve wholly of, but again, by design you have a choice to not follow suit if you do not want to do so. you say you don't want an experience worse than the fediverse, but on the fediverse you really don't have a whole lot of choices. it's not as censorship resistant as nostr.

i don't think muting is censorship. i don't think they're even remotely related.

I'll just say that making one change would eradicate the censorship claims overnight, and it's something I discussed with Verita directly.

Just make the filters opt-in, and not opt-OUT; make it something new Nostr users can leave off or enable during onboarding, and explain clearly exactly what it does, rather than pretending it's something that it isn't.