A good example is https://lemmy.world/c/documentaries

One of their mods, https://lemmy.world/u/sabbah, currently mods 54 communites despite only being on Lemmy for about a month and has never posted on c/documentaries (except for his post asking for people to join his mod team).

The other mod, https://lemmy.world/u/AradFort, has one post to c/documentaries and moderates 18 communities.

Does Lemmy.World have a plan to remove this kind of cancer before we start getting reddit supermods here too?

Edit: This comment shows how this is even more dangerous than I had thought.

Edit2: Official answer from LW admin is here

Final: Was going to create an issue for this on the Lemmy github, but I browsed for awhile and found that it had already been done. If anyone wants to continue the discussion there, here it is - https://github.com/LemmyNet/lemmy/issues/3452

Perhap we need another issue for the problem in the original edit (It being impossible currently to remove a ‘founding’ mod without destroying either the community of their account)

  • theneverfox@pawb.social
    link
    fedilink
    arrow-up
    8
    ·
    1 year ago

    Ok, I think you have a point. But where do you draw the line?

    IMO, it shouldn’t be a hard limit - that’s asking the dev team to deal with arguments on the topic indefinitely.

    I think per-instance limits make more sense in the short term, but that still just mitigates the reason not to do it, it doesn’t solve it.

    Ultimately, I think we should experiment with novel strategies, such as various democratic spins on moderation that decentralize authority. The fediverse is all about decentralization and trying stuff without missing out on the larger network after all.

    You seem passionate and you have a solid argument - you should post an issue on the GitHub. This shouldn’t be hard to actually implement - the majority of the work on this one is convincing everyone this should be done and what the rules should be

    • genoxidedev1@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I agree that a global hard-limit is problematic since every instance (admin) will want it to be how they see it, of course.

      A per-instance limit was what I had in mind (not originally, this point has come up before because of the user I mentioned in my last paragraph and someone convinced me; There also already is an issue regarding that or something similar as far as I remember and I gave my opinion on it in a reply).

      I think in that sense we both agree, it should be per-instance, and as you mentioned, the fediverse is all about decentralization, which is why I think something should be done about it.
      And I think unless we have further methods to maintain decentralized moderation, this hardlimit (per-instance) is the first step, or at least a step, in the necessary direction.
      Best case scenario, we’ll get other methods of maintaining decentralized moderation and get rid of the softlimit (?) later down the line.

      Of course democratic spins like subscribers voting mods every now and then would be an interesting solution (that opens up new problems, of course, but that comes with every solution).

      Hope my ADHD didn’t hurt the readability.

      • theneverfox@pawb.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Haha no worries, I too think in webs, I found it pretty clear. Talking to other people with ADHD is so much more straightforward

        I’m convinced on your approach (at least until someone comes out with a more elegant way to handle it), I’m focusing on the client side for now, but if this is still an open issue in a month or two I’ll consider writing it myself. It’d be a good ticket to shake off the rust in Rust

        My thoughts on democratization go further than that - when Reddit made their disingenuous democracy pitch, I started to think what that would actually mean

        My thought is something like, everyone is invited to be a mod, or random members are asked to do an hour of mod work. They go through and do mod work, but everything requires corroboration

        In my approach, you’d have to look at every mod action, then decide if it defaults to action or inaction. Then you use some basic statistics to come up with numbers to pass or reject an action based on how many mod actions your community clears per Capita.

        I plan to look at it down the road…I don’t know nearly enough about modding to say I’ve got a fully formed approach, but I think there’s something there. I plan to ask some admins if I can do a short stint as a mod in order to better understand what it’s like, and then I want to look at this.

        I also have this idea of a “mitosis” operation to split a community when the mods feel it’s grown beyond them and they’re losing control… Fomo makes the idea controversial, but i generally find small communities better than large ones in every way. Maybe by pairing this with some version of the “multi” idea a lot of people are pushing we might find a happy middle ground