I would have loved to use one of the alternative server implementations, but none of them supported both E2EE and SSO. It used an order of magnitude more resources than any other service in my entire infrastructure _at idle_ with no users and no federation. Synapse, by the way, is a real resource hog. Want to turn off federation _and_ make E2EE obligatory? Good luck! Even if you manage to get Synapse configured to work that way, you'll be delighted to discover that retention rules don't apply to encrypted events. Try to turn federation off, and you're in a no-man's land of untested and unpredictable behaviors. Having attempted to do exactly this recently, let me assure you that while it may be technically possible, it is practically infeasible.Īlmost everything in Matrix, at multiple layer of abstraction, is built on the presumption of federation: federated events, federated authn/authz, etc. If it's for something like company slack-like functionality you can choose to federate or not federate. It's totally possible to self host the official matrix 'synapse' daemon for self hosted slack-like functionality within an organization, and use the official 'element' client or any other compliant matrix protocol client.
0 kommentar(er)
