Offline Storage Migration did take very long

Wow, the migration of the offline storage from file to database did take very long. I thought one or two hours are enough. No, the scripts ran for 10 hours. Therefore the Jabber/XMPP services were offline for about 10 hours, from ~10:30 pm CEST yesterday to 8:50 am CEST today. We are very sorry about that. Good news: No more big downtimes are planned in the near future.

Prosody 0.10 up and running

Everything is done, the server runs on Prosody 0.10 and is up for over an hour now. Thanks to MattJ for his help solving the small issues when upgrading.

No new features like MAM and WebSocket are activated, yet. This will follow. But I had to disable mod_privacy_lists and mod_blocking and enable mod_blocklist. This means that we drop support for XEP-0016 which only older clients used nowadays as XEP-0191 is the newer standard which we still support with mod_blocklist.

We support OMEMO!

A few days ago Daniel Gultsch added the column XEP-0384: OMEMO Encryption to his compliance list. It suggested that only 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 I also reused some text of the blog post of Sebastian as it describes everything quite good. So thank you for that, Sebastian! 😉