Though in short, as a large public institution, being able to self-host a secure and decentralised communications network is highly preferable to needing to rely on a centralised service administered by a company in a foreign jurisdiction.
https://www.youtube.com/playlist?list=PLl5dnxRMP1hX5u7TZ1FNa...
Advocacy and conferences aren't going to move the needle on mainstream adoption; those methods almost by definition are targeting the enthusiast crowd. In my view, the only factor that matters to attracting users is UI/UX. Streamlining the user's experience will do more for user adoption than any number of bridges.
It's possible that growing the community is the primary goal of Element.io rather than the Matrix Foundation, but in that case, it seems that there is a tension between the goals of the foundation vs Element. I'd like to understand the breakdown between the responsibilities of the foundation vs Element more clearly.
Element is a for-profit company, originally set up to hire the Matrix Core team and is the primary driver for many projects in the Matrix eco-system. Element cannot be successful without a thriving Matrix eco-system.
In the early days the line between Element and Matrix was rather blurred, which is why we set up the Foundation as a separate entity in 2018 to ensure that whatever happened to Element, Matrix could continue as an independent entity.
Maybe if they were more open and transparent, folks could help get them on the right track, either by making recomendations to improve, volunteering to help with things, or contributeing financially.
I really want them to succeed, but this has been going on for years now.
The Matrix Foundation Governing Board now has a dedicated finance committee, I don't have concrete timelines for publishing, though I would expect this to happen within a small number of months.
https://matrix.org/blog/2024/12/governing-board-first-report...
https://matrix.org/blog/2024/12/unrelated-cybercriminal-netw...
More to the point, even with e2ee, there is still communication metadata that is leaving your network for a third-party service. In a defense context, you would almost certainly prefer that the data does not leave your network unnecessarily.
In terms of Matrix usability and performance, Matrix 2.0 (https://matrix.org/blog/2024/10/29/matrix-2.0-is-here/) represents a huge step forward and can be used today with compatible clients such as Element X (https://element.io/blog/deep-dive-into-element-x/)