[Arathorn]

your issue is complaining that matrix-bot-sdk can’t exfiltrate encryption keys which predate it joining a room? this feels like a pretty reasonable limitation. if you really need this, use matrix-rust-sdk with MSC4268 enabled.

[vitonsky]

No, as i wrote in issue title and explained twice in this thread, the problem is bot SDK does not support encryption. It must work by default, for "privacy focused" application. Chat with no encryption must be an option, not default.

Matrix protocol is over-complicated, as consequence any SDK and even clients are over-complicated too, that eventually makes any interaction with Matrix is difficult, unpleasant, and error-prone.

Matrix design is error-prone by its nature:

Keys exchange confuses many users, I had many questions of people who are not programmer.

Matrix encourage login at random sites who up their web client, that is critical security problem.

But a Matrix fans are blind to a problems. This is why I don't believe Matrix will transform from marginal chat for freaks to a mainstream chat where people talk. So eventually, Matrix is a platform where Matrix fans talks about Matrix and send porn to each other.

[Arathorn]

matrix-bot-sdk does support encryption: https://turt2live.github.io/matrix-bot-sdk/tutorial-encrypti...

[vitonsky]

Check discussion in GitHub issue https://github.com/turt2live/matrix-bot-sdk/issues/363

Quote > Decryption of messages in encrypted rooms always end with error `Error: Can't find the room key to decrypt the event`

Maintainer action is "turt2live closed this as not planned on May 10, 2024"

It's all you need to know about a goals of Matrix and its success.