what does it mean that Beehaw "defederated" from lemmy.world?
I thought I understood, but I still have Beehaw content in my feed, so I guess I don't understand after all... Can someone dumb it down for me?
You are viewing a single comment
I thought I understood, but I still have Beehaw content in my feed, so I guess I don't understand after all... Can someone dumb it down for me?
So for those who know this better, should Lemmy Kbin users look for alternative to these communities (games/gaming for me)
You should be looking at multiple communities on the same topic just as a matter of course. Single mega-communities really aught to be discouraged, since they actually crush meaningful engagement (most posts don't ever get seen, most comments don't ever get seen, etc.)
If you follow multiple communities on the same topic, you can get the same kind of constant content stream -- if that's what you're concerned about -- while also actually having your contributions noticed.
Plus, not having single points of failure is the lesson everyone should be taking away from Twitter and Reddit.
Not necessarily. From what I understand, it's about lemmy/kbin not vetting users. Because they were a a more heavily moderated community (by design) it's harder for them to keep that standard with other federated instances. Instead of trying to combat the population increase platforms have received, they defederated while the "riff raff" gets sorted out. If they are willing to re-federate in the future, I'm sure they'll be back. It's just the influx of users makes it harder for their small team to moderate content.
This is how federation works, though. It's by design. If you are wanting to see that content, you are able to move to a different instance (or even beehaw, if they are still taking applications), or to one that is still federated with them.
Yeah, I don't really see this as a drama.
Beehaw and lemmy.world have different goals. Beehaw said that this isn't a permanent ruling nor a judgement on said communities - merely a practicality to meet their goals. Lemmy's moderation tools and the moderation staffs are just unable to keep up with the rate of new users currently.
The decision will be revisited in the future, when both of these things have time to catch up. It sucks, but neither side is wrong here.
I'm getting a little bit mixed signals, as it seems beehaw mods are little quick to moderate users, which to be fair, you specifically signed up for. Beehaw can moderate how they want. I think it's just partly because so many came at once, people filtered to what was available regardless of if they agreed with the platform rules heavily or not. You just went where you went to get in. It'll get sorted eventually
Kbin? I thought they were only defederating from lemmy.world and sh.itjust.works?
AFAIK it is only lemmy.world and SJW, but I mentioned kbin because it was another instance that was receiving a lot of new users along with those other platforms.
I don't believe any kbin instances have been de-federated by beehaw...
Yeah, but if people were intentionally being trolls, it stands to reason that they'll hop on the next available open registration site and begin their shenanigans there, getting us banned too.
From what I've seen, for the most part the KBin magazines have been great, but we've definitely got a few people that I've seen that might intentionally start harassing trans people for instance and if they make lives difficult for the beehaw mods, we might get banned too just by association.
Open signups aren't novel on the fediverse, lots of places have them. The problem is having them without following up and banning problematic users... but yes I expect that if stricter instance-wide moderation doesn't happen this instance will end up being defederated by most of the fediverse (with mastodon at least that seems to be the norm).
I'm hoping moderation has been been lacking because Ernest is just overwhelmed with the amount of load, and that it is fixed soon, if not I'll end up moving on once admins start defederating it (probably to another kbin instance).