The instances blocking Zuckerberg's Threads.net

Stantana@lemmy.sambands.net to Fediverse@lemmy.ml – 487 points –
#Fedipact - The instances blocking Zuckerberg's Threads.net
fedipact.veganism.social

Made by Nume MacAroon at Veganism.social https://veganism.social/@nm

127

You are viewing a single comment

Hate to burst your bubble, but no-one was actually using XMPP with Google Talk except for open-source tech nerds.

And google stopped any chances of that ever happening. The Fediverse should just let itself grow gradually and naturally, as should have XMPP

How so? I don't see the EEE in Google discontinuing XMPP support tbh.

They piggy backed on rapidly growing XMPP and then became lazy with keeping compatible with the rest of the xmpp federation and at some point the s2s connection stopped being feasible as they never implemented TLS for it, and did't really care as most xmpp users were on their server anyways and thus did't use the s2s connection.

Its not a typical nefarious EEE story, but it did a lot of damage to the xmpp federation anyways.

This predates Google Talk and is rather about the XMPP Gmail integration. Back then XMPP was the hot topic in tech circles (Twitter was even prototyped to be XMPP based) and people were switching to it and recommending it to others to replace ICQ/MSN/AIM etc. However, often they recommended others to use the Google XMPP service as back then Google was still naively seen as the "Do no evil" good guy, having just started up recently and giving away free things like previously unheared off 1GB of email storage etc.

So the situation is not quite comparable to AP and Facebook (and XMPP is far from dead), but it is still possible to draw some lessons from it.

So what?

Means there's no incentive for Google to support it.

Then why did they once support XMPP?

Probably to experiment with it, or maybe it was a good idea back then. Definitely not to extinguish it lol