3 ms·

We have done a huge amount of work on fixing E2EE issues - when running latest matrix-rust-sdk clients (e.g. Element X) and matrix-js-sdk using matrix-rust-sdk-

We have done a huge amount of work on fixing E2EE issues - when running latest matrix-rust-sdk clients (e.g. Element X) and matrix-js-sdk using matrix-rust-sdk-crypto (e.g. Element Web/Desktop), "unable to decrypt" bugs should be unheard of. So, the point of this blog post is to try to spell out that we've fixed this. Meanwhile if you see ANY unable to decrypt errors, PLEASE submit debug logs on both the sender & receiver, and we will jump on it aggressively. In terms of threads: yes, the stuck unread notification bug(s) were a disaster, but also fixed last year. Behind the scenes, 2023 was an absolutely awful year for Matrix & Element along many axes, c.f: https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/#in-other-news https://matrix.org/blog/2023/12/25/the-matrix-holiday-update.... Sorry that you got caught in the disruption.

ailurooo 2y ago
The UX for E2EE is full of trip mines that will easily lose your encryption key. You need to be designing a product around people who don't read and just want a slack/discord like format. The amount of times i've lost my decryption keys or my friends have lost my decryption keys because they don't religiously backup their keys is such a dramatic time sync..
Arathorn 2y ago
btw, there should be a great talk The Matrix Conference tomorrow about this: https://cfp.matrix.org/matrixconf2024/talk/8BVVT3/ https://cfp.matrix.org/matrixconf2024/talk/8BVVT3/ See also https://cfp.matrix.org/matrixconf2024/schedule/ https://cfp.matrix.org/matrixconf2024/schedule/ for all the other Matrix stuff happening over the next 2 days :)