Discussion
Loading...

Discussion

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Mike Fraser :Jets: :flag:
@mike@thecanadian.social  ·  activity timestamp 16 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 post
  • Block
Ben Ford :grinchsmile:
@binford2k@hachyderm.io replied  ·  activity timestamp 13 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 17 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 16 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 16 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 14 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 13 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 12 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