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.
Prosody 0.10 was finally released yesterday. So today at 8:30 pm CEST (~3 hours from now) we plan to upgrade our Prosody server from 0.9 to 0.10. The XMPP/Jabber services will be offline for about 1 to 2 hours. At least this is our plan. ;-) Please stay tuned!
Very good article about WhatsApp and related topics. Really worth reading it – if you understand German a bit or use Google Translate or something like this. Thank you Thomas Leister!
Nice tutorial about XMPP over TLS (XEP-0368) from Nico of Magical Broccoli, if you are running your own XMPP/Jabber server you might be interested – if you understand German a bit or use Google Translate or something like this.
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! ;-)
The problem with “Encryption is required” when registering an account is solved for two days now. Sorry for any inconvenience this might have caused.
There was a change in Prosody with the latest update which made it necessary to identify the problem and modify our scripts on the website.
We just moved from StartSSL to Let’s Encrypt certificates for all public Jabber domains including the certificate for this website. You can find the new certificate fingerprints on the Server Specifications page.
This will affect Jabber itself and all transport services, and also this website. And it will take place during the next 24 to 48 hours. Please be patient and expect some service outages. We changed the TTL of our DNS zones to 1 minute but nevertheless it could be that your client still looks for the old server. You might need to relogin to the Internet and/or restart your client.
We will be back here when everything is moved. Until then you also can reach us on Twitter, where a link to this post will also be posted.