Nostr Web Client

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.

elsat 1y ago 💬 4

Good point - how do yall implement mute on Nos?

I dont think currently damus imports / checks for mute lists generated on other clients - nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 lmk if I am wrong.

This should be added. Checking backlog.

Reply to this note

Please Login to reply.

Discussion

Daniel D’Aquino 1y ago

nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5, 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

Matt Lorentz 1y ago

I think Damus is still using the old kind 30000 mute list which has been deprecated and everyone is standardizing on 10000. We are using 10000 in Nos. See https://github.com/nostr-protocol/nips/blob/master/51.md#deprecated-standard-lists

jb55 1y ago 💬 3

we have 10000 on TestFlight, do you do encrypted mutes?

elsat 1y ago

Damus 1.9 imports muted list from nos without trouble

https://github.com/damus-io/damus/issues/2155