> Without advocacy, conferences, documentation and tutorials, Matrix would become a niche protocol used by a few enthusiasts for side projects, whilst big proprietary and siloed networks continue to hold the world’s communications.
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.
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.