| Disclaimer: I work on the project. Matrix started out with its early DNA in focusing on the problem of how to create a decentralised e2ee multi-client messenger. Getting that right took a lot of time and effort, which initially came at the expense of UX. Elsewhere in the comments, it is clear that there are not many (any?) similar projects out there that solve the same problem, especially to the level of maturity where it is trusted by governments and civil institutions around the world. So the effort was worth it, and we have the proof points to show that Matrix solves a real problem. Now we need to continue to work hard to create a UX that matches (perhaps exceeds?) the quality of the proprietary, centralised and non e2ee messaging apps that set the UX standards users have come to expect. This needs to happen both at the protocol level and in the client and server implementations. For me personally, this means Synapse and the Element clients, but we have many quality implementations in the wild. Matrix 2.0, mentioned above, is part of this initiative, though there is a lot of additional work in progress to both improve existing features (like Spaces and Threads) and add expected features, such as user status. The post calls out running on Dendrite, which, as a project not under active development, contributes to some of the problems. However, I would not want that to be an excuse, because there is legitimate feedback in the post overall. If someone reading this is new to the project and wants to host their own server, I'd recommend checking out [ESS Community](https://github.com/element-hq/ess-helm) - though other distributions exist. Thanks everyone for flying Matrix and sharing your experiences (good and bad), we're getting there. |
I am happy that Matrix has found a place in government organizations. For many individual users, Matrix currently solves no problem because they simply can not use it. I hope this will continue to change, I am cheering for you.