Damir Jelić
Damir Jelić
Are you sure the correct password is in the secure data field? This does work as I'm using it myself. While it's a bit hidden since we have some code...
So what does the print show?
Ah ok, so it seems that the problem lies in the fact that we don't get an update when the data inside the secure store changes like we do when...
No that's not possible, the messages usually aren't even loaded so Weechat doesn't yet know about them, I think you'll rather want to use server side search though that's not...
The main issue has always been libolm, we need libolm 3. If your distro has libolm, mostly everything goes smoothly, otherwise you'll need to install it yourself and installing C...
The buffer name is set every time an event has the chance of changing the name. We don't store any events locally so those events arrive every time you start...
The problem with this is that we don't really have a secure place where to store the access token, `/secure` isn't programmatically available to us. Users of course can store...
They are not stored in plaintext, well not quite correct, you have the choice to store them in plaintext or you can store them encrypted using `/secure`. Take a look...
Things that we should consider for the Rust rewrite, if we're using SSO: - Try to use the OS keystore and store the access token there - If there isn't...
You'll have to leave the room, `/part` works for this, or leaving it from another client works too.