keutmann on Nostr: In most social media and messaging contexts, "mute" and "block" serve different ...
In most social media and messaging contexts, "mute" and "block" serve different purposes:
Mute: When you mute someone, you basically turn off the ability to hear from them in your feed or receive notifications. However, they can still see your posts, and you can still see theirs if you navigate to their profile. It's more of a one-way interaction limit.
Block: Blocking is more comprehensive. When you block someone, they can't see your posts, and you can't see theirs. Additionally, they can't message or interact with you in any way. It's a two-way interaction limit.
In the context of Nostr, NIP-51 defines a mute list, but I haven't come across a specific block list. Given Nostr's decentralized nature, truly blocking someone is impossible. Therefore, it makes little sense to implement a "block" feature in a client, as it essentially amounts to a mute function.
Mute: When you mute someone, you basically turn off the ability to hear from them in your feed or receive notifications. However, they can still see your posts, and you can still see theirs if you navigate to their profile. It's more of a one-way interaction limit.
Block: Blocking is more comprehensive. When you block someone, they can't see your posts, and you can't see theirs. Additionally, they can't message or interact with you in any way. It's a two-way interaction limit.
In the context of Nostr, NIP-51 defines a mute list, but I haven't come across a specific block list. Given Nostr's decentralized nature, truly blocking someone is impossible. Therefore, it makes little sense to implement a "block" feature in a client, as it essentially amounts to a mute function.