Decommissioning Matrix: Moving to XMPP for Instant Messaging
May 16 2021
With my recent announcement that I’ll be ending my personal Matrix service, there comes the added question: what now? For me it is a walk down memory lane, to XMPP.
Edit 2021 AUG 7: As much as I enjoyed XMPP back around 2010, the application ecosystem has changed a lot and there seems to be less support for XMPP now. I’m sorry to report that OMEMO wasn’t what I expected it to be either, and the major drivers for XMPP, to me, was being able to use Irssi or Weechat. That didn’t work out either and Profanity was disappointing. I’m leaving it with that and the fact that you can now again reach me on Matrix.
A list of the XMPP Extensions (XEP) is maintained at the XMPP Extensions website. There are currently 457 XEPs.
XMPP is a universal messaging standard which have been in active use for a long time. The same way it is challenging to use with different types of sub-standards, called XEPs, it is also a wonderful way to work with the ecosystem and different purpose-built clients. While Matrix was starting to build this ecosystem but had problems gaining momentum - especially for the CLI clients, XMPP has had a wide variety of support for different clients. Personally I found Profanity good.
For now I just wanted to share some details on how to get in touch via Jabber/XMPP after we have exchanged an email introduction via my contact page.
To get a JID (Jabber ID, XMPP JID, you can register at e.g. jabber.no.
When you have registered an account, and if you do not want a permanent presence on the network or do not want a desktop messenger, you may login through converse.js.
OMEMO, which is equivalent to Matrix encryption is defined in XEP-0384. I am particularly fond of the threat model described, the clarity of it. A recommended read.If end to end encryption is required for the conversation, which would make sense using third party XMPP servers - OMEMO can be enabled in converse.js.
Read with Gemini