Damir Jelić
Damir Jelić
Sure, but I think that will have to wait for #868 to be finished.
This has been closed by https://github.com/matrix-org/matrix-rust-sdk/pull/1015.
I think that's a bug in the rust-weechat crate, something to do with the FdHook constructor.
The build will by default use the systemwide `weechat-plugin.h` file, otherwise a bundled one will be used. The bundled one is as you can see very outdated. You can also...
Yeah, that might be a good idea at this point. The initial idea was to keep it up-to date with the latest Weechat release.
Encryption will work transparently as long as the `encryption` feature is enabled, if the room the message is being sent to is encrypted the message will be encrypted. Decryption works...
Well it seems like it did encrypt stuff transparently, though Element didn't receive the key to decrypt the message. Could you take a look at the logs in Element in...
No errors before that? The ids there are just hashes and don't leak any info, but they are not important anyways. Any info how you set up the sync loop?
Ah OK, we should indeed document that you need to continuously sync for E2EE to work. So `sync_once()` won't cut it, you'll need to put `sync()` into a background task...
All of the examples keep a sync running, they either react to events using the [event emitter](https://github.com/matrix-org/matrix-rust-sdk/blob/master/matrix_sdk/examples/login.rs#L52) or [pass a callback that will be run after every sync successful sync](https://github.com/matrix-org/matrix-rust-sdk/blob/master/matrix_sdk/examples/emoji_verification.rs#L82).