I think we need to update the NIP’s so that relays respect blocks and don’t server messages from the blocker to the blocked.

Reply to this note

Please Login to reply.

Discussion

I don’t think there’s any point to that. Notes are public, and the blocked user would be able to get around the block with a new key. In fact, he could put the blocker’s public key into a client and get a read-only view of Nostr from the blocker’s perspective.

A read-only view minus the blocker’s direct messages, of course.

What would this accomplish? And why users would want that?

Agreed.

I think this is against nostr spirit, you are enabling censorship on the relay level now.

I think clients hiding the posts of the person you are blocking is a good measure, since the user has the choice to see or not the notes of the person he’s blocking

People should have the right to choose who they want to talk to and who they don’t.

I fully support that, you are judging that the block/mute feature on the client level is not enough ?

Only individual client side. Otherwise we are recreating fediverse

Free Speech is put in the hands of those who are giving it.

And it doesn’t come at a price, but at the same time, it’s nearly priceless.

The critical difference is the fediverse has blocks between servers. A server owns and controls all users and content. You can’t trust a fediverse server to act on your behalf. They can change who you follow or what you see.

In Nostr because we use multiple relays and the content is signed by users who control their own content and social graph the power dynamic is flipped.

I as a user, can choose to use relays that will respect my block messages to not show my posts to Joe stalker, or I could use a relay that will share my posts. If a relay goes ‘evil’ and stops following our agreement, I can easily move all of my content to another relay.

Agency and autonomy matter. If you don’t like relays that enforce blocks, don’t use them, run a really that follows different rules.

I think we need more information from relays about how they’re run, who’s running them, what nips they implement, and what their rules are. That way we can all make informed choices about which ones we want to use.

I agree. We have NIP-11 and the additional fields that were recently merged. We also have our website and readme/docs. What else should we provide as relay operators and where?

Critical difference indeed.

Woah, the movement on this is amazing… did not know that about the internet.

As long as as individuals block list doesn't dictate the experience for others I'm good with it. Have seen a couple of accounts still carrying block warnings on all their posts, not just the "inappropriate" ones

I’m not sure this is practical or possible. REQs aren’t tied to pubkeys (unless the client is authenticated). Even if they were, what’s to stop the blocked user from making a new pubkey?