7 ms·
XMPP: The Gem of Instant Messaging
- snvzz 2y agoRefusal to do a flag day to implement ACK ultimately resulted in board dissolution, shitty unreliable protocol with zombie presences and lost messages. Eventually, the community just walked away, to IM systems that actually work somewhat reliably. This is how XMPP fell into irrelevance.
- MattJ100 2y agoI'm not sure what you mean. The XMPP Standards Foundation still has a Board, as that's required by the foundation's bylaws. "Flag days" in a decentralized network have to be used with caution. Ask whether it's better to communicate without a specific feature, or whether it's better to split the network into fragments which are unable to communicate with each other. The former is almost always preferable, however we used the "flag day" approach for mandatory server-to-server TLS, for example (which actually isolated Google Talk from the main network). As for acks, those were first defined in 2004, and have generally been implemented since the beginning in clients that need it (e.g. mobile clients, and every client since WiFi and laptops became ubiquitous). I can think of a number of reasons that XMPP is often overlooked when it comes to modern IM, but this is a weirdly specific thing to pick out, especially when I can hardly remember a time it wasn't implemented everywhere.
- snvzz 2y ago>still has a Board Of course it does. A different one. >"Flag days" in a decentralized network have to be used with caution. Yet sometimes they are necessary, even if they annoy people. Core issues need to be fixed. >As for acks, those were first defined in 2004, and have generally been implemented since the beginning in clients that need it I am not talking about read receipts or the like. I am talking about TCP connections assumed reliable. Protocol's messages sent, and assumed received. Not clients, but more seriously server to server. This is why zombie presences were widespread. >I can think of a number of reasons that XMPP is often overlooked when it comes to modern IM There really is but one. It was infamous for being seriously unreliable, and as people moved to actually reliable IM systems (majorly proprietary), they never looked back.
- skeptrune 2y agoI think the big issue with XMPP are the clients. Element is so much better that it's hard not to recommend Matrix to people despite its bloat and metadata leakage problems. JMP/Snikket for tying a normal phone number to your XMPP @ are really convenient, but the clients remain a problem. Plus, SIP dialers are not supported on IOS afaik. I am really surprised there isn't a venture backed company pushing XMPP forward. Maybe people have tried and realized it's not viable.
- singpolyma3 2y agoI'm curious which apps you've tried and what the deficiencies are you find in them. There are a number of companies in the ecosystem. Most have chosen not to pursue VC money in order to keep things going much longer. While a venture backed company can have success, most flame out eventually in my observation.
- gog 2y agoIs there an iOS app that supports push messages?
- singpolyma3 2y agoYes. Snikket, siskin, and monal all make use of push messages (since that's required to work on iOS at all these days)
- gog 2y agoIt looks like you need server support for that as well (makes sense), to bad Prosody doesn't have it in a released version but you have to build it manually.
- MattJ100 2y agoNo need to build anything, it's not a binary or anything like that. Prosody is just a very plugin-oriented project (plugins are written in Lua). For better or worse, we (the Prosody team) have certain standards for inclusion of community modules in the core codebase, and mod_cloud_notify doesn't quite meet them yet. On Debian and derived systems, you can just 'apt install prosody-modules', and on other systems you can 'prosodyctl install mod_cloud_notify' or otherwise download it directly: https://modules.prosody.im/mod_cloud_notify https://modules.prosody.im/mod_cloud_notify (no configuration is necessary apart from adding it to the module list in your config).
- mindcrime 2y agoI love XMPP. The phrase "the gem of Instant Messaging" really resonates here. I run an ejabberd instance and it works great. For anybody who wants to see a random interesting (well, interesting to some) application of XMPP, I recently put together a small demo of using XMPP with Jason[1] to connect AgentSpeak[2] agents to chat. https://github.com/jason-lang/jason/discussions/118 https://github.com/jason-lang/jason/discussions/118 [1]: https://github.com/jason-lang/jason https://github.com/jason-lang/jason [2]: https://en.wikipedia.org/wiki/AgentSpeak https://en.wikipedia.org/wiki/AgentSpeak
- aidenn0 2y agoWe evaluated some options at work for self-hosted chat about a decade ago. XMPP lost out due to the lack of a good iPhone client. Not sure if things are any better now.
- fsflover 2y agoDid you choose Matrix?
- aidenn0 2y agoMattermost.
- singpolyma3 2y agoThere are a couple iOS clients now but it's an area of active work for sure.
- lxgr 2y agoThere are now a lot of XMPP extensions to fit the mobile messaging use case better (usage of push notifications instead of a persistent TCP connection etc.), and at least two clients using them: ChatSecure (although the push server seems to be broken currently) and Monal. Due to the lack of anyone to chat with on XMPP, I can't really speak to the day-to-day usability unfortunately...
- zaik 2y agoMonal on iOS is making a lot of progress recently.
- Andrew_nenakhov 2y agoBtw we are working on a really great iOS client for xmpp. I think we'll release it in a few months.
- arcbyte 2y agoXMPP lost because the spec is overcomplicated and hard to implement. As a result, good clients never materialized and innovation was really hard to do. Everything in this article is an offshoot of the overcomplicated spec.
- pixelatedindex 2y agoIs there a “modern” equivalent to XMPP? How does it compare to the matrix protocol?
- singpolyma3 2y agoThe modern equivalent to XMPP is XMPP. Like every other healthy and alive protocol it evolves over time to meet new needs.
- xg15 2y agoIs it actually "alive" still?
- MattJ100 2y agoYes, definitely! Latest edition of the monthly newsletter highlighting various stuff in the community and ecosystem: https://xmpp.org/2024/11/the-xmpp-newsletter-october-2024/ https://xmpp.org/2024/11/the-xmpp-newsletter-october-2024/
- DennisP 2y agoGiven the context above, does that mean the modern version is no longer "overcomplicated and hard to implement?"
- SamWhited 2y agoI don't know that it was ever "over complicated and hard to implement" (see my response to the thing you're quoting above, I think), at least, not any more so than any protocol, but I'm still not really sure what the specific complaints are when people mention this, maybe you could elaborate on what's hard to implement? Most people just grab an XMPP library and go, you don't normally have to implement XMPP itself to make a client (just like you don't implement HTTP when you want to make a request, you go snag a library that does this for you).
- jeffnappi 2y agoXMPP and specifically ejabberd are what made WhatsApp possible to build with ~50 people at absolutely massive scale (~400M MAU @ 2014 acquisition).
- plussed_reader 2y agoSo really it's just about ZuckBook not paying forward via OSS?
- shortrounddev2 2y agoZuck didn't create whatsapp, he only bought it
- plussed_reader 2y agoGo on....
- WD-42 2y agoI really miss the days of being able to use pidgin to talk to everyone
- roflmaostc 2y agoHaha yeah. Within Pidgin I used ICQ, XMPP (over my own VPS), Skype, Facebook messenger, ... Now I have to use different apps for Signal, Element, Slack, Discord, WhatsApp, Telegram, ...
- WD-42 2y agoFacebook via xmpp was the last thing Facebook was good for. It was nice to be able to strike up the occasional conversation with an old school friend or acquaintance. It really does feel like everyone is online more than ever yet somehow more isolated.
- luplex 2y agoI can recommend beeper! I don't use it for encrypted messengers because I don't want to accidentally leak incoming messages that were sent with the expectation of e2ee. But it's great for catching a few of the odd ones.
- ptman 2y agoBeeper (built on matrix) has convenient bridges to lots of services. You can use the hosted service or self-host (https://github.com/beeper/bridge-manager https://github.com/beeper/bridge-manager) or you can host plain matrix using https://github.com/spantaleev/matrix-docker-ansible-deploy/ https://github.com/spantaleev/matrix-docker-ansible-deploy/
- aine 2y ago"plain matrix" sounds a bit wrong - we put great effort into maintaining numerous of components of the playbook, including bridges, so it has a lot to offer. Alternatively, you can just get a managed server on https://etke.cc https://etke.cc Disclaimer: I'm Aine of etke.cc, and MDAD is our project
- xg15 2y ago> With the wide array of XMPP clients available across all major operating systems (Linux, Windows, macOS, Android, iOS, KaiOS) ... One of those is not like the others...
- lxgr 2y agoI've recently looked at the suite of protocols underlying RCS (or so at least I think; the standards landscape is as confusing as ever), and it's baffling how the industry ended up with that when XMPP was... just there. The contortions they had to do to cram server-based federated instant messaging into the context of the SIP protocol stack by sheer force are something to behold. I can only assume this is entirely by design – the more needless complexity, the more opportunity to patent things (or at least keep competitors out): As far as I understand it, practically all carriers are just outsourcing the entire thing to Google.
- tiffanyh 2y agoI'm always reminded of this xkcd comic about standards. https://xkcd.com/927/ https://xkcd.com/927/
- deleted 2y ago[deleted]
- 8lall0 2y agoMeh. https://about.psyc.eu/Jabber https://about.psyc.eu/Jabber
- rom1v 2y agoMandatory blog post on XMPP and decentralized protocols: https://signal.org/blog/the-ecosystem-is-moving/ https://signal.org/blog/the-ecosystem-is-moving/
- zigzag312 2y ago> "XMPP still largely resembles a synchronous protocol with limited support for rich media, which can’t realistically be deployed on mobile devices. If XMPP is so extensible, why haven’t those extensions quickly brought it up to speed with the modern world?" So, it's not such a gem?
- zaik 2y agoMandatory objection to this blog post: https://gultsch.de/objection.html https://gultsch.de/objection.html
- LaGrange 2y ago> if anything the velocity of the entire landscape seems to be steadily increasing. It is, gods make it stop. "Oh no complicated specification" do you think you're getting paid 100k/year because it's _easy_? Gods.
- ValleZ 2y agoXMPP was not a mobile friendly protocol for a while, had efficiently no security out of the box and lacked simplest things like image or other file transfers.
- baybal2 2y ago[dead]
- shadowgovt 2y agoAnd nowadays it faces a marketing issue because it's extensible, so none of those problems go away because a solution exists somewhere. "Hey, I want to set up a modern messenger." "Sure! Here's XMPP, the ten extensions you need to enable and configure (problem left as an exercise for the reader), and the seven ports you need to open!" "... Okay? A Matrix node is apparently a drop-in solution; I'm gonna use that." XMPP is in desperate need of a Docker image that Just Works and the wizard to set up that Docker image. And then you need users savvy enough to have their clients configured correctly.
- zaik 2y ago> Docker image that Just Works https://snikket.org/service/quickstart/ https://snikket.org/service/quickstart/
- AshamedCaptain 2y agoIronically I think the absolute opposite. An XMPP server is something I can install on my ten year old home server without a second thought ( you have several to choose from even in debian's repositories) and expect it to work with minimal config. Matrix servers? You have mostly one implementation to choose from and it comes "packaged" as a monster container with several python modules likely already with CVEs and god knows what else. And then the resource usage...
- shadowgovt 2y agoYeah, it's great. One package that works and already knows all its dependencies. And thosev exploring the CVEs should generally find themselves in a chroot jail so not too much to worry about.
- upofadown 2y agoThe SMS gateway provided by jmp.chat has made XMPP fairly awesome for me. I have an XMPP client on all my devices and SMS contacts are just more contacts in my roster.
- qup 2y agoCan you explain how the gateway works?
- upofadown 2y agoYou get a phone number with the account. SMSs come from/to that number. You can transfer in a number if you want. You get some phone minutes as well. The basic idea is that you only need a data connection to your various devices. It eliminates the annoying need to type on your phone when you want to exchange SMSs with someone while you are on your laptop/desktop. Particularly helpful to people like myself who don't have a smartphone to type on.
- PokemonNoGo 2y ago> SMS contacts are just more contacts in my roster Sorry for the question but i don't really understand what this means?
- upofadown 2y agoA SMS contact is just a regular XMPP address. They show up looking like this: +15555555555@cheogram.com You would normally immediately add a nickname.
- xnx 2y agoXMPP was too open to be allowed to exist in any popular way. It's a miracle that SMTP still survives after so many attempts to "kill email" (Slack, etc.)
- cullumsmith 2y agoMy family uses a self-hosted Prosody instance with the Conversations app on Android and Dino/Gajim on the desktop. It works great. Combined with JMP.chat, we even get SMS and voice calls from the telephone network to all our different XMPP apps. Truly feels like the future. The technology of yesteryear seems to have more staying power. The protocols churned out by my generation seem destined for either VC/advertisement capture or death by CADT [0]. Maybe with the exception of Signal (so far...) [0] https://www.jwz.org/doc/cadt.html https://www.jwz.org/doc/cadt.html
- pbhjpbhj 2y ago"Cascade of Attention Deficit Teenagers" https://archive.is/t5m32 https://archive.is/t5m32 The host, jwz.org, redirects traffic linked from HN.
- kuon 2y agoI love XMMP and I use it in different contexts, but there is one thing I miss is GIF integration like discord. I guess I could try to write a gajim plugin to integrate tenor or giphy. This aside, it is much easier to integrate than matrix, things like web hook is just a POST request to /api/send_message... I think it would take off again with a nice crossplatform client with a discord like interface. But that would be expensive to develop.
- shortrounddev2 2y agoXMPP is nice, I like pidgin as a client. I'm not a fan of modern chat applications having such a focus on group messaging/channels; I miss IM-focused desktop messaging software. Unfortunately, getting people you know to actually USE your preferred chat software is more difficult than running an XMPP server. Often I've met people online or IRL and exchanged phone numbers with them only for them to ask to move to Discord, which I don't really like using.
- self_awareness 2y agoWriting bridges isn't a bad idea to fill the gap between old software for protocols nobody uses, and new protocols that have poor clients. For example, I'm writing this post with `vim` using `slrn` news reader, which uses a bridge that translates HN to NNTP (and vice versa).
- quantadev 2y agoThe key to getting a Messaging protocol "right" is to have the simplest possible post of a message to a server, and the simplest possible read of messages from a server down to like 20 lines of code, which Nostr did get right. Nostr is great because it doesn't tie your user name to some domain name that you don't own (like ActivityPub/Fediverse does). If a domain name is part of a user name, that ultimate gives "control" over your identity to someone else...(unless you're hosting your own domain, of course) I think XMPP is probably the superior protocol (better than both Fediverse, and Nostr, and I've written implementations in both), for some technical reasons, but as far as I know it takes way more than 20 lines of code to implement a read/write operation, so imo it's too complicated. Even ActivityPub looks simple at a first pass, but if you try to write your own server (like I did) you realize the protocol is a complete mess and compatibility issues are rampant across different sever implementations as a result.
- cyberax 2y agoI hope XMPP just goes away and stops distracting people from more productive avenues. It can't be fixed. It's dead. Matrix is the modern replacement. I used XMPP to implement a chat client within our application around 2012. It was a freaking nightmare. The roster system, the incompatibilities, the lack of standardized synchronization, the never-working group messaging.
- zaik 2y ago> It can't be fixed. It's dead. Lots of good XMPP implementations disprove this. I hope Matrix just goes away and stops distracting the FOSS community from improving existing internet standards instead of custom protocols by random startups :)
- cyberax 2y ago> Lots of good XMPP implementations disprove this. A list, please. For iOS, Android, macOS, Windows. > I hope Matrix just goes away and stops distracting the FOSS community from improving existing internet standards instead of custom protocols by random startups :) XMPP had its chance, it blew it.
- self_awareness 2y ago> XMPP had its chance, it blew it. It's not like Matrix is killing it. It's not exactly a new protocol, yet still feels like it's in the pre-alpha stage. Both protocol and the client/server software.
- rakoo 2y ago"I tried this thing 12 years ago and it sucked, therefore it still sucks today and will suck forever"
- deleted 2y ago[deleted]
- MongoTheMad 2y agoXML is the reason why XMPP is not widely adopted. XML is such a painful configuration structure.
- bigdumbape 2y agoXMPP is amazing. There was a neat white paper years ago about XMPP over HF radio. Long live XMPP.
- solarkraft 2y agoXMPP could’ve been great, I‘ve used it and the implementations have worked quite well. There have been revival/popularization attempts, but nowadays traction seems to be with Matrix. Unfortunately that spec also has big issues and the ecosystem is still struggling with usability (though it has improved a lot recently) and implementations. It’s an unfortunate situation in a time in which an open communication standard is more important than ever.