A few days ago Daniel Gultsch added the column XEP-0384: OMEMO Encryption to his compliance list. It suggested that only conversations.im supports OMEMO Encryption, which isn’t true. Yesterday an explanation was added to one of the source files of the ComplianceTester and also a question mark was added to the column mentioned above, which is a link to this explanation.
Daniel Gultsch strongly recommends that the servers PEP module should support publish-options. If enabled, Conversations starting with version 1.20, will be able to send OMEMO encrypted messages to clients, without the need to add them to your roster first. This is a great new feature and we like it, and would like to support it, but currently the PEP module from Prosody does not support publish-options (yet).
Long speak short: You can still use Conversations and other clients with OMEMO over our and other servers, but without the feature of writing encrypted messages to persons, who are not in your address book.
For more information please see here at 5222.de. I also reused some text of the blog post of Sebastian as it describes everything quite good. So thank you for that, Sebastian! ;-)
We upgraded the Jabber server to Prosody 0.12 (from 0.11) yesterday, see the changelog.
If anyone is looking for a Matrix server besides matrix.org or matrix.im, please visit us…
We did a lot of digging into the issues that the browser windows froze when…
We just added another public domain to our XMPP/Jabber server: hot-chilli.im For the future we…
On March 30, the EU Commission plans to introduce a package of laws against child…