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.

  • effingjoe@kbin.social
    64·
    1 year ago

    I feel like people read a comment that linked XMPP with EEE and keep parroting it while not understanding it.

    XMPP still exists, but people largely don’t want “Instant Messaging” anymore. They don’t want to care about whether the person is online before they can send a message.

    Google dropping support for XMPP didn’t do that, it’s what caused them to drop it. They moved on to what people wanted: asynchronous messaging.

    This concern about the now overused “EEE” stuff is blown away out of proportion.