The admin of sh.itjust.works has been approached but as of yet has failed to reply to concerned Lemmy users. I’m glad Beehaw admins look out for us by cutting off instances that host communities like this.
this post was submitted on 23 Jun 2023
327 points (100.0% liked)
Chat
7483 readers
17 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This "defederate at the slightest sign of trouble" mindset is dangerous. It's not like sh.itjust.works endorsed that terrible community they just happened to temporary set up there before they were banned.
If you just block every instance that hosts a community you disagree with, beehaw will end up completely isolated. This isn't necessarily a problem, but don't try to pretend you're part of the federation at that point.
That’s not why sh.itjust.works was defederated from Beehaw. It was defederated for having open signups resulting in moderation issues and botting. This thread is an affirmation that it was a good call since they now have toxic users creating toxic communities which is part of the reason for defederation.
You’re creating a problem that doesn’t exist to get mad at it.
Is that why? sh.itjust.works isn't included in the list of instances defederated for bot risk.