I’m looking into hosting one of these for the first time. From my limited research, XMPP seems to win in every way, which makes me think I must be missing something. Matrix is almost always mentioned as the de-facto standard, but I rarely saw arguments why it is better than XMPP?
Xmpp seems way easier to host, requiring less resources, has many more options for clients, and is simpler and thus easier to manage and reason about when something goes wrong.
So what’s the deal?
Xmpp is old and has no traction. Matrix is new and there are many people believing in it. There is a lot of money put on matrix. A lot of people want matrix to succeed. Especially companies, agencies and governments love matrix. Jumping on a train that already moves forward is easier than trying to push a standing train.
With xmpp, or signal I’ve got all my messages on my device. Distributing the info to other devices is difficult. With matrix everything sits on the server and distributes the info to the clients. That’s like my file cloud, or my photo cloud or my music server, or my document server. Everything is saved centrally on a server and all is independent of the consumer device. I can use multiple devices and everything sits on the server. That’s great for me as a user, it’s easy.
Xmpp is scattered which is great on one hand but matrix development is moving very fast. Xmpp can’t compete with that.
What’s the advantage of xmpp over signal for the end user?
It is true that Matrix follows a fat server model, but multi-device usage works perfectly well in XMPP these days.
I can use my published PGP keys with XMPP, for starters. And I can use OMEMO. Matrix supports neither afaik.
Wut
If nothing else, there is space for a competitor to MS teams in the corporate space.
Everyone else is ending up on teams, but no one actually likes it.
Everyone ends up on MS Teams because they bundle it with Office365, so execs have the choice of “free” or another $12/mo/user for Slack. It immediately makes it a case of “justify how Slack is so much better we spend thousands on it when Microsoft gives us Teams for free”. Those execs don’t use chat software in the first place.
That’s why the EU forced them to unbundle Teams.
No, not always. I know of a very major firm that uses google suite for everything but chat and video calls. They use MS Teams because its just that much better than google’s alternative. From the chats Ive had, the issue with Slack there is that someone high up in their IT stack hates it.
Teams is relative.
At a previous job (Microsoft shop but in the public sector so 10 years behind), the standard messenger when I started was Skype for Business.
In case you’ve never used Skype for Business, it’s “Skype” in branding only and actually has nothing to do with the Skype software that Microsoft purchased and is more like MSN Messenger.
Compared to that, Teams is a huge step up.
Also, at a Microsoft shop, you have to use what Microsoft provides even though it’s usually balls.
It’s 90% of the reason I now refuse to work anywhere that’s bought into the Microsoft ecosystem. It’s just so… mediocre
It’s not because you compare Teams to something worse that Teams isn’t terrible.
Well, as far as I’m concerned Skype for Business set the benchmark for terrible. Teams isn’t even close to being that level of bad
I agree, but we should always compare to what is better and strive for that. Otherwise we get the situation today where the argument to take a product over another is that it’s less bad than the old one
has many more options for clients,
The problem of XMPP is here. These options are not uniform among the possible different combinations of servers and clients.
The situation has improved a lot, but there was a point in time where saying “this is my XMPP handle” was far from enough to know if you’d be able to communicate with others, and you’d have to figure out things like:
- Does the server support MUC?
- Does the server support E2E? If so, which?
- Are emojis supported on the server, or do they get converted to ASCII?
- Can you use audio calls? If so, which codec?
- If my client supports “share live location”, what do you see on your end?
Not to mention that until recently there was no decent XMPP client for iOS. Even today, the best alternative is siskin, which may have its vocal fans but quite frankly is pretty barebones and has a UI that would be considered ugly even in 2010.
Matrix as a protocol is technically worse than XMPP and Synapse is a resource hog compared to Prosody and Ejabberd? Yes, true. But at least I can tell non-technical people to download Element from the App stores and they will have a consistently-not-great-but-acceptable-and-improving experience.
This is the correct answer, IMO.
I loved using XMPP back in the day, but I struggled talking with people who weren’t on the same server as me because of spec and client variations.
While Synapse is a resource hog, it (and Element) - to a certain degree - does the job. Can’t wait until sync v3 lands in the main server.
The only issue I have is with one friend who insists on deploying his own version of Synapse, but can’t figure out coturn and - as a result - we can’t voice chat properly.
Goddammit. Two steps forward, one step backward. 😅
Funny I just launched Conduit this morning. Seems to work better than Synapse and is supposedly lighter.
Conduit sounds very exciting - but my synapse installation (and its concomitant database) is too old and big for me to make a switch to anything else just yet.
But I’m hoping Dendrite will one day allow me to migrate over - I don’t like how one of my most mission critical programs is a Python program running out of a packaged venv. 😅
Suggest your friend to give Eturnal a try maybe. I have it running on an Oracle free tier instance, and I use it daily to have video calls with my family using Synapse/Element (and Jitsi inside Element for group calls), and it works great. The documentation is very good too.
Edit: this is my Eturnal config, for reference:
eturnal: listen: - ip: "::" port: 3478 transport: udp enable_turn: true - ip: "::" port: 3478 transport: auto enable_turn: true - ip: "::" port: 5349 transport: tls enable_turn: true realm: turn.<MY_DOMAIN> tls_crt_file: /etc/letsencrypt/live/turn.<MY_DOMAIN>/fullchain.pem tls_key_file: /etc/letsencrypt/live/turn.<MY_DOMAIN>/privkey.pem tls_options: - no_tlsv1 - no_tlsv1_1 - cipher_server_preferenceAnd the compose file:
services: eturnal: container_name: eturnal image: ghcr.io/processone/eturnal:latest environment: ETURNAL_RELAY_MIN_PORT: 49160 ETURNAL_RELAY_MAX_PORT: 59160 ETURNAL_RELAY_IPV4_ADDR: <REDACTED> ETURNAL_RELAY_IPV6_ADDR: <REDACTED> ETURNAL_SECRET: <VERY LONG RANDOM STRING> volumes: - ./eturnal.yml:/etc/eturnal.yml:ro - /etc/letsencrypt:/etc/letsencrypt:ro restart: unless-stopped read_only: true cap_drop: - ALL security_opt: - no-new-privileges:true network_mode: hostOoh, I’ll tell them to try it out - looks cool, cheers!
But at least I can tell non-technical people to download Element from the App stores and they will have a consistently-not-great-but-acceptable-and-improving experience.
Conversations on Android looks and feels like any other modern messenger and supports basically all the XMPP features there are. And I found Monal on iOS to be pretty usable as well, when I tested it 3 years ago.
Yes, Monal is catching up to Siskin fast, but until recently didn’t support a/v calls which is why many people still prefer Siskin.
As for a unified system, have a look at https://snikket.org which offers a one-stop solution under a single brand similar to Element. It uses lightly modified versions of Conversations, Siskin and Prosody (as a server) under the hood.
Conversations on Android seems to be the default answer for “advanced client”.
But for everything else… look at Monal’s blog, they only added support to audio calls in October of last year. Nice to see it’s still being developed, but “too little, too late” seems fair.
The other XMPP client for iOS called Siskin has had a/v calls for many years now.
Yeah, I mentioned it in the first comment. But seriously, it looks like something built in 2009. It might be functional, but only a die-hard XMPP fan would be interested in using it.
Many people have not used XMPP in years or never and go by hearsay of outdated information.
Matrix on the other hand had several million Euros of venture-capital to fund a marketing campaign.
This makes matrix even less attractive to me lol. But you’re right, that’s a very good point.
several million Euros of venture-capital to fund a marketing campaign.
Citation needed. Matrix was funded by Amdocs initially, then got investment from Automattic and has gotten some contracts from European Governments, but AFAIK there is no “VC investment” and there certainly aren’t “millions to fund marketing”.
They do have better marketing than any XMPP developer, though. You basically don’t hear anything from process.one or the Prosody devs.
As unpopular as VC funding is in some circles, the Matrix community owes a huge debt of thanks to Element’s investors (Status, Notion, firstminute, Dawn, Automattic, Protocol Labs and Metaplanet) and Amdocs for funding over $50M of work on both Matrix and Element since 2017.
Ok. I lost track of their funding. Seems like they raised $30M in a series B round in 2021.
Still, look at the timeline. 2021 is not that long ago, and Matrix was already ahead of XMPP in mindshare by then. It’s not really fair to say that this money was only spent in marketing, and it is not fair to say that without it XMPP would be making some comeback.
I didn’t say it was only spend on marketing, but they sure send a lot of people to developer conferences everywhere and offered “free” services to many open-source projects with that money.
They were doing that before 2021. Even acquired gitter and ported it to Matrix.
Yes and they had plenty of funding from highly questionable sources before 2021 as well. Even if you only take the 20 million difference in two figures mentioned above, but Element also partnered with a really shady crypto-currency startup in 2018, which had its own sources of investor funding.
Sorry, but now this is starting to sound like sour grapes.
Ok, they got a good amount of funding. But that alone is not enough to justify how they managed to gain as much mindshare as they did in relation to XMPP.
Element’s funding in 2018 or 2021 did not steal any opportunity for (e.g,) snikket to work on their product. Element following the “cathedral” model allowed them to be faster in the development of multi-platform clients, while the XMPP devs were all fixed to the Bazaar ideal, and because of that absolutely failed to deliver a modern application in the platform that is used by half of mobile users in the US.
We (techy types) tend to ignore things that end users care about and we are a lot more forgiving with systems that we see as “technically superior”, but the market cares a lot more about things like “Can I send emojis without having to worry about what client people use?” then “synchronization model or disk space requirements”.
This is not just “marketing”, this is “having someone with actual business and product sense”.
If it was up to me, sure I’d wish that more people would be using XMPP. But in 2019 when I told my parents that I wouldn’t be using WhatsApp anymore and that we needed a different app if they wanted to have video calls and see their grandchildren, XMPP was not even a choice for my iOS-using father, and Element (née Riot.im) was at least usable.
They do have better marketing than any XMPP developer, though. You basically don’t hear anything from process.one or the Prosody devs.
XMPP developer https://gultsch.social/@daniel does a good enough job at that imho
Thos, exactly this. Whenever I ask the question OP asked, it’s always some people who used some ancient client in 2008 and never bothered to try again. And then Matrix came to existence with their marketing and they happily started using it, even though it didn’t have any better features
it’s always some people who used some ancient client in 2008 and never bothered to try again.
The biggest hurdle for widespread adoption of open platforms, imo.
Holy shit, that explains how this piece of embarrassment has conned actual people into using it.
I don’t think you can pick out any one reason. XMPP is very old and has extensions for a huge variety of features. Many people have experience with older versions which had many major missing features (such as strong multi-device with offline support and server-side history) and a lot of the “hype” has died out long ago.
Matrix is new and made a lot of decisions that really helped its popularity.
- Having a HTTP-based client-to-server protocol makes web clients very easy to make.
- It is based on sync and merging rather than messages which moves some difficult problems (like multidevice and server-side history) into the core protocol meaning that it works well out of the box.
- Having HTTP based protocols make hosting it familiar for many people.
- The “default” Element clients have lots of features out of the box, features that for a long time were not always present on XMPP servers or clients. This gives a more consistent experience.
We will see what the history holds. Matrix is still very new and maybe the hype will die out and we end up moving back to XMPP. Or maybe something new. Overall I don’t think there are major fundamental differences. I think Matrix making graph sync the core primitive to build off of was a good idea, but in practice I don’t think it matters much.
You say that XMPP is much lighter. But I think that is mostly due to Synapse not being very efficient. Other implementations are fairly light. Even then my Synapse is using fairly small amounts of resources. You should also check that you are making an apples-to-apples comparison with large rooms, media and message history like you would typically see in a common Matrix server.
You say that XMPP is much lighter. But I think that is mostly due to Synapse not being very efficient. Other implementations are fairly light. Even then my Synapse is using fairly small amounts of resources. You should also check that you are making an apples-to-apples comparison with large rooms, media and message history like you would typically see in a common Matrix server.
I have a Prosody server running with about 10 concurrent users (friends/family). I just checked and it’s using 32M of RAM, local storage is in the megabytes. The database I’m using as a backend for message history and such is about 70MB. The only other data is temporary cache for uploaded media, which varies depending on what’s uploaded. How does that compare with a typical Matrix server for friends and family?
My Synapse install is using 94MiB of RAM and 500MiB of database disk space. CPU usage is effectively zero. I only have a 3 active users but decades of conversation history for myself (imported from other services). An uncompressed
pg_dumpof the data is about 250MiB which is within an order of magnitude of the raw text that I have in it. Nearly all of the conversations are encrypted so it wouldn’t compress much.Given that just running
pythontakes 13MB of RAM it probably isn’t using many resources past loading the code. At least at small scale running a Matrix server is not a notable resource burden for most people. A Matrix server written in a more efficient language (like Conduit) would likely be fairly similar to an XMPP server written in the same language. Either way unless you are hosting thousands of users it doesn’t seem like this is a major problem for either protocol.It should be noted here that Synapse resource use is highly dependent on the specific usage and can easily blow up if even a single user is joining a lot of large popular rooms on the Matrix network. XMPP has no such issue and scales pretty linear with user number.
How did you manage to convince friends and (especially) family to actually use Matrix? Quite impressive!
Google killed XMPP momentum. And while Matrix has many issues it needs to figure out, especially the development being almost exclusively supported by a for-profit company, they seem to slowly (very slowly) work towards more independence.
Matrix did some things right. Going with JSON spec instead of XML, having Element as uniform cross-platform client, offering bridges as a way to stay connected with your family and friends without needing to convince them to move (XMPP offers transports, but they function entirely differently) and offering end-to-end encryption by default.
XMPP in true open source fashion doesn’t have any uniformity from user perspective. Different ways to do the same thing on different clients, different clients on different platforms. That is a benefit for a savvy tech nerd, but it’s a huge inconvenience for a non-techie family member or friend.
Why is JSON better than XML? It’s more modern, sure, but from technical perspective it is not objectively better right? Not something worth switching protocols for.
You mention XMPP has transports as opposed to Matrix bridges. I thought they give you roughly the same outcome. What’s the difference?
The only things JSON has over xml is that it’s easier to write a parser for it and the format is less verbose and less complicated. There are extensions to JSON that can add features that xml has and the JSON spec doesn’t have. Overall the xml spec is bigger and has more features but that also makes it overkill for many of the cases that it would be used in.
Why is JSON better than XML? It’s more modern, sure, but from technical perspective it is not objectively better right? Not something worth switching protocols for.
XML is unnecessarily complicated. By trying to cram everything into the spec, it’s cumbersome and hard to parse.
You mention XMPP has transports as opposed to Matrix bridges. I thought they give you roughly the same outcome. What’s the difference?
The goal is the same, but the way they archive that is different. For transport to work, you need an account on each platform you are using the transport on. It relays the messages through that account by mimicking the client. While bridges work by relaying the messages between rooms and not specific users.
My understanding is limited, so if you are interested, please do your own research.
Most Matrix bridges to commercial chat systems also require accounts on those networks. That’s the only way to make them work on most of these systems.
I guess you are specifically referring to the Matrix to Discord bridge that does work like you describe, but a similar bridge has existed for XMPP to Discord in the past but is currently broken and unmaintained. The currently working XMPP to Discord transport does require you to puppeteer a personal Discord account, but that is rather because of a different focus of the used transport framework than any technical limitation of XMPP in that regard.
All platforms that don’t have public API access will require a way to relay that information, but I was talking about the difference in how the messages are relayed. Matrix bridges work fundamentally on each platform/protocol having its own room and relaying the messages through the bridged room instead of the user as XMPP does. That’s why you can relay the same messages to multiple rooms on Matrix, but can’t do the same on XMPP.
No, that is only an implementation detail, you can easily do a very similar thing with XMPP group-chats.
In fact the way Matrix does it is a major limitation and the source of an endless amount of issues with their IRC bridge.
cumbersome to parse
Parsers have already existed for so long in every major language. Why need to worry about parsing?
And why need to worry about transports working differently if they achieve the same thing? They seem similarly convenient if I understood what you said correctly
Additionally, libraries for XMPP exist in most languages, there is a varying degree of completeness, but they all do a good job of hiding XML from the programmer
I’ve been an XMPP user for decades. I use it daily to talk to all of my friends and most of my immediate family, so I’m certainly an advocate for it.
I think in the simplest terms Matrix gets mentioned more often because it’s newer and it’s development has largely been driven by a corporation with significant funding. XMPP had similar corporate sponsors years ago, but a lot of them moved on. The XMPP community isn’t gone, though, and XMPP development has continued.
As others have said, it’s true that XMPP had some difficult issues in the past with various clients only supporting certain extensions (XEPs), which meant what worked on one client may not work on another. This problem isn’t nearly as much of an issue nowadays, but it was frustrating in the past. There are official compliance suites that clients and servers can use to ensure they meet the base features for a particular purpose, so that has helped in that regard.
To me, XMPP is preferable because it’s a messaging protocol, not a giant graph database of all social interactions. I don’t need or want that. The main XMPP server software does handle message history that is synced across all devices, but this is often user configurable and none of that information is needed by or shared with other servers. MUCs are not replicated across the network, but only exist on the server that hosts them. While this does mean that server is a single point of failure, it’s much simpler to operate and, at least in my opinion, is better from a privacy perspective.
Traditionally XMPP, albeit with propriety extensions, has been used as the basis for a large number of messaging platforms. Google Talk was XMPP. Facebook Messenger was XMPP. WhatsApp still is XMPP, as far as I know. Kik is also XMPP. Google and Facebook’s platforms may still use XMPP, but I don’t know for sure. It certainly works as a messaging platform for lots of users, but without all the VC money, development is pretty much only done by volunteers or client developers that offer paid builds of their clients (like Conversations on Android).
I am hosting both XMPP and Matrix now, and my main concern with Matrix is storage. I am afraid it would eat up the very limited disk space I have on my VPS. Conduit offers no built-in way to clean files up, and media is stored in a weird way that makes it a PITA to see which ones can and cannot be deleted. I now know that neither the database files nor the media can be just deleted.
I sorta like the idea of a chatroom existing on more than one server, but that MUST have been opt-in or at the very least opt-out.
pidgin still doesn’t support omemo
Pidgin’s XMPP support hasn’t been updated in more than a decade*. Please don’t use Pidgin for XMPP! It lacks so much more than just not supporting e2ee via OMEMO.
*apparently they recently started working on a full re-write of it for an upcoming version, but it is slow going.
Show me a docker compose file which I can simply start and don’t have to mess around more than deploy it, and I will discuss xmpp more often.
Here is a docker compose: https://snikket.org/service/resources/docker-compose.yml
You only two configuration options in the config file: domain and email.
OK, I’ll give it a try. Thanks.
I’ve tried Snikket a few years ago. Nice project. 👍
I never tried hosting matrix because it was rumoured to be a bitch to host.
I don’t think XMPP is simpler than Matrix. With my insufficient knowledge; XMPP servers and clients have different standards. Some supports audio/video calls, some requires encryption while other maybe not etc.
Matrix has a standard set of features and all software around it built for those features. TBH I find Matrix pretty instable lately tho.
I was under the impression that there is only one Matrix server implementation. Standards are not really required in that situation.
There’s way more and I already tried three implementations while trying to get a set of features I need. It’s a wild west out there and the resource usage is way higher than e.g. hosting Prosody. Seemingly it has to do with chatrooms being a full mesh, but my single user server consumes about 700mb RSS and 2.4 gb VSZ which is kinda high.
XMPP servers and clients have different standards. Some supports audio/video calls
And the same is true about Matrix lol
Yes, you can shoot me from there and you’re right but I don’t see much difference between Matrix clients. The experience is pretty common between them. Synapse is de facto standard.
Matrix clients are simple, easy, and nice to look at. The matrix server might need more resources, but it comes with everything out of the box. There’s no need to fiddle with extensions and their weird naming, and hope that the other server/client also supports the extension. Also, are there bridges to other protocols?
I remember trying to get encryption working on Pidgin and it was all around a bad experience.
XMPP might be as powerful or more powerful than matrix, but nothing about it screams modern. It’s like IRC for Gen X’ers.
You are basing your experience on Pidgin, which is the worst possible choice for an XMPP client that hasn’t been updated in over a decade. Other XMPP clients are relatively modern looking and easy to use, including encryption (probably easier than Matrix for most users).
I looked at Dino and another one mentioned here and they look dated. Windows 95 feel with better anti-aliasing, rounder corners, but same colors? Gtk 2 or something?
Pidgin was my messenger of choice to communicate with people on facebook, gmail, and a few other protocols back then.
But yeah, my experience with XMPP wasn’t good and if they don’t have bridges, there isn’t much of a reason for me to switch right now. It doesn’t seem to provide any advantages over Matrix.
Dino has an intentionally simplistic design, but it doesn’t look “dated” at all. Gajim or Movim both look pretty modern and similar to Discord etc. these days.
And XMPP has bridges to pretty much all major commercial networks, it just doesn’t have a major centralized provider of them that in exchange siphons up all your personal data like Element & Beeper does. But you can easily self-host the available bridges for XMPP.
Dino has an intentionally simplistic design, but it doesn’t look “dated” at all.
That’s highly subjective, but I’ve shown some Gtk3 apps to people at work and the most expressive first reaction I got was “ew”. Dino and others getting that exact reaction wouldn’t be surprising.
it just doesn’t have a major centralized provider of them that in exchange siphons up all your personal data like Element & Beeper does. But you can easily self-host the available bridges for XMPP
And this is another reason why it isn’t prominent. “Grandma, all you need to do is host an XMPP server. It’s incredibly easy”.
You can easily do it for your Grandma. But your argument can be just as easily applied to Matrix vs. WhatsApp etc. If you use the centralized services of Matrix.org or Beeper then Matrix is just a very poor version of Discord.
I looked at Dino and another one mentioned here and they look dated. Windows 95 feel with better anti-aliasing, rounder corners, but same colors? Gtk 2 or something?
Looks like a standard GTK4 app to me. Whether or not that is to someone’s tastes is obviously subjective, but it uses the same design language as every other GTK app under the sun.
GTK apps always look out of place on Windows though. Looks far more sensible in its native environment (i.e. *nix running GNOME).
🤔 maybe GTK4 apps look dated to me. Didn’t realise that’s what GTK4 looks like.
The anti AI license is so lame.
If the goal is to make a similar experience to discord, we should make a desktop/android client which changes the way the info is shown. I boil down discords main features this: 1-to-1 call/text, modern messenger features (emojis, text, audio, video, link embeds), servers with the option for channels and always on voice chats, group chats (weird overlap with servers). Always on voice chats should be as simple as disabling notifying or dialing members. Is it not just that simple to get a heavily reduced version of discord? Maybe noisetorch for noise cancelation.
deleted by creator
I couldn’t find any decent XMPP clients that supported encryption and worked on both desktop and mobile without looking like they were made in 1995
For Linux and Windows, gajim works very well and is easy to use. It definitely doesn’t have an interface from 1995. If you need something easier for people on Linux, dino is even more streamlined and is extremely easy to use. I think there was an effort to make a Windows build too, but I don’t know how far along that is or if they are still working on it.
For Android Conversations is the gold standard. On macOS there’s Sikin and Monal, but I’ve never used them since I’m not a Mac or iPhone user. But all these clients support a wide variety of features including encryption.
It also doesn’t seem to function well as a Discord-like replacement, since I don’t want a separate “group chat” for every single topic. I want a central hub where people can then join pre-existing channels like you can in Discord and Matrix.
I’m not sure I follow you on this point. XMPP has had MUCs (Multi-user Conferences) which function similarly to chat rooms/IRC channels for a long, long time. The channels are accessible regardless of what server you’re on as long as your server is federating with the wider XMPP network. There’s even a searchable list of public MUCs at search.jabber.network covering a variety of topics. Most servers allow creating new channels if you want to start a new one, and anyone can join regardless of their server.
deleted by creator
Not sure what the problem with Gajim was. There’s a distro package already in Arch, although I usually use the AUR packages from git. I haven’t had any problem with either of them, though.
You should be able to limit MUCs so that they’re only for local users of a server and not accessible to people outside the server. Or, you can make them invite only, require a password, etc. So there are options there.
One-to-one video and audio chat works pretty well with XMPP. I don’t think group video/audio works, but I’ve never tried. I know that’s a really popular thing on Discord, so it’d be nice if XMPP had that too. I think there’s some work toward it, but I don’t know where that’s at.
Dino and Conversations weren’t good enough?
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters Git Popular version control system, primarily for code HTTP Hypertext Transfer Protocol, the Web IoT Internet of Things for device controllers VPS Virtual Private Server (opposed to shared hosting) XMPP Extensible Messaging and Presence Protocol (‘Jabber’) for open instant messaging
4 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #699 for this sub, first seen 22nd Apr 2024, 03:05] [FAQ] [Full list] [Contact] [Source code]
@Two9A@hachyderm.io
Missed the XMPP acronym. Probably needs to scan the title too
@onlinepersona Thanks; added XMPP. The bot should, in theory, pick up on acronyms used in post titles (if it knows about them beforehand); we’ll find out next time it’s mentioned, I guess.
I think it has more to do with Matrix is kinda becoming the standard for secure open source messaging server but I do agree with you I would just use what works for you personally.
Tinode and Snikket should be discussed too. They’re server and clients, built upon XMPP and including the many extensions, “XEPs” that an admin would want in order to give their users a modern experience.
Tinode is not XMPP/Jabber. It is not compatible with XMPP. It’s meant as a replacement for XMPP.
From their repo. it has AFAIK nothing to do with XMPP, they just use it as an SEO term.
I’m going to throw this out there not being sure how true it is, but I find it interesting to think about.
XMPP is much more widely used than Matrix if you count WhatsApp (Meta/Facebook). ActivityPub is much more widely used than AT Protocol and nostr combined if you count Threads (Meta/Facebook). So reasons why people aren’t talking about XMPP include not wanting to recognize that Meta is hugely influential in this space and that most people don’t talk about the underlying protocols of the services and tools they’re use at all leaving a self selected group of people looking for alternatives with traction that don’t depend on Meta. Outside of WhatsApp, there’s not a lot of traction with any particular XMPP implementation. And none of the XMPP implementations have a Discord-ish organization of chat rooms that’s popular and familiar right now. Matrix has both right now (although I don’t think it will ever be more than a small niche in the mobile messaging space).
I’m fine with using Matrix for what it is. There are programming language communities that have been very helpful for me and a number of Lemmy related communities that have been nice to be a part of.
WhatsApp is using a complete fork of the XMPP specifications and never had influence on XMPP. In the early days when Facebook messenger was using XMPP as a C2S interface they had a bit of influence but what you said used to be much more true for Google some years ago and what happened there is a major reason why people don’t want Facebook to become influential in ActivityPub (which it isn’t yet).
