8go

You compile it and create an executable and the executable produced is called `matrix-commander-rs.armv7-linux-androideabi` ? The permissions of `matrix-commander-rs.armv7-linux-androideabi` are correct? You start it wit `./some-path/matrix-commander-rs.armv7-linux-androideabi` ?

Yes, there is a verification issue. Matrix has modified the verification specification. And then thereafter modified the implementation of the Element clients. Hence verification is no longer working. Sadly, `matrix-nio`...

See other comments in closed issue #171 I am trying to concentrate all verify-related issue here, in Issue #182.

Added new release v7.7.0 with commit 1470570846f66b6c590b22d56ce9e8dda379fe30 added 2 new verification features: --verify manual, --verify emojireq - `--verify manual` does a one-way setting of trust - `--verify emojireq` initiates an...

Anyone else is using `matrix-nio` and is doing verification? Please raise your hand. :pray:

@kilavila > would be nice if we could use keys tho: --verify 'secret key' There is no such functionality in `matrix-nio`. Submit an issue with `matrix-nio` to request this feature...

Yes, @jknedlik , this is my understanding as well.

I might add that those who truly wish to verify, could do it by using `matrix-commander-rs` to verify and to swap the credentials back and forth between `matrix-commander` and `matrix-commander-rs`...

@hax0rbana-adam : While I have no immediate solution for you, I appreciate you sharing your experience. It will help others, and thanks for drawing attention to the Debian 11 situation.

Thanks @asano6xA0 for sharing !