- cross-posted to:
- fediverse@kbin.social
- cross-posted to:
- fediverse@kbin.social
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:
-
Federate regardless (mostly the toxic instances everyone else blocks)
-
Federate with extreme caution and good preparation (some instances with the resources and remit from their users)
-
Defederate (wait and see)
-
Defederate with the intention of staying defederated
-
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.
It’s blatantly wrong. Google extended XMPP for their own purposes and when participating with XMPP no longer suited them, they left. The collapse of the “XMPP userbase” is a misnomer - those users were never XMPP users. They were Google Chat users. When Google left, XMPP was in the same state it was in before Google got on board. It returned to its status as a niche protocol for a service that, as @effingjoe@kbin.social points out, people didn’t really want anymore.