Denis Varlakov

@tmpfs, unfortunately, `StateMachine` implementation is difficult to maintain. Any protocol implementation (e.g. gg20) requires a lot of non-trivial boilerplate, and it's simply difficult to deliver bugfixes, analyse the code, etc....

There's [`round-based2` branch in the repo], but it's poorly documented at this point, though most of api is established. You can look at [`round-based-ing`], lib that integrates `round-based` and ING's...

Hi @palladionIT, sorry for confusion, `CompletedOfflineProtocol` must not be reused. Reusing leaks the private key. We need to fix this comment. About serialization — probably it's the same reason, storing...

How can I restrict 'full write access' if I just installed the app? I don't have this option in the app settings

Actually, `/*! ... */` comments are not supported either (see `INNER_BLOCK_DOC` in [the spec](https://doc.rust-lang.org/reference/comments.html)). These regular expressions should cover them: ```kotlin blockCommentStartRegexString = "/\\*[*!]?" blockCommentEndRegexString = "\\*\\*?/" lineCommentRegexString = "//[/!]?"...

I tested regexes above locally, they did the job. Let me know if you want me to open a PR

Hi @rubdos! Actually I simply missed this amazing crate when I was googling something similar. It can significantly simplify our code! My only concern is why are you still using...

Thank you for keeping up to date! We will switch on `libsignal-client` shortly after Michael-F-Bryan/libsignal-service-rs#83 is merged

> we've moved to https://github.com/whisperfish/ I saw all this story with choosing right license (GPLv3 / AGPLv3) and signing CLA. Tricky journey!

I made [a fork of oqs-rs](https://github.com/survived/oqs-rs/tree/liboqs-upgrade) and keeping it compatible with the freshest version of liboqs. However, there're a lot of work to do: like, update documentation, remove dead code...