Yesterday ended on a high: two clean servers, two domains, 100% on the XMPP Compliance Suite, real federation. Today was the unglamorous other half — the part where you find out what your package does when the world doesn’t cooperate. I paired with Claude again. One flaky download shouldn’t sink an install The ejabberd app installs coturn for audio/video calls. Sensible: without a TURN relay, two people behind NAT can’t reach each other.

Continue reading →

Yesterday I concluded that ejabberd-for-Matrix isn’t ready, and that for plain XMPP my Prosody 13 setup is actually ahead. Fair. But the ejabberd YunoHost app still needed to exist — properly, catalog-quality — for the day that Matrix gateway bug gets fixed, and because choice is good. A half-finished packaging experiment isn’t a real option. So today’s job was to take the app from “installs on my test box if I hold its hand” to “a stranger could install this and it just works.

Continue reading →

Yesterday I came home to Jabber — my own XMPP server, ralph@mayer.rocks, passing the compliance suite. But I run more than XMPP. There’s a Matrix homeserver (Synapse) too, with bridges puppeting Signal and WhatsApp into it. It’s a lot of moving parts for “sending messages to people.” So today’s question was bigger: could a single server do it all? ejabberd is an XMPP server like Prosody — but it also ships an experimental Matrix gateway.

Continue reading →

I used to give talks about XMPP. Back then I was sure Jabber would win — an open, federated, standards-based protocol for real-time messaging, the way email is for mail. It didn’t win. The walled gardens did, and today “chat” means a dozen incompatible silos, each with its own app demanding a slice of your phone and your attention. But the protocol never died. And lately I’ve had the itch to come home to it.

Continue reading →