Yes there are all sort of workarounds like protocol extensions and what have you not, but then you add massive new friction to the system ("No sorry my client doesn't do OpenVideoCall2.0 it only does LibreAVConference0.3"). That type of friction isn't that hard to deal with if you have a bunch of tech savvy people with time on their hands. But it is no longer appropriate for todays web that is used by everyone.
> Indeed, cannibalizing a federated application-layer protocol into a centralized service is almost a sure recipe for a successful consumer product today. It’s what Slack did with IRC, what Facebook did with email, and what WhatsApp has done with XMPP. In each case, the federated service is stuck in time, while the centralized service is able to iterate into the modern world and beyond.
How so? Nothing prevent versioning a protocol and having experimental servers.
And furthermore, it'd be reimplemented almost instantly by Facebook / Apple / Microsoft / Google.
So I can see why they decided to chart a different path.
wait, how? It's not like there was/is a lot of ppl on IRC, just a handful, and it doesnt fit into their product (talking with strangers)
As has been mentioned here, Facebook is running out of strangers to connect: future growth will depend on adding new types of users.
Make something idiot-proof and the world will make a better idiot. And it looks like I'm the bigger idiot here because I don't understand the interface at all.
I'm in two servers for two open source projects but my ID seems to be different for the two servers and not federated for some reason. Or is it? I don't really know. ¯\_(ツ)_/¯