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!
How about instead we welcome them into the Fediverse?
If they introduce an improvement and release it to the Fediverse for free, and forever, then we all gain.
If they introduce an improvement and keep it proprietary then we can blast them.
No. Meta is shit. End of story.
It would still be up to the admins/devs to introduce those features to their respective instances. There is nothing preventing the integration of innovative features whilst still keeping the instances entirely separate.
An improvement under Foss won’t happen. It is all closed source for them. At most it will be “buggy implementations trying to follow what the majority of users are using under zuck” and then we will be doing nothing but free q&a for zuck
I’m also not exactly seeing what the fuss is about. It might end up being a net positive for everyone. It also might end up being shitty, in which case the Fediverse and that Thread thing will probably divorce one way or another, probably by defederation of each other, but neither would die. Doesn’t seem like there’s much downside.
You didn’t mention your knowledge of how Google killed the federated software xmpp in your comment. As such, I think you should read one of the articles about how to kill the fediverse before you say “let’s be optimistic about how zuck treats his competition so they can continue to operate adjacently”
I actually read that article you’re thinking about right after posting this comment, and I have to say it was pretty compelling. I’d say we still don’t know Meta’s intentions so it’s all just guessing (reminder that Google built GMail and yet email is still around), but I definitely understand better the caution now.