I know we already talked about this on the public matrix room, but I just wanted there to be an issue about this:
When I send a message in a chat that the bot picks up on, I get the error 26 Mar 22:35:23 - [info] [matrix-server-config:Node-RED_matrix-bot] Received encrypted timeline event [m.bad.encrypted]: (Commands) @XXXXXXXXXX:matrix.org :: ** Unable to decrypt: The sender has disabled encrypting to unverified devices. **.
Disabling the "never send to unverified sessions" setting, causes the following different error message 27 Mar 13:30:50 - [info] [matrix-server-config:Node-RED_matrix-bot] Received encrypted timeline event [m.bad.encrypted]: (Test) @XXXXXXXXXX:matrix.org :: ** Unable to decrypt: The secure channel with the sender was corrupted. Trying to create a new secure channel and re-requesting the keys. **
Does the bot have an option to auto-react to a verify request? Something similar to the join on invite?
answer from skylord123: Verification is still a work in progress, I have a branch that I am working on it (help is greatly appreciated if someone wants to step in).
I know we already talked about this on the public matrix room, but I just wanted there to be an issue about this:
When I send a message in a chat that the bot picks up on, I get the error
26 Mar 22:35:23 - [info] [matrix-server-config:Node-RED_matrix-bot] Received encrypted timeline event [m.bad.encrypted]: (Commands) @XXXXXXXXXX:matrix.org :: ** Unable to decrypt: The sender has disabled encrypting to unverified devices. **.Disabling the "never send to unverified sessions" setting, causes the following different error message
27 Mar 13:30:50 - [info] [matrix-server-config:Node-RED_matrix-bot] Received encrypted timeline event [m.bad.encrypted]: (Test) @XXXXXXXXXX:matrix.org :: ** Unable to decrypt: The secure channel with the sender was corrupted. Trying to create a new secure channel and re-requesting the keys. **Does the bot have an option to auto-react to a verify request? Something similar to the join on invite?
answer from skylord123: Verification is still a work in progress, I have a branch that I am working on it (help is greatly appreciated if someone wants to step in).