@vanitasvitae Thanks for the blog post, very interesting stuff! Happy to see omemo evolving + SCE.
@vanitasvitae Thank you very much for this interesting thread! Very much appreciated :)
Dino 0.1 is released! 🎉
Dino is a secure and open-source application for decentralized messaging. It uses the XMPP (“Jabber”) protocol and is interoperable with other XMPP clients and servers. We aim to provide an intuitive, clean and modern user interface.
Release blog post: https://dino.im/blog/2020/01/dino-0.1-release/
> Mein innerer 10jähriger
Disagree. This is objectively hilarious. :)
@ij Have you tried mod_http_altconnect (https://modules.prosody.im/mod_http_altconnect.html)? The test for XEP-1056 has been updated a couple of weeks ago (https://github.com/iNPUTmice/caas/commit/74928079352f94f536595f7eade9c7236cbd9194), so people using prosody's internal web server were failing the new test because of missing CORS headers. The community module from above should be taking care of that.
I agree about ChatSecure. But you should definitely lower your friend's expectations and tell them to keep an eye on the OMEMO fingerprints. ChatSecure tends to untrust them randomly. Also, IIRC, OMEMO for groupchats has to be enabled globally once, and then for each room individually a second time.
@mike @stevenroose I just stumbled upon your threat and thought I'd chime in: profanity has native OMEMO support since v0.7, no plugins needed anymore. You need to have libsignal-protocol-c installed, though. See https://profanity-im.github.io/guide/latest/omemo.html#installing-omemo for further info.