If this is the case, I urge EVERY instance admin across all currently federated apps to blacklist threads.
If threads is allowed to federate with these apps, it will outweigh all contributions to these apps, and when Meta eventually defederates (which they will), the vast majority of the community will be lost.
PLEASE HEED THIS WARNING!
Will Meta try to fuck over Fediverse? Very likely.
Is it mutually beneficial to be federated? Yes.
Mastodon will never be the biggest player around for microblogging because too many people nope out when presented with server selection, even with defaults.
Take whatever users you can now. Threads app has no “following” chronological timeline, probably never will. Show people you can do that from Mastodon and it’s clients.
It’s likely that one of the reasons Meta is using Activity Pub is upcoming EU regulations on electronic platform gatekeepers. They will have to open them in some way anyway. It’s likely regulators will be checking if Meta is playing nice with Threads.
Threads can try to EEE Mastodon but so can Mastodon. Mastodon can fuck over Threads in many ways too, mostly by providing better experience and it’s better than isolating.
Ahem, there seems to be some points that are glossed over:
Yes, asap. The zuck wants “the metaberse” to be a thing.
No, they will ddos us now, and defederate later after obtaining the “power users”. Google did similar when the more versatile xmpp account was xmpp-compatible-Google-talk that was pushing features and using the xmpp early adopter community as a free q&a while attracting all new users.
One of your assumptions is that lemmy admins are chasing user count. Some instances are chasing user quality. “Getting users while you can” is a good example of this assumption. A approach on forums (lemmy seems like a forum to me) is A community only chases users until critical mass is reached. Then it doesn’t matter as the community can maintain content production and quality easily.
You say just “make a Better experience”. Making one via open source developers or a team of paid Facebook developers will have vastly different production speeds. The problem being laid at the mastodon open source developers of “just be better” is a fools errand, and Google did a similar tactic of introducing features that were inherently buggy on xmpp only servers. I can only imagine how Facebook will do it so that there is no extra time to do anything other than debug the Facebook users experience. If we remain separate, we can be distinct and not “used”. And grow in a manner that doesn’t burn out.