-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session verification on WeeChat client side seems not working #334
Comments
Sadly the protocol has diverged from the initial implementation of the interactive verification and I was not able to keep up. There's some support in the Rust version of weechat-matrix, but it also isn't done yet: poljar/weechat-matrix-rs#56. |
Hey I wanna use it as well but for the exact same reason I cant. That's unfortunate. I belive that security keys exist though which let you verify a device. Is there a way to verify with those? Best regards :) |
I was able to do it from the other side, so basically calling |
Dear Developer and Community,
Thank you very much for the awesome project!
I am sorry, but it appears there is a little documentation available on the subject of a Matrix session verification on the WeeChat side. For example, once the "Verify" button is pressed in the browser (e.g. Element) client, nothing appears in WeeChat and such command variations like
/olm verify
or/olm verification
do result in success but errors like:The client though receives a cancelled event if, for example, the modal verification dialog (e.g. https://i.imgur.com/z47yBci.png ) in the browser client is closed and outputs:
Is that expected and what are the exact steps to complete the verification of the session initiated via the plugin?
Best and kind regards
Related: https://alangrow.com/blog/weechat-matrix (Matrix Chat in the Terminal with weechat-matrix...)
The text was updated successfully, but these errors were encountered: