this post was submitted on 17 Jun 2023
3 points (100.0% liked)

/kbin meta

639 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
3
Moderate by lottery? (kbin.social)
submitted 1 year ago by [email protected] to c/[email protected]
19 comments fedilink hide all child comments
 

So this is a half formed idea that might be horrible, I thought I'd throw it out there for critique.

  • We have a problem on Kbin.social and probably other instances of under staffed moderation & admin teams.
  • Some large magazines have a single moderator
  • This will soon lead to *bad-shit appearing here
  • We will likely get de-federated at some point

A random selection of peers is good enough for juries. So how about we apply it here?

Every ~100th new user is made a site wide Admin (cannot delete only unpublish content, it remains visible in the backend to other mods)

Every ~100th new Magazine subscriber is similarly made a mod of that space.

A few would go powertripping, many would be inactive, but I think it might build the mod/admin team in a reasonable way.

We have to build the processes for powertripping/inactive admins anyway, so in a sense it's not extra work.

You'd build in some randomness, so the system was harder to game, it wouldn't literally be the 100th person. It might be the 80th, or 110th, but averaging out at ~100

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago

This is how you get bad actors spamming new accounts. But a better idea might be to have a central location for trusted moderators to convene and for overwhelmed mods to request short-term assistance modding, until they can find long-term help from within their own communities.

How to find trusted moderators is a bit hard this early on in kbin's life, it would have to be done based on early comments & perhaps contributions to the issue tracker / the repo itself. Or maybe proof via Discord and/or reddit of good faith.

That said, so far the problem I see seems to be too little content, not anything overrun with bots, so these ideas seem to be solutions in search of a problem, at least thus far.