> basically, the "Unable to decrypt message" is what almost any error ends in
That's not the issue(s) I'm referring to. And typical of Matrix's lack of engagement with weaknesses and issues that have been raised several times. They continue to neglect the issues their protocol has.
This podcast goes into some of the details: https://securitycryptographywhatever.com/2022/11/02/Matrix-w...
However, I would be prepared for a "we fixed those issues" claim which really amounts to shallow fixes that move the issue elsewhere.
The proposal to move to MLS was accepted for a lot of reasons, reasons that have not, or cannot be addressed with their current protocol.
loading story #50559857
loading story #50560459