Subnostr

It would more or less follow the principles of DIP-01 (a list managed by your WoT, which means distinct lists for distinct users) and DIP-02 (based on explicit attestations instead of scraped data). I can’t think of any existing feature of any existing client that does that. (Except for my WoT-generated relays list, sorta.)

https://github.com/wds4/DCoSL/tree/main/dips/coreProtocol

captain ☦️ 2y ago

What's your understanding of the difference in meaning between a mute and a report event?

Reply to this note

Please Login to reply.

Discussion

david 2y ago

I’ve never used report event so I’m not sure. I guess it depends on who the event gets reported to and what gets done with it. Is it a developer-curated mute list that applies to everyone using that client? Or get passed along to relays and they use it to blacklist bad actors?

captain ☦️ 2y ago

It's a public event, anyone can create and publish, and relays and clients are free to interpret how they see fit

david 2y ago

I wouldn’t be surprised if relays are manually curating mute lists and using event reports to help them.

Centralized manual curation of something that yearns for decentralized curation. A losing proposition. Like in the last season of Halt and Catch Fire (they were trying to curate the web manually, pre-Google.)