Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.

If you’re a server admin, please defederate Meta’s domain “threads.net

If you don’t run your own server, please ask your server admin to defederate “threads.net”.

  • Zorque@kbin.social
    link
    fedilink
    arrow-up
    26
    arrow-down
    6
    ·
    7 months ago

    Then feel free to go to threads or somewhere that does federate with them. You don’t have to stay on a particular instance if they don’t federate with something you want to engage with.

    That’s your freedom of choice.

    • BaroqueInMind@kbin.social
      link
      fedilink
      arrow-up
      2
      arrow-down
      20
      ·
      7 months ago

      There is no plan for kbin to defederate with Threads, which is why I’m here you dolt. Maybe you should leave.

      • Draconic NEO@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        Makes sense, Kbin is one of the most lax instances when it comes to moderation and defederation, and that’s why they’re considered so bad when it comes to spam and illegal content.

        • BaroqueInMind@kbin.social
          link
          fedilink
          arrow-up
          1
          arrow-down
          2
          ·
          7 months ago

          I like the freedom of kbin but also maintain an account on Beehaw because they are the complete opposite with frustratingly strict moderation to the point of moderators telling people to check their naughty language at the door (which is totally understandable).

          • Draconic NEO@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            7 months ago

            However the serious problem with Kbin’s very lax approach is that it invites some really nasty people who will exploit it. I heard an admin say that a majority of the spam and CSAM attacks have come either from kbin.social or other kbin instances, and at the time it was made worse by a bug that prevented mod actions from federating from kbin, meaning the content stays up even after moderated on its home server. It wasn’t great.