Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
mekka okereke :verified:
@mekkaokereke@hachyderm.io  ·  activity timestamp yesterday

@mike @rapscalorie @me

There is more than just a *possibility* that shared blocklist will be weaponized. It's as close to a certainty as we can get. And the weaponization of blocklists are paradoxically most often targeted at marginalized people. 🤷🏿‍♂️

Because of this, some very smart people oppose shared blocklists. The people that oppose blocklists are not irrational or selfish or uniformed. I just happen to disagree with them.

Because there are more choices than:
a) No blocklists
b) Blocklists that people agree to without thought

BlueSky has shared Blocklists. I've been the target of weaponized blocklists over there. Happens. One example: Inauthentic accounts pretending to be trans, got me added to a transphobes list. I was on that list for a few months. Then a real trans person with moderation experience saw what was going on, and got me off of the list. ♥️👍🏿

I've also been added to blocklists by good faith people that were confused. A Ukrainian person didn't understand that I have a bunch of Ukrainian relatives, and thought that I was disparaging Ukrainian drone units by saying that most of the casualties caused by Ukraine were by artillery. They are. I got added to an "Americans that don't care about Ukraine" or some such list. I think I'm still there. Similar happened when I said that my Haitian friends should be granted asylum from war the same as my Ukrainian friends.

I still support shared blocklists, because the benefit outweighs the harms, and many of the risks can be mitigated. And right now, it is way too hard and too expensive in terms of time, for a small Fediverse instance to be well moderated.

A bunch of government accounts joined BlueSky, and many users just subscribed to blocklists that included them. They're now the most blocked accounts on BlueSky. 🤷🏿‍♂️

https://clearsky.app

Click blocked > Top blocked

  • Copy link
  • Flag this post
  • Block
Ⓐ Dirk Ritter
@GNUmatic@deppenkessel.de replied  ·  activity timestamp 3 hours ago

@mekkaokereke

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.

  • Copy link
  • Flag this comment
  • Block
Ben Ford :grinchsmile:
@binford2k@hachyderm.io replied  ·  activity timestamp 19 hours ago

@mekkaokereke oh fun. The only person blocking me there is the second most prolific blocker. 😂

  • Copy link
  • Flag this comment
  • Block
flaeky pancako
@fleeky@prsm.space replied  ·  activity timestamp 23 hours ago

@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 ..

  • Copy link
  • Flag this comment
  • Block
mekka okereke :verified:
@mekkaokereke@hachyderm.io replied  ·  activity timestamp 21 hours ago

@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.

  • Copy link
  • Flag this comment
  • Block
Mike Fraser :Jets: :flag:
@mike@thecanadian.social replied  ·  activity timestamp 21 hours ago

@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.

  • Copy link
  • Flag this comment
  • Block
Greg Lloyd
@Roundtrip@federate.social replied  ·  activity timestamp 19 hours ago

@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

  • Copy link
  • Flag this comment
  • Block
Greg Lloyd
@Roundtrip@federate.social replied  ·  activity timestamp 18 hours ago

@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…

#fediverse #blocklist #moderation #github

  • Copy link
  • Flag this comment
  • Block
Greg Lloyd
@Roundtrip@federate.social replied  ·  activity timestamp 18 hours ago

@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…

#fediverse #blocklist #moderation

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.3.21 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login