What would you say about scraping a list of everyone muted by your follows (nip-51) and auto muting anyone who’s muted by some threshold number of them?
nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg desperately needs block/mute given the surge of spammers.
Discussion
I'd definitely use that if I had a ready means of flipping this off and on.
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.)
What's your understanding of the difference in meaning between a mute and a report event?
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?
It's a public event, anyone can create and publish, and relays and clients are free to interpret how they see fit
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.)