Actually in terms of integrations and bridges XMPP is better, it was built for that from the very beginning, when it was perceived that there’ll be many-many proprietary IM networks and XMPP users will use bridges for those.
Sadly it’s losing popularity, but I don’t see Matrix popularity growing that fast or being that stable to say that it’s more relevant.
Personally I don’t like Matrix because all its clients I tried were for whatever reason very slow, fetching history was somehow a computatively-intensive task for them. So it’s just purely user perspective.
But I’ve seen its API, and that seems very nice and easy to use.
While XMPP has that, eh, 2000s industrial feel with lots of XML and extensions with bland numbers. Still, it’s now pretty clear which extensions are expected to be used by everyone, and it has nice clients like Psi.
Yeah so does Matrix but that doesn’t mean everything Element adds as an extension magically becomes standardized.
As if every Matrix client supported all of it.
All of them support E2EE.
XMPP has voice and video calling
Source? Closest thing I could find is “Jitsi exists and uses XMPP under the hood”
Just as good as “not JSON based”
Obvious bandwidth reduction and ease of parsing aside I think JSON is better because it forces you to be intentional about how you add a protocol extension.
Why Matrix when we have XMPP?
More modern and offers broader usecases
Not a reason.
Elaborate?
Felt like since matrix was newer, it was more setup for all the integrations and bridges and the e2ee out of the box.
But since you forced me to read again about xmpp I’ve come back with this comment.
Yes, I agree with that.
Actually in terms of integrations and bridges XMPP is better, it was built for that from the very beginning, when it was perceived that there’ll be many-many proprietary IM networks and XMPP users will use bridges for those.
Sadly it’s losing popularity, but I don’t see Matrix popularity growing that fast or being that stable to say that it’s more relevant.
Personally I don’t like Matrix because all its clients I tried were for whatever reason very slow, fetching history was somehow a computatively-intensive task for them. So it’s just purely user perspective.
But I’ve seen its API, and that seems very nice and easy to use.
While XMPP has that, eh, 2000s industrial feel with lots of XML and extensions with bland numbers. Still, it’s now pretty clear which extensions are expected to be used by everyone, and it has nice clients like Psi.
It is standard. The standard allows extensions. (EDIT: That one is standardized.) You should have checked first.
As if every Matrix client supported all of it. A very weird point.
XMPP has that too. You should have checked first.
Just as good as “not JSON based”. Weird again.
Yeah so does Matrix but that doesn’t mean everything Element adds as an extension magically becomes standardized.
All of them support E2EE.
Source? Closest thing I could find is “Jitsi exists and uses XMPP under the hood”
Obvious bandwidth reduction and ease of parsing aside I think JSON is better because it forces you to be intentional about how you add a protocol extension.
forgot these:
Not the same way, there are standardized XEPs for XMPP. One may not support and not use them, yes.
Well, every time I’ve used XMPP recently I’ve used OMEMO, so there’s no practical difference. Every modern client supports it.
Jingle - XEP-0166.
XMPP has compression.
OK, suppose so, not being a developer I still think I’d just use libxml for this and json-c for that, but OK.
WDYM?