Matrix/Element was the best fit when I looked into reasonably private messaging for a small org. - Matrix has E2EE support, the able to be self-hosted, decent

Matrix/Element was the best fit when I looked into reasonably private messaging for a small org. - Matrix has E2EE support, the able to be self-hosted, decent if not perfect clients for all platforms, and an easy to spin up hosted solution through their services company. I think who talks to who could leak, but I think the content is reasonably put into an envelope so to speak. The 2019 security issue seems to have been resolved. I just wish there was a built-in option for Matrix (Element.io) instances to enforce "only allow E2EE chats". I mean: allowing instances to disable federation prevents some outflows, and E2EE by default is sane, but I want to NOT allow users to accidentally (e.g., in ignorance) click the toggle switch that turns off E2EE for communication chats that they create. BIGGEST FEEDBACK ON MATRIX/Element: I really think this "only allow E2EE" should be part of the protocol somehow (as an option for instances), and not just a server customization/implementation detail. --> I haven't had the courage to contribute this meek suggestion to "More Instant Messaging Interoperability (MIMI)" [0, 1], but does anyone know if it's being talked about? Does this make sense? It seems sort of obvious to me. [0] https://mailarchive.ietf.org/arch/browse/mimi/ https://mailarchive.ietf.org/arch/browse/mimi/ [1] https://turt2live.github.io/ietf-mimi-matrix-message-format/draft-ralston-mimi-matrix-message-format.html https://turt2live.github.io/ietf-mimi-matrix-message-format/...