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.

  • Kerrigor@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    I see you’re not familiar with EEE. This is a classic move by enterprise to kill an open competitor.

    • Flax@feddit.uk
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 year ago

      I am. How could they kill the fediverse? If they tried to kill it, it would only return to how things was. Chances are tumblr could join in and then they couldn’t easily extinguish it.

      • Kerrigor@kbin.social
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Ever heard of XMPP?

        If a single party participating in an open standard is large enough, they can go off the track, and then kill off interoperability.

        • Flax@feddit.uk
          link
          fedilink
          arrow-up
          0
          arrow-down
          1
          ·
          1 year ago

          But this isn’t a single party. Mastodon and Lemmy and Kbin are well established