@adfeno the matrix protocol is public and many are implementing clients and servers.
XMPP while first of its kind, is also heavily XML based and was largely developed without universal end to end encryption, or battery budget in mind.
Matrix corrects a lot of the XMPP failings that made it ineffecient and expensive to scale which is exactly why Facebook, Google, and others abandoned it for their large scale deployments.
@adfeno They intentionally didn't go the IETF route until all the major use cases are covered, however the IETF itself is in the process of moving to Matrix for their own internal use to discuss new internet protocols soooo.... Yeah.
The argument that “it's bad becaus of XML” is moot. Sure it does consume more resources depending on the message, but with the #XMPP #XEP for push notifications, it provides incentive for account providers to make those push services available for their own accounts, thus no longer depending on #GAFAM and such like.
Synapse is the proof of concept server, anyone is can make their own server code, Dendrite is one such example.
They just need to implement the different specs. This issue is that matrix is growing really fast and servers like dendrite are fairly new. There will soon be a time when dendrite catches up fully and only needs to add new features as and when they come.
@lrvick @adfeno This is not true. XMPP works really well in resource constrained environments (and actually, it was developed for it, according to xmpp.org) It does scale far better than current matrix implementations. Missing E2EE definitely is not a problem, as the core XMPP protocol is deliberately minimal. Facebook and Google simply don't want compatibility
@lrvick I don't know why then #Matrix team didn't register the standards officially with a standards body such as #IETF, #W3C, #ISO or #OASIS. This is my major point. Without this, #Matrix team can change the specification as they see fit, without anyone even having a way to say no, nor a test period.
@adfeno Hi there, why wouldn't you mention this topic on Matrix's official forum? I think it must be worth doing so.
@adfeno we are seeing the test period right now. They want to see how the published spec works at scale before they take on the overhead of locking it in stone with IETF.
Meanwhile the IETF itself is using Slack and considering Matrix because there is nothing better atm.
@lrvick @adfeno Using slack is new to me in that context. The WGs I'm active in (CBOR, CoRE, ACE) still use EMail primarily, Jabber for chat during meetings, WebEx during interims and MeetEcho (which integrates Jabber) for the full meetings. Matrix and Zulip(?) got trials at the last full meeting, and at least the Matrix bridge is still up.
Mastodon da Ecologia Digital.
Construindo o ambiente digital público ~ comum ~, em prol de um ‘movimento ambiental para a rede [Internet]” -> #ecodigital
"Tal como o meio-ambiente, o domínio público (ou comum) precisa ser 'inventado' antes de ser salvo." - James Boyle, criador do ‘ambientalismo para a rede’