Replying to Avatar CappyNate🍁

That's cult response.

There's nothing wrong with muting. Muting is excellent. P2P muting.

The second you add batch muting and private muting, the game changes entirely. A function can now be weaponized without anyone knowing. Creating a shadowban effect with no way of stopping it.

All mutes should be public. And a mute monitoring service should be paramount to ensure batch muting isn't being weaponized. This can only be done publicly.

If every Bitcoin financial transaction can be public, every Nostr event can be too.
Avatar
jb55 1y ago

this is why we’re not adding batch muting, but of course any client can and users can use those clients if they like. free market gonna free market. I don’t understand your argument against private mutelists though as they ameliorate the situation you’re describing.

Reply to this note

Please Login to reply.

Discussion

Avatar
CappyNate🍁 1y ago

Good that you aren't. As you mention, others will.

Batch muting will occur regardless. It can't be stopped. The key fight against it is being able to see it occurring. To expose + address.

The second we can't see it (private), we're hooped.

I just put a post up, feel free to attack it. This definitely isn't a client-side or Damus issue, so not directed at you. Seems like a protocol-wide issue.

Avatar
jb55 1y ago

You can definitely see it. Just send the same note to multiple public relays and see which ones reject the note. Relays can’t use private mute lists so your concern doesn’t make any sense.

It sounds like you are conflating individuals private mute lists with private relay mutelists, they are not the same thing. The latter is easy to detect.