iamb missing any messages that couldn't be decrypted #245

New issue

Open

opened 2025-10-14 15:43:38 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:43:38 -06:00

Owner

Originally created by @juippis on 5/27/2024

Hey,

I hope I can explain the problem even though I don't really understand the matrix protocol too well.

Sometimes some messages can't be decrypted - most likely because the sender/server lags out somehow. weechat-matrix and gomuks will indicate that someone sent a message that you couldn't receive with:

gomuks: failed to decrypt megolm event: no session with given ID found

weechat-matrix: Unable to decrypt: The sender's device has not sent us the keys for this message

gomuks allows you to /clearcache to properly retry receiving the messages, and will then show them to you.

I noticed iamb just ignores these events. So you never even know if you missed a message, unless you're running a client in parallel that shows these events.

I hope you can understand the issue here :) let me know if I can provide more information.

*Originally created by @juippis on 5/27/2024* Hey, I hope I can explain the problem even though I don't really understand the matrix protocol too well. Sometimes some messages can't be decrypted - most likely because the sender/server lags out somehow. weechat-matrix and gomuks will indicate that someone sent a message that you couldn't receive with: **gomuks**: failed to decrypt megolm event: no session with given ID found **weechat-matrix**: Unable to decrypt: The sender's device has not sent us the keys for this message gomuks allows you to `/clearcache` to properly retry receiving the messages, and will then show them to you. I noticed iamb just ignores these events. So you never even know if you missed a message, unless you're running a client in parallel that shows these events. I hope you can understand the issue here :) let me know if I can provide more information.