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.

  • Illecors@lemmy.cafeEnglish
    21·
    1 year ago

    Posts are public, yes, but you won’t be able to see a post from an instance you’re not federated with on your own instance. Yes, you can just load the instance url directly, but that’s just web scraping. All voting interactions, views, etc are not available in those cases.

    I understand that if we have a setup like this:

        Threads
  /         X
A ----------- B

    then interactions from instance B on a post on instance A will, in fact, be available to Threads. But nothing happening on B will.

    Interactions on posts/communities on instance B coming from instance A will not be seen by Threads.

    Overall, I think Threads will not actually ever enable federation to begin with, and even if it does - Lemmy is a bit of a different beast compared to Mastodon.