Gregory's Server@macberg @smxi @tarajdactyl @malcircuit The fundamental problem with matrix is also it's supposed strength: tt's a base protocol with a set of extensions.
In theory, most of not all of the problems mentioned are solved by some extension or another. However, there's nothing forcing people to implement extensions and it often takes a while if it happens at all. The moment you have a client/client or client/server mismatch, you end up with the lowest common denominator which is often pretty low.
This is especially bad when it comes to crypto and authentication schemes. Every client and server has some set which it supports and some set which it rejects because it doesn't think they're secure enough and some set which it doesn't support yet because developers don't have time or someone's software is out of date or whatever. The end result is a comedy show of random authentication failures because they can't all agree on a common trusted and implement crypto/auth pair. 🙃
It also shows up in other features but then it usually degrades to "you can't do that" and not "message failed to send" for something that's just text.
@faithisleaping @smxi @tarajdactyl @malcircuit Oh yikes. That thing about protocol extensions sounds like a bad design choice if you're trying to create an entire network that is compatible with itself. Or at least it sounds like they made the base protocol way too bare. That's sad to hear. I'm still hoping it can be fixed though because I like the idea of matrix.