- cross-posted to:
- privacy@lemmy.ca
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ca
- privacy@lemmy.ml
You must log in or # to comment.
It’s worrying to see that it’s Matrix that’s gaining ground in IT, when IT people more than anyone else should know that XMPP is the better alternative, Matrix is a bloated nu-protocol in comparison.
hope this leads to money going towards Element open source development. it works but it’s not great right now
Honestly, federated FOSS makes so much sense for government communication, as it insulates them from reliance on corporate entities.
I just wish Matrix’s E2EE worked better. Even if you have all your keys managed probably, it’s still really unreliable.
When was the last time you used it? They’ve been working hard on fixing the encryption bugs, and it shows. I haven’t seen a glitch in… maybe half a year now?
I just wish Matrix’s E2EE worked better.
For “real-time communication” for individuals who don’t want to maintain their own communication infrastructure, the information around https://www.privacyguides.org/en/real-time-communication/ is surely at least somewhat useful. The recommendations might not be suitable for “government communication” or for people who are capable of setting up and maintaining a lot of infrastructure since I wouldn’t describe the infrastructure required as being easy to host independently: it doesn’t seem to be easy to set up 3 servers and make it possible to use them to communicate even if something bad happens to the communication network maintained by the original creators of the software. However, the Matrix protocol might be unsuitable for this too, since it is considered to be “social networking software” now, and it is no longer considered to be “great for securing your sensitive communications”: https://www.privacyguides.org/en/social-networks/#element
