Aside from the hand-waving comment about XMPP
“Aside” is doing a lot of the heavy lifting here, it reeks of a nauseating amount of hubris and makes one wonder if they’re suitable to maintain the project at all if they’re so oblivious to potential threats to the project.
I don’t understand what people think should happen here
Not roll out the red carpet for starters, and not engage with the company under NDA would be a good second.
Especially for a FOSS project that receives a healthy amount of contributions from others and likes to tout that it's co-owned by all contributors, it could be argued that it's highly objectionable for one person to engage, essentially as a representative, in non-transparent dealings that are sealed under NDA.
It really isn't rocket science, here's how the admin of the Fosstodon instance handled it.
Notice the lack of red carpet, the unwillingness to participate in an "off the record" event and the abundance of transparency towards the people he's responsible for.
I'm not saying that Rochko should've adopted the same abrasive "lol, get rekt" tone, its up to him if he's comfortable with that, but the points I'm hammering on about above can be achieved in respectful manner as well.
There is tons of choice here and the way it’s architected, several layers of protection.
There is no protection. As I've stated in a different comment, t doesn’t take more than 2 seconds of thinking to see how empty the words are that Mastodon is not at risk.
- Threads federates with Mastodon instances
- Threads uses its massive engineering resources to implement proprietary functionality that’s incompatible with Mastodon instances
- A non-trivial number of Mastodon users jump over to Threads, this is the first wave of people that leave Mastodon
- Threads drops support for federation and silos itself off
- The majority of the remainder of people on Mastodon jump over to Threads because they want to be able to continue to interact with the people that jumped over to Threads and/or because they want to be able to continue to interact with normies now that they’re used to that
- Mastodon is effectively dead, safe for a select few that stick to their guns
3 and 5 will happen in a cascading manner, the more people switch to Threads, the more others will also want to switch.
At the end of the day, if a large corporation joining the network, kills it, then it was destined to be destroyed from the beginning.
Perhaps it is destined to be destroyed.
The concerns and ramifications of a large corporation, or any entity that vastly overshadows the "organic" Mastodon user base in orders of magnitude for that matter, federating with Mastodon have been brought up numerous times by many parties, with the goal of looking for a solutions.
These concerns weren't only brought up in light of a possible EEE strategy that lead to the death of Mastodon, but also in light of a more Google-esque play where the market share isn't necessarily used to outright kill, but instead to exert control1.
Every single time it fell on deaf ears (i.e. Rochko ignored it, if not outright killing the discussion), often shrugged off matter of factly that it isn't a risk.
Also make no mistake, we're talking about a layered issue here.
A network that can destroy Mastodon against its will due to its sheer size is bad enough.
Mastodon, by virtue of Rochko, facilitating this from within, adds an entirely new dimension to this.
1 Google famously bypasses standardization bodies and simply implements their in-house developed standards, leaving other browser engines to get with the program and implement what Google wants, or become irrelevant