XMPP

the first, okay.

Um, it was built on XMPP.

There was a windows client.

We eventually, uh, uh, merged it into Gmail and it became Gmail chat.

... um, so yeah, that's what we've been doing.

And through that we- I've worked on everything from Tor to open app stores, to, uh, secure messaging through XMPP and Matrix, to, um, privacy preserving analytics because we saw a lot of people just dropping in like Google and Facebook analytics into their supposed secure stuff.

Um, and then most recently, like internet shut down technologies 'cause we've seen countries and places go from like, "Hey, we're going to filter a website" to, "We are turning off the whole internet."

Yeah.

Debates centered on the technical distinctions between different Apple email services and the broader implications of domain changes for privacy and spam filtering.

Title: Jabber XMPP: Twenty-five Years of Digital Independence.

Source: Daniel Gulcz.

The post discusses the history, challenges, and current state of XMPP, Extensible Messaging and Presence Protocol, a standard for online communication that has been around for more than twenty-five years.

It highlights XMPP strengths such as vendor independence and open standards, but also notes issues like complexity and limited adoption compared to newer protocols like Matrix.

The article emphasizes the importance of standards and interoperability for digital infrastructure and warns against replacement by closed single vendor solutions.

In the comments, the community mostly supported XMPP's legacy and resilience, with users sharing their experiences with setting up and using XMPP servers and clients.

Some argued that XMPP remains relevant, especially for private small-scale communication and agent workflows, but others pointed to its complexity and usability hurdles.