Post
@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…
Biggest gripes with defederation block lists? Aside from a modest starter package we imported, it's just tedious work, because there's never a clear definition of what is blocked and why exactly, so you can't just blindly go for it.
Splitting it up into clearly defined categories would help, at least. Probably some shit holes would show up on multiple lists for all sorts of reasons, but that would be the least of my concern, because you can only block each domain once anyway.
@mekkaokereke oh fun. The only person blocking me there is the second most prolific blocker. 😂
@mekkaokereke @mike @rapscalorie @me this has been percolating in my head for a while , we need something better than a person who knows you luckily being a moderator ..
got to be a better idea than this but it seems like we could use a blocklist judiciary ??
what happens with shared blocklists when the data is contradictory and the moderators curating those lists disagree ?
mind you i think the concerns i have are not immediately important , so maybe not even worth thinking about ..
@fleeky @mike @rapscalorie @me
No, your questions are immediately important and spot on! 👍🏿
Creating a blocklist process is not as interesting or difficult or as important as defining the appeals process, or the mechanism whereby something can get off the blocklist.
@mekkaokereke @fleeky @rapscalorie @me I think there has been some work done in this area already. It feels like I've been in a conversation like this previously.
@mike @mekkaokereke @fleeky @rapscalorie @me
Slashdot-style distributed content moderation / Karma might also be applied to blocklist arbitration:
‘Slash(dot) and Burn: Distributed Moderation in a Large Online Conversation Space’
Cliff Lampe, Paul Resnick
School of Information University of Michigan
(2004 preprint of a ACM CHI 2004 paper)
#fediverse #blocklist #moderation
http://www.presnick.people.si.umich.edu/papers/chi04/LampeResnick.pdf
@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…
A space for Bonfire maintainers and contributors to communicate
