- cross-posted to:
- news@beehaw.org
- cross-posted to:
- news@beehaw.org
cross-posted from: https://beehaw.org/post/628792
From the article:
"Beehaw is relatively new and relatively small at the moment, but it’s one of the closest approximations of what Reddit is that you’re going to find, and well worth investigating as a Reddit replacement. The interface even looks a lot like Reddit, albeit without a lot of the on-screen features and furniture that build up over almost two decades of operation.
Have a read of the Beehaw mission statement and you’ll see the platform is committed to avoiding the “hate speech” and “disinformation” that’s prevalent elsewhere. The communities available right now cover everything from neurodivergence and people of color to literature and gardening, so you’re sure to find something of interest here."
When the vast majority of the total moderation actions performed by an instance is against the users on just two external instances, there’s clearly a problem with those instances. It’s completely reasonable to greatly reduce the amount of moderation you have to do by shutting off the source of the problem.
Guilt by association is a real thing and it’s often justifiable if you are in that association by choice. Hang out with Nazis if you want, but don’t complain when you get grouped in with them by everyone else.
@RoboRay@kbin.social the fact you have an account on lemmy.world you opened 10 days ago before Beehaw defederated it is quite ironic. They literally only defederated lemmy.world because of the massive influx of new users from Reddit and the open enrollment. There was no moderation to be performed as far as I’ve seen. As a matter of fact, your comment above is quite literally the most inflammatory comment I have seen yet while browsing the fediverse in the last week so maybe Beehaw should defederate with kbin.social? It’s got the same influx of new users and open enrollment. kbin.social was almost certainly only spared because at the time they weren’t federating with anyone due to the DDOS protection from Cloudflare. How utterly ridiculous.
Yeah, I made an account, learned of potential issues, took a look at kbin and decided I like that better, and haven’t been back. Never posted a thing from it, as far as I can remember. Stalk much?
As to it being inflammatory, I’m pretty much repeating the explanations giving by the admins for defederating. You did read the explanation post, right?
Mentioning you actually autofills both options, so no, not stalking…
Clearly you haven’t checked the modlogs because Beehaw admins literally banned 5 users of probably 20,000 at the time before deciding to defederate based on open enrollment, which kbin.social also has so don’t be surprised when your instance is also defederated.
Oh, that’s very interesting that it autofills both… I’m surprised that it will tie the accounts together like that. It seems potentially error-prone as different people on different instances are bound to end up picking the same usernames.
But if they defederate from kbin, no, I’m not going to fret about it. It’s bound to be temporary until issues are addressed, as is the current situation. Kbin itself was completely defederated for much of the time I have been using it.