| ▲ | teekert 6 hours ago | |||||||||||||||||||||||||||||||
I recently listened to a podcast addressing this (one of the hosts works on Matrix/Element), basically, the "Unable to decrypt message" is what almost any error ends in. Also, they recently tried to remove all these issues and managed a 10x reduction, another highly focused effort may reduce it another 10x. I believe this was on the Late Night Linux podcast [0]. In any case, I use Matrix for anything FOSDEM related and I have seen 1 of these errors over the last year, said user said they replied from within an Android notification fwiw. I really enjoy Matrix/Element tbh. | ||||||||||||||||||||||||||||||||
| ▲ | seanieb 6 hours ago | parent [-] | |||||||||||||||||||||||||||||||
> 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. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||