@mike @mekkaokereke @fleeky @rapscalorie @me
Another approach would be to publish and manage each Communal Blocklist that aims to gain a wide following as a GitHub-like project, with discussion, proposals, and deliberative approval of small — or large — batches of blocklist changes. This would make it possible for a blocklist to maintain a public reputation for fairness, prompt action, and topic focus. Change volume would likely be a challenge…
@mike @mekkaokereke @fleeky @rapscalorie @me
Maybe a better approach would be a way for a Fediverse server to be able to nominate and mark itself as as “Shared Blocklist” source, then host discussion of moderation decisions, and share its current net Blocklist. It would need a TBD simple and efficient way for each Shared Blocklist server to periodically accept or reject proposed changes from Shared Blocklist servers *it* references…