this post was submitted on 15 Jun 2023
46 points (100.0% liked)
Fediverse
12 readers
1 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's because they defederated from the two largest competing instances. I'm talking about the communities users not the instances. The issue is that beehaw has the largest and therefore defacto default communities. The timing is bad and will likely affect wider adoption. The biggest problem is that it is entirely foreseeable and solved by either accepting a smaller community (closing signups) or improving moderation capabilities (getting more moderators or investing in an alternative moderation system) before it meant splitting the threadiverse in half.
I'm not denying that it sucks, but if you'd told anybody this was going to happen a month ago they'd have just laughed at you. Of course they were unprepared. Everbody has more than they can deal with. Adding more mods isn't as simple as picking some names out of a hat, and this isn't a thing anyone was preparing for. There currently are no alternative moderation systems, everything is too new and until recently was all way to small for that to be important, and they just have more work then they can deal with trying to suddenly moderate all of the threadiverse.
This was a bad option that sucked, but every option was a bad option that sucked. I'm more concerned with how they deal with things as they normalize over the coming weeks and months than I am with how they're trying to put out the fires in the short term.
But they chose a nonstandard moderation strategy that limited their ability to scale moderation with users. The default system is that communities are moderated independently of admins (not saying admins don't form communities or that there's no overlap between admins and mods) whereas on beehaw only the admins can create communities and therefore are the primary moderators.
Now I'm not saying that there's anything inherently wrong with the system they've chosen but the fact that it is nonstandard and in fact built into the core precept of beehaw means that this was easily foreseen.
Easily forseen if you knew that lemmy was suddenly going to have a hundred times as many users in the space of a couple weeks. That was the thing no one was prepared for though.
A couple of weeks is more than enough time to realize where things were headed and act. lemmy.ml managed to do it.
lemmy.ml has a completely different idea of how it wants to be run. That happens to have been hurt a lot less by a sudden massive influx of new users, but that wasn't the reason it was different. What do you even think beehaw could have done that would have better given their goals?