It is expected to be 2-3 months before Threads is ready to federate (see link). There will, inevitably, be five different reactions from instances:

  1. Federate regardless (mostly the toxic instances everyone else blocks)

  2. Federate with extreme caution and good preparation (some instances with the resources and remit from their users)

  3. Defederate (wait and see)

  4. Defederate with the intention of staying defederated

  5. Defederate with all Threads-federated instances too

It’s all good. Instances should do what works best for them and people should make their home with the instances that have the moderation policies they want.

In the interests of instances which choose options 2 or 3, perhaps we could start to build a pre-emptive block list for known bad actors on Threads?

I’m not on it but I think a fair few people are? And there are various commentaries which name some of the obvious offenders.

  • Zaktor@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    Defederation is a one-way block of incoming traffic from the blocked instance. I’m on lemmy.world and can still see Beehaw content posted by Beehaw users even though they’ve defederated from lemmy.world, but if I comment on that content it will only be visible to lemmy.world users. Beehaw has protected its communities from lemmy.world commenters, but its content is still accessible by anyone for any purpose. Instances that federate with both sides don’t change this.

    • Kichae@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I’m looking at beehaw communities on both Lemmy.world and Beehaw.org,and they’re totally out of sync with each other. There’s the rare post from a beehaw user that breaks through somehow - possibly boosted from a kbin or Mastodon instance? - but for the most part, you’re getting basically none of the content from those communities.

      Because beehaw isn’t sending you any updates.

      Is it that you’re seeing beehaw users who are posting to communities hosted on 3rd party communities? Because that’s absolutely possible.

      And that’s absolutely the issue with federating with sites that continue to federate with instances you’ve defederated from. You’re blocking direct communication in both directions, but there’s a lot of indirect communication going on.

      Like, this is literally the scenario I described.