mxisd

> they really have a highly usable product Setting up a Matrix server is a lot harder than you might think, especially when you start talking about federation and identity management. The mxisd[1] project has recently disbanded due to what I believe to be philosophical differences with the Matrix maintainers vision of identity management. I like a lot of things about Riot/Synapse, but I would suggest you try setting up your own Matrix server if you haven't yet. It's not what I would call highly usable. Mind you, I have only tried setting up the reference implementation (Synapse/Riot). I would be interested in seeing a write-up/comparison done by Mozilla as part of these trials. [1] https://github.com/kamax-matrix/mxisd

Matrix doesn't E2E encrypt everything, only certain rooms. It's not currently possible, but I suppose there's no technical roadblock to making a server prevent access to E2E encrypted rooms to meet FOIA requirements. As for user management, synapse has identity servers and password providers to form a complete authentication solution. mxisd[0] is a service that uses both to offer LDAP authentication, although it seems dead with no real replacement. [0] https://github.com/kamax-matrix/mxisd

Installing Synapse is very easy actually with Pip, however as this OP showed that using your own identity server is also necessity. FOr that you want https://github.com/kamax-matrix/mxisd

It seems like a few folks have been burned by the failure to put the spec before the implementation. Another example: Kamax provides mxisd[1], the only federated identity server (the official identity server is/was controlled by vector, and doesnt openly federate). They had to give up on mxhsd[2], their home server implementation due to spec inadequacies, and ended up forking the spec into Grid[3] [1] https://github.com/kamax-matrix/mxisd [2] https://github.com/kamax-matrix/mxhsd [3] https://gitlab.com/kamax-io/grid/gridepo