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.

  • ipha@beehaw.org
    link
    fedilink
    English
    arrow-up
    88
    ·
    1 year ago

    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.

    • Nerd02@forum.basedcount.com
      link
      fedilink
      English
      arrow-up
      33
      ·
      1 year ago

      Agreed. Sh.itjust.works has plenty of interesting communities, pressing the big red button for just one name seems a bit overkill.

    • Thalestr@beehaw.org
      link
      fedilink
      English
      arrow-up
      29
      ·
      1 year ago

      This. Defederation should be used as a last resort or if an instance has been a significant problem.

    • Jeze3D@beehaw.orgOP
      link
      fedilink
      English
      arrow-up
      12
      ·
      1 year ago

      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.

    • BeegYoshi@lemm.ee
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      It seems like a deliberate attempt to cause trouble and a federation debate to me. All that nonsense belongs on exploding-heads where it can be easily ignored