Nostr Web Client

I guess censorship as a result of what a client dev decided is hard to solve for if all devs decide to do such a thing.

But why would any dev start to do such a thing in the first place? Why would users addopt it secondly? And subsequently, if the clients are opensource it would be trivial to fork take it out. And lastly you'd think there would be clients not doing such things out there.

Lastly:

Hardcoded censorsing on a client level is just bad tech btw, terrible way of doing things.

Say you have really good reasons to want to make sure your users dont get into contact with someone; blocking that person hardcoded in your client wont help your users in all their other clients.

a0x77ry 1y ago

"But why would any dev start to do such a thing in the first place?"

A hypothetical scenario: Because they believe that anyone who disagrees with their political beliefs is a Nazi and should be silenced

"Why would users addopt it secondly?"

Because they are the best clients technically, and these users do not really care about politics. They are just normal people who want to use social media.

Yes, you can fork the clients, but non-political people don't care enough to switch to your fork.

I'm not saying these things are happening right now. I'm just saying that a scenario similar to this is possible. There is nothing in the nostr protocol to prevent this. I really hope I'm wrong.

Reply to this note

Please Login to reply.

Discussion

Constant 1y ago

There is nothing in this world to prevent this other than coercion.

But your scenario is that selfsegregating people with a self segragating app/client will become dominant and popular? Maybe, also not really that impossible thinking about it. Then again, it is a large world and Nostr gives you all means possible to route around it if it happens; but when it happens it is a social phenomena, not a tech thing