The issue with censorship has never been about hosting your content.

Since the 90s anyone can run their own web server and host whatever content they wanted.

If you were banned from Twitter there was a bunch of platforms ready for you to post your content to.

The problem is if people will actually find and see your content.

Everyone post to Twitter because they have a chance of being seen. You post to other less popular platform and nobody will find you.

That’s where the censorship is relevant. Twitter might not ban you, but you don’t show up on people’s feed. I don’t see what I think is relevant but what somebody else decides is relevant for me.

When I point out Nostr doesn’t actually solve this problem people accuse me of wanting to force others to see my content.

Makes zero sense, but happens again and again.

Reply to this note

Please Login to reply.

Discussion

How do you think Nostr could be improved to fix this?

I don’t think it’s a matter of fixing the code.

We need a novel protocol distinct from Nostr, though once such protocol exists it might be possible to use it as a transport layer for Nostr.

I’m working on a candidate solution.

But we we’ll have to wait and see if it actually works — and if it is adopted by any significant number of people.

That is if I actually get around implementing and publishing it.