blog: stop self-repeating about Matrix

[Mikaela]

I often repeat the same issues about Matrix when the discussion comes up, so I should type a blog about it finally and stop saying the exact same things. It will be a living document and need a link to changelog.

• Elements are inconsistent, they barely have anything more than name in common with each other, especially when you try to use Web, iOS and Android. E.g. iOS misses web previews and always visible timestamps Android has.
• User directory leaks latest usernames and avatars, even per-room ones.
• Uploaded media files are never removed
• There are no contacts, other than identity server and rooms you are in
• Room messages are stored forever (unless all participating servers happen to have explicitly set expiration times), no expiration time for room admins.

[Mikaela]

Bonus: https://github.com/matrix-org/synapse/labels/performance not based on personal experience.

[Mikaela]

Remember to say that no other solution is by no means perfect either, but this post isn't about them.

[Mikaela]

1. multiple issues and irrelevant annoyance
   • 
2. User Directory leaks Per-room Nicknames and Avatars matrix-org/synapse#5677
   1. https://github.com/matrix-org/matrix-doc/issues/545
   2. partially addressed by MSC3189: Per-room/per-space profiles matrix-org/matrix-spec-proposals#3189
3. When we redact events, any mxc content they refer to should be redacted too (SYN-216) matrix-org/synapse#1263
4. https://github.com/matrix-org/matrix-doc/issues/2936
5. MSC2228: Self destructing events matrix-org/matrix-spec-proposals#2228

[Mikaela]

Utopia of decentralised accounts https://github.com/matrix-org/matrix-doc/issues/915 without painful centralized migration tool.