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.

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

    Yeah that’s something I’ve not seen discussed here much. I get that people want control, but getting started with an ActivityPub centric site (like kbin) is now cheaper than ever. Get your own cheap hosting on a VPS and handle some traffic.

    People can even create their own instances just to federate with everyone and absorb their content if they’re worried about the rules and regulations or “x server not connecting with y”

    Overall I think it’s a pretty good system compared to a single silo like Reddit