This is a very interesting article about the long-term sustainability of the Fediverse for moderators, administrators, and developers. We’ve already had two of our lovely Beehaw admins take breaks to take care of themselves as they experience the burnout associated with maintaining a community, and I think for a lot of use we already know how exhausting it can be to take a center stage position in an online community.

Unfortunately, I don’t have any great starting points for what to do, but at least talking about it is a start.

  •  Arotrios   ( @Arotrios@kbin.social ) 
    link
    fedilink
    41
    edit-2
    11 months ago

    Speaking as someone who ran a set of public forums back in the early days of the internet, the number one thing I can suggest is don’t do it alone.

    Alone, you’re one person arguing with hundreds of other people that your opinion is the right one. This burns out anyone but the most narcissistic assholes (I should know, being the latter). With a team, you get to deflect attacks that would be personally directed at you to the overall team while relying on their support to provide a unified front. Bullies generally target single individuals - they rarely go after groups.

    This can be hard to build, and it often relies on a third party in the admin role to encourage the creation and unity of the mod team until it gets on its feet, often becoming part of the team in the early phases until it runs well on its own. A minimum of three people is usually what it takes to really make a community thrive cleanly.

    Unfortunately, the fragmented nature of the Fediverse makes it difficult to build these kind of teams, as the mods have to be users on the same instance platform, and a small instance with only 20 users can end up with an enormous amount of content and commentary from users across the wider Fediverse. This, of course, ties into @hoodlem 's comment regarding bandwidth costs for instance owners - the speed at which your traffic can scale is exponential, and you need to be prepared for it from both a financial and staffing standpoint.

    One solutions that could help would be to have an ActivityPub login standard that would allow logged-in users from one instance to moderate a community on another when given permissions. A cross-platform private messaging standard would help here as well. Of course, both of these functions would have to be encrypted and secured to prevent cross-site attacks, but they could be steps in unifying the Fediverse without centralizing it.

    EDIT: as pointed out in the comments, you can mod across instances, but it doesn’t look like you can mod across platforms yet.

    • One solutions that could help would be to have an ActivityPub login standard that would allow logged-in users from one instance to moderate a community on another when given permissions.

      That’s already possible on lemmy. Not sure about kbin.

      • That’s pretty cool - I wasn’t aware of that functionality - makes me want to investigate further. I’m wondering if the basis for the function is within the ActivityPub protocol, or if it’s a function built into the Lemmy code.

    • Unfortunately, the fragmented nature of the Fediverse makes it difficult to build these kind of teams, as the mods have to be users on the same instance

      No they don’t. As long as the instances are federated then you can moderate a community on another instance. I’ve set up communities on my home instance for other people to mod and I mod a few lemmy.world ones.