Recently we changed our IRC transport from Spectrum 2 to biboumi. If you are using the IRC transport you might have noticed it already. ;-) If not and you will use it in the future we hope you like it.
Author: Roi
Storage limits
We changed some storage limits in the last days:
- HTTP Upload: 50MB per file, 100MB overall quota
- Automatic deletion of offline messages: 93 days
- Automatic deletion of MAM archive messages: 31 days (if MAM was enabled by the user, otherwise no storage)
- Automatic deletion of chatroom messages: 31 days (if MUC_Log was enabled by the user, otherwise no storage)
- Automatic deletion of unused accounts: not yet
Updated web forms
We have updated our web forms and restored accessibility for users who are blind or visually impaired. You can again pass the captcha by listening to it if you cannot see the captcha image.
Also we would like to remind our Jabber hosting customers that you and your users also can use the public web forms (Change password, Reset password, Add/change email, remove account) on this website. You cannot use the Create account form as you can create new JIDs through the Web Admin and we won’t expose our Jabber hosting customers to the public.
We changed the configuration from “One transport per one IRC network” (we used irc.freenode.org) to “One transport for more IRC networks”. This affects how you must connect to a room. The format is: #room%irc.freenode.org@irc.domain.tld
For more information please see the transport description.
Connections to our Tor .onion address work again since today. So if you like to connect directly through Tor you can use the following address as Jabber server address for all Jabber domains running on our server: c2aaokzwkwkct543.onion
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.
We need to convert the Prosody offline storage to the new database format. Therefore we need to take the server down. This will happen at between 10 and 11 pm CEST today.
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.