Interesting bit of news for the threadiverse. All three of these are fairly large lemmy instances

You are viewing a single thread.
View all comments View context
1 point

I do think it’s fair to criticize the decision to try to be one of the largest instances while only having four moderators. They should have accepted a place as a midsize instance with midsize communities in order to maintain their moderation goals. Or they could have worked to get more moderators. Blaming the defederated instances and mod tools seem disingenuous at best. That said mod tools undoubtedly need improvement.

permalink
report
parent
reply
3 points

To be fair, they said the reason they were defederating from those two instances in particular is because most of their moderation involved people from them. They didn’t expand beehaw beyond what they could handle, the rest of lemmy expanded beyond what they could handle. If this really is just a temporary measure, which is also what they said, then I think it’s pretty reasonable.

permalink
report
parent
reply
1 point
*

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.

permalink
report
parent
reply
3 points

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.

permalink
report
parent
reply
1 point
*

The admins have always been clear that they’re not trying to replace Reddit, and I’m quite sure they were not trying to be one of the largest instances.

If they weren’t trying to get large then how did that happen? Based on admin comments, beehaw was one of the more active instances when the first wave of migration happened; and a decent amount of the pre-first wave posts about lemmy I saw on Reddit were about how Beehaw was a good instance to join as it was defederated from lemmygrad.

permalink
report
parent
reply
0 points

I’m not saying this has anything to do with replacing reddit but it is bad for the larger threadiverse community. Notably there were several other instances that closed registration for the purposes of not growing quicker than they could handle long term (see lemmy.ml). Beehaw has most of the largest (and therefore defacto default) communities. Active steps to avoid that would have allowed them to maintain their moderation goals while growing in an organic and sustainable way that benefits the larger threadiverse community.

permalink
report
parent
reply
0 points

I was strictly replying to the part of your comment where you said they made a decision to try to be one of the largest instances – imo they did not make a explicit decision to try to be that, but rather the growth was a side effect of the circumstances around reddit users checking out the fediverse.

Is closing registrations is better than having an application with questions that weed out low-effort users? IMO it’s probably a wash. beehaw has only banned one user from the local instance that I know of, so the application process seems to be working overall. The issue is that other instances are growing too quickly and needing to moderate those users, not their own.

I do agree this isn’t great for the threadiverse and I wish it hadn’t come to this, both on a personal and community level. I was subbed to the knitting community on lemmy.world, it was the most active of those communities that I saw, and now I’m locked out. Idk if I want to move to an alt on a different instance, or self-host my own so that I’m fully in control of what I can see, or what. :S

permalink
report
parent
reply

Fediverse

!fediverse@kbin.social

Create post

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.

Community stats

  • 3

    Monthly active users

  • 680

    Posts

  • 3.9K

    Comments

Community moderators