this post was submitted on 26 Jan 2024
28 points (96.7% liked)
Encrypted messaging
223 readers
1 users here now
This is a community to discuss FOSS encrypted communications.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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?
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.