There are two items that can help based on the discussion a couple weeks ago: 1. If someone is harassing a user it is not enough to mute that user bc they are still in the replies. In some cases the harasser’s friends are seeing the replies and piling on. However the person being harassed doesn’t know the harassment is continuing and then is blindsided by the additional harassment coming their way. Freedom from needs to extend to freedom from having someone in your replies continuing to harass you. The current model assumes Nostr is a level playing field that exists in a cultural vacuum and that is not the case. As a result those who experience harassment IRL also feel the brunt of it here. Direct harassment is different from saying whatever you want. It involves being in someone’s replies or mentioning them directly. People need the ability to say no to both of these. 2. The second issue women reported was being found by random jerks. This happens bc some apps have aggregator feeds. Users need the option to opt out of these. I also think there’s more user research needed to understand if other problems exist.

One other thing I forgot to mention is that across Nostr we are not implementing mutes the same way. If I mute someone on Nos, they are not muted on Damus. I’m not sure how often people use different clients, but it would be good to have mutes work across the network as a starting point.

Good point - how do yall implement mute on Nos? I dont think currently damus imports / checks for mute lists generated on other clients - @Daniel D’Aquino lmk if I am wrong. This should be added. Checking backlog.

@elsat, I am not 100% familiar with the details of mute-lists, but I believe they are often stored in a special kind of Nostr event, so it should be generally interoperable, but yeah, there might be some specific detail that is causing this issue