I do think the EU should start with a more basic app like FluffyChat in testing but rebranded, then try to make their own app over the Matrix protocol that fits their specific communications needs and share that development publicly with open source.
The biggest problem with XMPP is what various servers and clients implement is kind of all over the place. For instance, most clients support an older version of OMEMO, but some clients support newer versions, and the different versions are incompatible.
The other issue is some platforms (iOS in particular) have pretty shitty XMPP apps filled with bugs.
I still generally like XMPP more than Matrix since ATM Matrix clients are also filled with bugs/laggy, Synapse (the main server implementation) is very resource heavy, and message syncing is kind of shit if the client doesn’t implement sliding sync (like FluffyChat). I personally think the UI for both XMPP and Matrix clients generally kind of suck, which isn’t great for convincing non-techy people to use them.
I mean, matrix is similar. So many official features aren’t supported by various clients, and then there are non official features that the clients do support, that aren’t supported by the official clients.
But matrix or XMPP, that problem is easily enough avoided at the “government rollout” level by standardising on a particular client and server combination
Matrix is fragmented too, but it’s generally less fragmented in my experience (if you use a relatively well developed client). Part of this is because most people just use Synapse for their server. With XMPP, server implementations support random combinations of XEPs, and specific servers often are missing random XEPs because they’re not enabled by default and so on (thinking about ejabberd for instance here, the default config probably isn’t what most people want). I also routinely have random compatibility problems between clients pop up with XMPP. As a basic example, retracting messages is very haphazard.
Anyway, yeah, if they standardize on server and client setup for all govt instances, it’d be fine either way probably. The clients may be somewhat janky, but they can probably fix those issues more easily when they’re only focused on one client (although unless it’s like FluffyChat and cross-platform, they may need to standardize multiple clients) and server.
It’s good to have an easy model for communication between members of different trusted organizations without requiring everyone to create a new account on a different server.
I’ve heard element, the common server software and even the protocol itself are also simply meh as well … That’s not a great start… And the name alone is a huge problem for adoption
Matrix is good. Element is not. It is a terrible application filled with bugs that ends up limiting the quality of other client applications.
I do think the EU should start with a more basic app like FluffyChat in testing but rebranded, then try to make their own app over the Matrix protocol that fits their specific communications needs and share that development publicly with open source.
German military uses matrix with their own messenger.
https://play.google.com/store/apps/details?id=de.bwi.bwmessenger
Didn’t XMPP already solve these issues a long time ago?
The biggest problem with XMPP is what various servers and clients implement is kind of all over the place. For instance, most clients support an older version of OMEMO, but some clients support newer versions, and the different versions are incompatible.
The other issue is some platforms (iOS in particular) have pretty shitty XMPP apps filled with bugs.
I still generally like XMPP more than Matrix since ATM Matrix clients are also filled with bugs/laggy, Synapse (the main server implementation) is very resource heavy, and message syncing is kind of shit if the client doesn’t implement sliding sync (like FluffyChat). I personally think the UI for both XMPP and Matrix clients generally kind of suck, which isn’t great for convincing non-techy people to use them.
I mean, matrix is similar. So many official features aren’t supported by various clients, and then there are non official features that the clients do support, that aren’t supported by the official clients.
But matrix or XMPP, that problem is easily enough avoided at the “government rollout” level by standardising on a particular client and server combination
Matrix is fragmented too, but it’s generally less fragmented in my experience (if you use a relatively well developed client). Part of this is because most people just use Synapse for their server. With XMPP, server implementations support random combinations of XEPs, and specific servers often are missing random XEPs because they’re not enabled by default and so on (thinking about ejabberd for instance here, the default config probably isn’t what most people want). I also routinely have random compatibility problems between clients pop up with XMPP. As a basic example, retracting messages is very haphazard.
Anyway, yeah, if they standardize on server and client setup for all govt instances, it’d be fine either way probably. The clients may be somewhat janky, but they can probably fix those issues more easily when they’re only focused on one client (although unless it’s like FluffyChat and cross-platform, they may need to standardize multiple clients) and server.
Ding ding ding. Make a Discord/Slack clone that does screensharing and drag/drop file sharing and I won’t care if it uses XMPP or Matrix
So Rocket.Chat (which TIL can federate to Matrix)?
Did they just add that? Last I heard it was on the roadmap
I think there have been some attempts to do so, but they’re just not good enough (and/or end up dead after a while).
This is a case where federation is nice.
It’s good to have an easy model for communication between members of different trusted organizations without requiring everyone to create a new account on a different server.
XMPP is federated
Any matrix client available for both android and ios with video conference capabilities?
…
that might have sounded a bit too aggressive. My question is genuine. Family members needs.
Yeah. Compared to Teams, Matrix is fine. It’s just far from a powerful tool built by people who actually give a shit.
Rocket.Chat seems to be doing well in Europe as well; they recently released their own native matrix implementation.
I’ve heard element, the common server software and even the protocol itself are also simply meh as well … That’s not a great start… And the name alone is a huge problem for adoption
Element the server suite is fine - it’s just a version of Synapse with rust and Python bindings.