Yep, I've stopped recommending Matrix because 1. There is virtually zero user-facing documentation. Need to know how to backup keys, verify another user, or wh

Yep, I've stopped recommending Matrix because 1. There is virtually zero user-facing documentation. Need to know how to backup keys, verify another user, or what E2EE means? Ask your server operator. Basically the onus is on operators to document this stuff for their users. Except the stuff we're documenting is hard even for server operators, and especially challenging to document in a way that both nontechnical and technical users can understand. 2. Because this stuff is challenging even for more technically minded users to understand, it leads to a kind of burnout for interested non-technical users where they learn all they can about some feature and how it works at a high level from out of date random blogs, try to use the (complex, multi-step) feature, but then something won't work, and it isn't be clear whether it was because the user did something wrong or because the clients or server implementations are broken 3. Issues where core functionality is broken (e.g. two mutually verified users on my homeserver haven't been able to talk to each other in months -- see [1], [2], [3]) languish for months with zero response from maintainers. 4. While core functionality is both broken and undocumented, the maintainers announce rabbit hole features that no one asked for and seem very much like distractions, like their recently-announced microblogging view/client[4] In short the Element maintainers have shown little interest in making the platform accessible to the people who need its differentiating features the most, and have prioritized the "mad science"/technical aspect of their platform at the expense of the human element (end-users and operators). It'd be cool if Element used their resources to hire some UX folks and community advocates whose sole focus is addressing the horrid accessibility of their platform. I think most users would rather see that than further "mad science". [1] https://github.com/vector-im/element-ios/issues/3762 https://github.com/vector-im/element-ios/issues/3762 [2] https://github.com/vector-im/element-ios/issues/3572 https://github.com/vector-im/element-ios/issues/3572 [3] https://github.com/vector-im/element-ios/issues/3393 https://github.com/vector-im/element-ios/issues/3393 [4] https://matrix.org/blog/2020/12/18/introducing-cerulean https://matrix.org/blog/2020/12/18/introducing-cerulean