This confused person doesn't understand what Nostr is about.
Especially the "clients" part.
Discussion
There is a lot of baiting going on here lately.
What about clients do you mean?
Clients can and do filter which people can benefit from it if they choose to.
Also, I wouldn’t think someone like Rabble leading a team creating a client is confused about how clients works.
There aren't two ways of understanding what he said, the context makes it very clear.
He is saying that clients should be capable of censoring "unacceptable" (according to whom?) content. He didn't say "the user by configuring the client" or something of the kind, he said "the client" (i.e. the client's developer).
This has already been tried by some fediverse clients that used to come with predefined blacklists in their code.
Such practice is in direct opposition to Nostr's philosophy.
If he's not confused, then he's openly trying to destroy Nostr.
I disagree completely and I’m not trying to destroy nostr.
In fact, I believe Nostr can succeed because of it.
A user configures their experience by choosing a client, a relay, or their configuration.
Clients and relays can do whatever they want - nobody can stop them with nostrs current framework.
To be blunt - this exactly the type of freedom that makes the internet and its clients work.
Nobody is surprised when they launch the Spotify app or website and it doesn’t show content from yahoo.com.
I primarily browse Nostr via global (firehose). It is a complete mess. This stuff has to be tuned and nobody has to ask permission to do it with Nostr.
Wrong.
Global is global, it is meant to be that way.
Whatever you do to it in order to "tune it" makes it something else.
You are indeed lying to the user if you call it "global".
Put a warning on it if you wish, but don't take it away, it's up to the user to see it or not.
I never said someone had to “tune” global and still call it “global”.
Whoever floats your boat but in my mind there’s no sense trying to tell others what Nostr is or is not when there’s nothing about it that stops anyone from deciding on their own.
As I see it this will lead to a scenario where there are two classes of Nostr, one with censorship enabled and the "free-speech clients".
Much like KYC BTC and non-KYC BTC, and eventually they will break compatibility.
This already happened to the Fediverse and it's why it failed.
I disagree but am thrilled to hear others thoughts.
Take care.