News for hackers. Stuff that matters.
Re:Jabber/XMPP: 25 Years of Digital Independence by fishgoesblub on Monday August 24, 2026 @02:02PM (#49423612)
I love XMPP and am hopeful for its future with what the teams behind Movim[0], and Fluux[1] are doing. It was a tremendous shame that Matrix didn't improve upon XMPP and instead did their own thing. I continuously wonder what would the XMPP ecosystem look like, if the millions of dollars of funding Matrix initially had (what a waste) went to XMPP instead?

[0]: https://movim.eu/

[1]: https://github.com/processone/fluux-messenger

Re:Jabber/XMPP: 25 Years of Digital Independence by PunchyHamster on Monday August 24, 2026 @05:16PM (#49425954)
It makes sense. It's old, crufty mix of extensions, which nobody actually wants to be that modular for a chat client, because that just gets you into mess of what server/client supports
Re:Jabber/XMPP: 25 Years of Digital Independence by akho on Monday August 24, 2026 @05:45PM (#49426254)
Matrix is in the same place wrt feature mismatches. It's a quality of the problem, not of the solution. I actually think XMPP does a better, more structured job here.
Re:Jabber/XMPP: 25 Years of Digital Independence by neilalexander on Monday August 24, 2026 @06:20PM (#49426640)
XMPP leans heavily on capability negotiation and service discovery which makes it straightforward to degrade gracefully when feature mismatches occur. Matrix is significantly lacking in this regard.
Re:Jabber/XMPP: 25 Years of Digital Independence by shadowgovt on Monday August 24, 2026 @10:11PM (#49428313)
Unfortunately, some of the features that can degrade are things like "the chat is actually secure."
Re:Jabber/XMPP: 25 Years of Digital Independence by opan on Tuesday August 25, 2026 @12:17AM (#49429009)
I strongly prefer that with XMPP I can disable the encryption when it breaks to tell my friend I'm trapped under a boulder and bleeding out. With Matrix our chat is encrypted, I can't turn it off ever, if it stops working I can't communicate, my only option is to make a new room with encryption disabled and invite my friend hoping he sees the invite and accepts in time.
Re:Jabber/XMPP: 25 Years of Digital Independence by Dormeno on Tuesday August 25, 2026 @04:16AM (#49430573)
It's funny because I remember having an issue where my friend was sending me messages, and he couldn't read my messages, and my mobile client (Siskin) didn't let me turn off encryption for outgoing messages.
Re:Jabber/XMPP: 25 Years of Digital Independence by oivaksef on Tuesday August 25, 2026 @01:46AM (#49429557)
I want to see this movie

Edit: now I can't stop thinking about correlation vs causation - you being under the boulder bleeding out at the same time XMPP encryption suddenly stops working.

Physical hardware certificate thinggy which got crushed?

Re:Jabber/XMPP: 25 Years of Digital Independence by shadowgovt on Tuesday August 25, 2026 @03:32PM (#49439399)
Recommendation: if you're trained under a boulder, use the device you're running an XMPP chat client on to call 911.
Re:Jabber/XMPP: 25 Years of Digital Independence by 306bobby on Tuesday August 25, 2026 @08:59AM (#49433269)
That's how RCS's Universal Profile is too though as far as I understand with the new encryption standards.

Id rather someone be able to reach out to me with a note the chat is insecure, rather than be unreachable at all

Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Monday August 24, 2026 @07:02PM (#49427012)
> Matrix is in the same place wrt feature mismatches.

not it isn't - still today there's no choice between incompatible room types or incompatible encryption algorithms and whatever else.

Re:Jabber/XMPP: 25 Years of Digital Independence by akho on Tuesday August 25, 2026 @04:51AM (#49430808)
Calls are implemented differently across clients, threads only sometimes work. And, apparently from your comment, there's only ever going to be one encryption algorithm, because cryptography is a solved problem now?..
Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Tuesday August 25, 2026 @05:08AM (#49430953)
Don't Element Continuwuity, Synapse, Sable, FluffyChat and more all implement Matrix RTC, because this is most likely the future of video calls in Matrix (while not even officially part of the spec at this point)?

> And, apparently from your comment, there's only ever going to be one encryption algorithm, because cryptography is a solved problem now?..

That's not from my comment. If there will be another one it likely will be integrated into THE specification such that it will NOT divide the ecosystem into "I prefer MEGOLM" and "I prefer to implement new thing".

Re:Jabber/XMPP: 25 Years of Digital Independence by selfhoster1312 on Tuesday August 25, 2026 @12:31PM (#49436717)
I don't have a horse in this race, but "incompatible room types" is precisely an issue i encountered on a selfhosted server. Agreed, that was for S2S federation and not C2S, but that was an issue.
Re:Jabber/XMPP: 25 Years of Digital Independence by vcccgjuf on Monday August 24, 2026 @06:19PM (#49426626)
Matrix is nearly as old today as XMPP was when the Matrix project was started, and Matrix is still such a pile of shit standard that there's STILL only one server implementation and one client. That's actually not how the standard was designed; if Matrix had been a successful project, according to their own goals, the ecosystem would look a lot more like XMPP than it does.

Comparing XMPP at 11 years old to Matrix today makes it abundantly clear that the main thing Element LLC does is waste European public grant funds

Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Monday August 24, 2026 @06:56PM (#49426966)
Actually, Matrix has a series of server and client implementations.

Servers: https://matrix.org/ecosystem/servers/

Clients: https://matrix.org/ecosystem/clients/

Also, imho Matrix is a better standard than xmpp, because of what PunchHamster said and the better feature set. Of course, everyone is entitled to their own opinion :)

Re:Jabber/XMPP: 25 Years of Digital Independence by opan on Tuesday August 25, 2026 @12:20AM (#49429025)
I think GP was speaking hyperbolically, because most new features hit Element/Synapse first and other clients lag behind implementing them. If you care about more than the basics working, it's kind of just the illusion of choice.
Re:Jabber/XMPP: 25 Years of Digital Independence by ezst on Tuesday August 25, 2026 @03:35AM (#49430281)
Probably, and also from the fact that although there's a plethora of matrix clients and servers on paper, none is as feature complete (or feature-complete to the point of usefulness, I might say) as "the one". XMPP has about one decent-to-great client per platform and multiple fully compatible and interoperable server implementations, and every single one of them is by different groups.
Re:Jabber/XMPP: 25 Years of Digital Independence by JadedBlueEyes on Tuesday August 25, 2026 @05:24AM (#49431056)
I mean for alternative servers, 10% of people use Continuwuity and it looks pretty spec-complete [0] and more than enough to be useful.

[0]: https://forgejo.ellis.link/continuwuation/continuwuity/issue...

Re:Jabber/XMPP: 25 Years of Digital Independence by ezst on Tuesday August 25, 2026 @06:21AM (#49431461)
Last I checked (couple years ago?) it was ill-advised to use anything but Synapse, because:

- you would be at the mercy of very real and frequent federation problems (Matrix being so implementation-dependent and centred around Synapse ; like, the json serialization format is better described as "whatever order and structure python's stdlib is doing"¹)

- there is no non-destructive way back to another server (the open federation would just reject you, and you would have to "start anew"). Interestingly, that last one pushed some servers over the fence and into XMPP, and they could then switch implementations (e.g. from prosody to ejabberd) effortlessly.

¹: https://telegra.ph/why-not-matrix-08-07#:~:text=matrix%20hom...

Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Tuesday August 25, 2026 @07:40AM (#49432235)
1) solved by canonical Json many years ago, see https://spec.matrix.org/v1.19/appendices/#canonical-json (goes back to at least matrix 1.1 which was released 2021)

2) Why would open federation reject you? Given you don't throw away your private key

Re:Jabber/XMPP: 25 Years of Digital Independence by JadedBlueEyes on Tuesday August 25, 2026 @11:13AM (#49435567)
1) That hasn't been a problem for at least half a decade.

2) What do you even mean? I've literally deleted my entire database and then spun up a new server on the same domain before, it does not matter, other servers do not care! The worst that could happen is messages from the original server can no longer be verified as valid - and even that isn't a problem in practice.

Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Tuesday August 25, 2026 @04:31AM (#49430655)
Define what you think are more than the basics?
Re:Jabber/XMPP: 25 Years of Digital Independence by opan on Monday August 31, 2026 @03:04PM (#49513610)
Spaces, voice and video calls, custom emoji or stickers. Basically the stuff people coming from Discord are used to but the people coming from IRC/XMPP aren't used to.
Re:Jabber/XMPP: 25 Years of Digital Independence by muvlon on Tuesday August 25, 2026 @02:03AM (#49429654)
At 11 years old, XMPP had 0 usable clients (I was there and tried them). That's one less than Matrix.
Re:Jabber/XMPP: 25 Years of Digital Independence by inputmice on Tuesday August 25, 2026 @02:23AM (#49429777)
XMPP at 11 years old would place us in the year 2010. Requirements were different in those times. Psi on my desktop and Bombus (a J2ME client) on my Nokia E71 worked great. The transition from that into the mobile-first age was rough though. The article says that too. It only improved in 2014-2015.
Re:Jabber/XMPP: 25 Years of Digital Independence by singpolyma3 on Tuesday August 25, 2026 @09:13AM (#49433461)
Everyone says this and so I believe them, but I used xmpp as my primary communication tool through the whole thing and it worked ok on my first android phone (HTC magic) and amazingly on my n900 followed by acceptably on my BB10 device and never had any issues
Re:Jabber/XMPP: 25 Years of Digital Independence by zaik on Monday August 24, 2026 @05:37PM (#49426198)
> mess of what server/client supports

If you allow for independent implementations of the protocol this will always happen. Also, inventing another non-standard protocol creates even more incompatibility between clients and servers.

Re:Jabber/XMPP: 25 Years of Digital Independence by opan on Tuesday August 25, 2026 @12:18AM (#49429010)
IRC and email worked out pretty well I think.
Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Tuesday August 25, 2026 @05:28AM (#49431090)
e-mail stuck in time still not enceypting by defaul
Re:Jabber/XMPP: 25 Years of Digital Independence by singpolyma3 on Tuesday August 25, 2026 @09:14AM (#49433473)
Yes if you never add new features eventually everyone crystallizes
Re:Jabber/XMPP: 25 Years of Digital Independence by shadowgovt on Monday August 24, 2026 @10:10PM (#49428310)
"Oh, I'm sorry, did you want it to work? You should have installed the 'it actually works' modules."

Working with XMPP gave me a whole new appreciation for why people keep inventing their own chat protocols. I don't think this is an unsalvageable situation, but the protocol is desperately in need of an "XMPP: the Good Parts" doc.

Re:Jabber/XMPP: 25 Years of Digital Independence by ValdikSS on Monday August 24, 2026 @11:56PM (#49428889)
XEP-0479: XMPP Compliance Suites 2023

https://xmpp.org/extensions/xep-0479.html

Re:Jabber/XMPP: 25 Years of Digital Independence by tredre3 on Monday August 24, 2026 @11:17PM (#49428712)
> the protocol is desperately in need of an "XMPP: the Good Parts" doc.

It exists! https://docs.modernxmpp.org/

Re:Jabber/XMPP: 25 Years of Digital Independence by ValdikSS on Monday August 24, 2026 @11:55PM (#49428886)
Daniel (the author of the linked article) was one of the people to define profiles for human chatting: https://xmpp.org/extensions/xep-0479.html
Re:Jabber/XMPP: 25 Years of Digital Independence by account42 on Wednesday August 26, 2026 @04:14AM (#49445566)
That just means the protocol is old enough to have accumulated that much technical debt, which is a sign of resilience.
Re:Jabber/XMPP: 25 Years of Digital Independence by shadowgovt on Monday August 24, 2026 @10:08PM (#49428298)
It's because the xmpp standard is absolutely brutal. I've tried to stand up a server and the amount of configuration I had to do just to get off the ground was absolute nonsense.

It's sort of the Apache of chat protocols and that's not a compliment.

Re:Jabber/XMPP: 25 Years of Digital Independence by Semaphor on Monday August 24, 2026 @10:43PM (#49428498)
> I've tried to stand up a server and the amount of configuration I had to do

I run my own server for 2 people. Using Prosody [0] took some config but wasn’t that hard. Easier than installing Arch, harder than installing Windows ;)

Nowadays, there is also Snikket [1] by the Prosody maintainer, which is essentially an opinionated all-in-one configuration setup based on Prosody, barely any config needed.

[0]: https://prosody.im/

[1]: https://snikket.org/

Re:Jabber/XMPP: 25 Years of Digital Independence by rtpg on Tuesday August 25, 2026 @03:54AM (#49430415)
to anyone reading this who is thinking of setting up snikket: suffer through setting up prosody. It's a bit futzy but you won't find yourself saying "ah if only I had tried a bit harder" 10x a minute when trying to configure things later on.
Re:Jabber/XMPP: 25 Years of Digital Independence by tredre3 on Monday August 24, 2026 @11:08PM (#49428651)
Counter point: I ran prosody for years and changed almost nothing to the defaults.

Just like with Apache, all you need is a sane default configuration that covers the most common use cases, and I think modern XMPP servers offer that.

Re:Jabber/XMPP: 25 Years of Digital Independence by Semaphor on Tuesday August 25, 2026 @12:30AM (#49429079)
FWIW, I think I had to fight a bit to figure out setting everything up correctly for uploads to work. But as I said in sibling, nothing too problematic.
Re:Jabber/XMPP: 25 Years of Digital Independence by agile-gift0262 on Tuesday August 25, 2026 @01:57AM (#49429625)
Try out Snikket. Really easy to set up, with sensible defaults. You just docker compose up and have a pretty funcional XMPP server without needing to configure much. Adding complex things such as gateways onto Snikket is a bit more complicated, as you have to deal with Docker volumes etc to put the right file in the right place, but I found it easy to manage. I've been running my Snikket instance with gateways for WhatsApp and Matrix for a couple of years now and I'm really happy. It's very low maintenance
Re:Jabber/XMPP: 25 Years of Digital Independence by ezst on Tuesday August 25, 2026 @03:06AM (#49430090)
What server was that? I got into the XMPP self hosting game in 2014, even then, ejabberd was one of the most "fire and forget" piece of server software I was running. It takes some ports opening and some DNS SRV records to be set and you are good to go with all chat, calls and social features.
Re:Jabber/XMPP: 25 Years of Digital Independence by pkulak on Tuesday August 25, 2026 @01:03AM (#49429296)
Yeah yeah yeah. I’ve heard this for 8 years. And yet, everyone can talk a great game, no one can build a mobile client that is anywhere near the quality of any other chat platform.

And here I am, hosting a Matrix server for my family for 6 years now, with no issues and an amazing experience, from the backend to the huge variety of mobile clients, a mature Rust sdk that I can hook bots into with ease, etc.

Re:Jabber/XMPP: 25 Years of Digital Independence by pixelschubsi on Tuesday August 25, 2026 @02:54AM (#49429985)
Matrix doesn't even support server-to-client message pushing, only polling. Which means, if you want your phone to receive a message while your client is in the background, you have to use a non-Matrix protocol to receive those.

This protocol is XMPP in 99% of the time, both Apple and Google use XMPP to connect the phones to their push notification service.

On Android, some Matrix clients offer the option to use non-Google push notification channel via UnifiedPush. UnifiedPush needs a distributor, a service that runs on the phone and manages the delivery of push notifications. Conversations, a popular Android XMPP messenger, can be used as such distributor.

So if you want digital independence with Matrix and thus do not want to use Apple/Google push, you might end up installing an XMPP messenger, so that your Matrix messenger actually can show notifications. Matrix alone just doesn't provide what is needed for digital independence.

Re:Jabber/XMPP: 25 Years of Digital Independence by _flux on Tuesday August 25, 2026 @05:45AM (#49431193)
The protocol of Matrix does long polling though. Is there a big difference? You want at least heartbeat to detect a broken connection (at least from client end), and it looks like XMPP does not come with server-originated hearbeat for that purpose, so it's back to client-side pinging?
Re:Jabber/XMPP: 25 Years of Digital Independence by pixelschubsi on Tuesday August 25, 2026 @06:53AM (#49431732)
Well, apparently long polling is so bad on battery that Matrix clients for phones prefer to just not provide background notifications without any external push service. From what I understand, many Matrix services give their long polling a timeout of 60 seconds, which would prevent a phone from entering deep-sleep states.

XMPP uses a persistent connection. These are kept alive using TCP keepalive (both from server and on the client, but client side will be handled by the MPU and thus doesn't need CPU wake-up) and client initiated application protocol pings at intervals of 5 minutes or even less. Client initiated pings are much better on the application protocol, because they can be synced with other operating system tasks and thus don't need any active wake-up.

Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Tuesday August 25, 2026 @08:11AM (#49432583)
> Matrix doesn't even support server-to-client message pushing, only polling. Which means, if you want your phone to receive a message while your client is in the background, you have to use a non-Matrix protocol to receive those.

(aside long polling which I cannot comment) why is this a even an issue?

Centralized push services (may it be FCM or unified push) are at this point well established.

As a user using a specific messenger app as a push service doesn't gain me anything, it only makes it more difficult to switch messenger app if i choose to use it and mostly use an additional push service (hurting battery life), because most receive push notifications via Google anyway.

Re:Jabber/XMPP: 25 Years of Digital Independence by pkulak on Tuesday August 25, 2026 @05:11PM (#49440698)
What mobile OS do you use that allows an app to maintain a persistent TCP connection forever? Honest question. Last I checked, even Lineage/Graphene/etc will kill a background app after some amount of time. Doesn't matter if it's an hour or three days; if it ever happens, that's a deal breaker.

I think the right solution is to use a different notification service, not controlled by Google or Apple, not to get rid of the concept altogether.

Re:Jabber/XMPP: 25 Years of Digital Independence by account42 on Wednesday August 26, 2026 @04:03AM (#49445489)
I've not had any issues with my Samsung Android killing the Conversations client. It does have a persistent notification which is probably needed for this.
Re:Jabber/XMPP: 25 Years of Digital Independence by agile-gift0262 on Tuesday August 25, 2026 @01:51AM (#49429585)
Not sure about iOS, but for Android Conversations is great
Re:Jabber/XMPP: 25 Years of Digital Independence by account42 on Wednesday August 26, 2026 @04:06AM (#49445519)
Yes. The only feature I'm missing is to show linked images inline. But that's a matter of taste.
Re:Jabber/XMPP: 25 Years of Digital Independence by edhelas on Tuesday August 25, 2026 @01:48AM (#49429566)
Movim author there, thanks ! :)
Re:Jabber/XMPP: 25 Years of Digital Independence by lxgr on Tuesday August 25, 2026 @03:39AM (#49430309)
As I understand it, Matrix is a much better conceptual fit for the IRC/Slack-like use case where users expect substantial messaging history to persist across new devices and often even for members newly joining a channel. XMPP started out as a message routing protocol, with server-side history (for individual users or channels) bolted on as an afterthought; Matrix is modeled around conversations/channels as a first-class object on the server side.

Of course, that doesn't automatically make it great at what it's trying to do, nor does it make XMPP terrible in practice, but between mixed extension support at the client and server side, with XMPP you can never really know if you're getting "plain old Jabber" or something more like Matrix in terms of user experience.

Re:Jabber/XMPP: 25 Years of Digital Independence by ezst on Tuesday August 25, 2026 @04:13AM (#49430555)
> Matrix is a much better conceptual fit for the IRC/Slack-like use case

Debatable, this mostly boils down to the client design choices and priorities, and has little to nothing to do with the protocol. Someone came-up with a metaphor I like to illustrate it: the banquet and the barbecue¹. XMPP has "barbecue"-style clients like Conversations, Kaidan, Dino?, and other that are rather "banquet"-style like Gajim, Fluux, Movim, …

I personally use Conversations on the go and Gajim otherwise. I also happen to have interfaced all my "high-volume/many-participants" IRC chans from back in the days with the biboumi² gateway, so they appear to my XMPP clients as native XMPP groupchats, and the experience was great-enough for me to ultimately drop weechat a decade or so ago and have all my "banquet"-style chans under one XMPP roof.

> between mixed extension support at the client and server side, with XMPP you can never really know if you're getting "plain old Jabber" or something more like Matrix in terms of user experience.

From over a decade of using XMPP daily, this concern is more of philosophical nature than anything. The vast majority of the people you'll reach over XMPP use a decently modern and maintained client that will "just work". Worst case, they will still be getting your messages and the meaning across, because the "message passing" core of XMPP was defined 25-odds years ago and hasn't changed.

The real "risk" for XMPP would be to have a large number of users stuck on an unmaintained client, and users staying behind for years while the ecosystem moves on. We had a bit of that with pidgin 8-or-so years ago. The worse that happens is that you can't use the latest E2EE scheme with them, or that attachments are slower to arrive, this sort of things. That's IMO not bad for a 25 years old protocol that's truly decentralized.

¹: https://blogs.gnome.org/tbernard/2018/05/16/banquets-and-bar...

²: https://codeberg.org/poezio/biboumi/

Re:Jabber/XMPP: 25 Years of Digital Independence by lxgr on Tuesday August 25, 2026 @04:39AM (#49430710)
> Someone came-up with a metaphor I like to illustrate it: the banquet and the barbecue¹.

That's a nice way of putting it and it definitely resonates with my experience.

But why wouldn't it be possible to have these two in the same app as long as they are very cleanly separated in terms of who gets to notify me when, what's displayed where etc.?

WhatsApp (with channels) and Telegram (with its huge groups) seem to address both just fine, as far as I can tell, although I barely use their "mass-messaging/social-media-like" features.

As to whether one protocol can address both use cases: Maybe it doesn't need to either? I could see 1:1 chats and "ephemeral/barbecue" groups using one type of history persistence policy (i.e. usually none) and large group chats/pub-sub-like feeds another. This could all be independent of what holds somebody's persistent identity/identities.

Re:Jabber/XMPP: 25 Years of Digital Independence by ezst on Tuesday August 25, 2026 @06:08AM (#49431359)
> But why wouldn't it be possible to have these two in the same app

I don't believe it's "impossible" to have both in a same app, it's just that the kind of high-density UI and advanced features you depend upon for high-volume chats rarely intersect with family-scale/1-to-one chats, so you either make compromises that directly affect usability/efficiency, or you essentially end-up with 2 chat paradigms at odds in a same client.

> As to whether one protocol can address both use cases: Maybe it doesn't need to either?

It depends what you mean by protocol in this case. Chat rooms (MUCs in the XMPP verbiage) are handled by a specific component, so it's practically happening the way you describe, but at its core, the "message-passing" (stanza-based) nature of the XMPP protocol doesn't change.

Re:Jabber/XMPP: 25 Years of Digital Independence by tcfhgj on Tuesday August 25, 2026 @05:41AM (#49431174)
> Debatable, this mostly boils down to the client design choices and priorities, and has little to nothing to do with the protocol.

I think it does.

How would you as a client choose that the (potentially) encrypted chat history of all rooms is immediately available after logging in, let alone after joining an encrypted room?

You can't:

- how long messages are stored server side depends on someone else's server

- encrypted messages aren't recoverable from new sessions

Re:Jabber/XMPP: 25 Years of Digital Independence by account42 on Tuesday August 25, 2026 @11:22AM (#49435696)
> We had a bit of that with pidgin 8-or-so years ago.

8 years ago? Pidgin still doesn't do MAM today.

Re:Jabber/XMPP: 25 Years of Digital Independence by selfhoster1312 on Tuesday August 25, 2026 @12:16PM (#49436495)
Yes, but i haven't met someone who uses Pidgin in more than 5 years. Still, the pidgin team appears to be alive and their blog is always a good read!

https://pidgin.im/post/

Re:Jabber/XMPP: 25 Years of Digital Independence by rw_grim on Wednesday August 26, 2026 @04:15PM (#49455226)
We've retired the blog in favor of just posting on our discourse as noted in our last blog post ;)
Re:Jabber/XMPP: 25 Years of Digital Independence by rw_grim on Wednesday August 26, 2026 @04:16PM (#49455242)
Yep, it's hard to run a volunteer project when there's so much work to do...
Re:Jabber/XMPP: 25 Years of Digital Independence by rtpg on Tuesday August 25, 2026 @03:52AM (#49430409)
I was generally "Matrix feels right" but I read through [0] and other discussions and I think that Matrix's E2E focus + way of duplicating everything just means that it suffers a lot of scalability issues that "plain old Jabber" won't have.

now Jabber has client issues, but stuff like Monal "basically work" for text + images + chat rooms. I'm excited for Fluux. You can of course set up one of the random web clients. Stuff like reactions "work", notifications is a solved problem.

But like... at a basic level, "I'm hosting a Jabber server for my small community" has a lot less headaches than with Matrix. Yes if your server goes down then you lose the chat. Oh no. Plenty survived off of IRC IMO.

For the HN crowd... I would say that there's still fun jank, but who doesn't like jankiness in their programs for fun? People should swarm to this opportunity to have some fun with busted tooling again!

[0] https://wiki.alopex.li/ADiveIntoOpenChat

Re:Jabber/XMPP: 25 Years of Digital Independence by lxgr on Tuesday August 25, 2026 @04:33AM (#49430669)
> notifications is a solved problem.

Eh, last time I tried I still got leftover notifications for messages I had long read and even replied to on a different client hanging around on my other devices. (To be fair, Matrix does the same thing too, but only in roughly 50% of all cases, which is much more infuriating than something I can at least understand as a fundamental protocol limitation and not a weird implementation bug.)

I've been using XMPP on and off over the past 20 years and I would really love it to succeed, but papercuts like these need to be solved before I can recommend it even to technically open-minded friends.

> But like... at a basic level, "I'm hosting a Jabber server for my small community" has a lot less headaches than with Matrix. Yes if your server goes down then you lose the chat. Oh no. Plenty survived off of IRC IMO.

It might be great for that, but by the same token it's quite terrible as a persistent personal messaging handle. Durable identity/handles shouldn't be so bound to a community, since it makes it very hard to switch and you need to put an incredible amount of trust in the admin(s) as a result. (This is a tangent to the Matrix vs. XMPP point, as both have the same issue, as far as I can tell.)

Ideally, I'd like to have [email protected] as my persistent XMPP ID that I can freely migrate across servers just by updating a DNS record without having to worry too much about who is actually hosting the server. The AT protocol does this right.

Re:Jabber/XMPP: 25 Years of Digital Independence by rtpg on Tuesday August 25, 2026 @06:58AM (#49431787)
> Ideally, I'd like to have [email protected] as my persistent XMPP ID that I can freely migrate across servers just by updating a DNS record without having to worry too much about who is actually hosting the server. The AT protocol does this right.

I suppose here you're saying "I should be able to do this without providers having to do work"? Like you show up with [email protected] to bar.com and create an account, and everything kinda fits into place (modulo you having to set up some DNS?)

It is already possible of course to have XMPP server at domain A handle things for domain B as well. But it is cool how ATProto seems to really bake in the concept of "all domains are welcome".

Re:Jabber/XMPP: 25 Years of Digital Independence by lxgr on Tuesday August 25, 2026 @10:07AM (#49434406)
Not quite. I'd like to have [email protected] hosted at xmpp.foo.com today, but if foo.com shuts down unexpectedly one day, I'd like to be able to redirect it to xmpp.bar.com.

I might lose my chat history and maybe my contact list if I don't have a local backup of it, but people would still be able to reach me as [email protected]. Ideally, I'd be able to upload my local, end-to-end encrypted backup to xmpp.bar.com and continue exactly where I left off.

AT proto's main innovation to me is decoupling the concerns of user identifier and data host at the protocol level, in the same way that DNS and my web or mail host are decoupled.

Re:Jabber/XMPP: 25 Years of Digital Independence by goffi on Tuesday August 25, 2026 @10:56AM (#49435281)
Hey. I'm currently working on this: https://xmpp.org/extensions/xep-0516.html
Re:Jabber/XMPP: 25 Years of Digital Independence by lxgr on Tuesday August 25, 2026 @12:08PM (#49436385)
This is awesome, thank you!
Re:Jabber/XMPP: 25 Years of Digital Independence by rtpg on Tuesday August 25, 2026 @10:05PM (#49443306)
I mean apart from the uploading of the backup xmpp already lets you do this right? That's my impression at least. Maybe I'm misunderstanding something.

(The premise in my understanding is that you own example.com and control its DNS records right? And not "well I hosted on foo.com as [email protected] but it went down and now I want to move")

Re:Jabber/XMPP: 25 Years of Digital Independence by account42 on Wednesday August 26, 2026 @03:54AM (#49445410)
> Eh, last time I tried I still got leftover notifications for messages I had long read and even replied to on a different client hanging around on my other devices.

What server and client(s)? I have not seen this issue with ejabberd + Conversations. Might also be a matter of enabling the right extensions on the server.

Re:Jabber/XMPP: 25 Years of Digital Independence by regularfry on Tuesday August 25, 2026 @04:51AM (#49430809)
I found snikket to be pretty much perfect for the use case I wanted, which was something locally-hosted I could drop in a VM so I had a channel for talking to bots that didn't need API keys for third party services.

The only downsides I've experienced are:

1. Images and accompanying text get separated, which turn-based bots get confused by. I seem to recall there's a standard for this but it's not implemented.

2. XMPP support isn't common in claw-type agents so I've had to patch it in. Not a terrible experience overall.

I had a look at Matrix but bounced off Element, hard.

Re:Jabber/XMPP: 25 Years of Digital Independence by lxgr on Tuesday August 25, 2026 @04:56AM (#49430858)
> XMPP support isn't common in claw-type agents so I've had to patch it in.

I found this pretty baffling/sad. Why do these agent harnesses have messaging plug-ins for the most obscure messaging platforms but not XMPP? It seems like a no-brainer!

People would apparently rather pay for a second number/SIM/phone dedicated to Openclaw on WhatsApp and suffer periodic outages due to Meta actively discouraging automation use than set up a minimal XMPP server and client...

Even setting up Matrix (at least with E2E encryption) was incredibly painful. It worked in the end for me, but the amount of tokens I've had to burn... And I don't even want to think about the next update.

Re:Jabber/XMPP: 25 Years of Digital Independence by singpolyma3 on Tuesday August 25, 2026 @09:08AM (#49433368)
Submit patch?
Re:Jabber/XMPP: 25 Years of Digital Independence by regularfry on Wednesday August 26, 2026 @10:18AM (#49449686)
I did this on one project but things moved fast enough (and I've had too much going on) that I couldn't go round the review cycle fast enough and keep it architecturally aligned to get it merged.
Re:Jabber/XMPP: 25 Years of Digital Independence by account42 on Wednesday August 26, 2026 @03:46AM (#49445363)
> Yes if your server goes down then you lose the chat.

Don't all actively maintained servers support persistent message archive management now?