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: #email@example.com
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
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.
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 are sorry to announce that Facebook will put down their Facebook XMPP Chat API in April 30th 2015. For official Facebook information please see here. Key information quoted from there:
On April 30, 2014, we announced the deprecation of the XMPP Chat API as part of the release of Platform API v2.0. The service and API this document covers will no longer be available after April 30, 2015.
Once version 1.0 is deprecated on April 30, 2015, chat.facebook.com and the xmpp_login permission will no longer be available.
We will turn off our Facebook transport in the days after April 30th 2015. All data will be deleted. But you have to make sure that you clean up your roster and remove all @facebook.jabber.hot-chilli.net contacts.
We just changed the Prosody authentication provider module to hashed SCRAM-SHA-1 passwords.
You most probably will not notice anything. But if your client does not support SCRAM-SHA-1 the password will be sent in plain, not DIGEST-MD5 like until now. So be sure you only use a TLS/SSL connection to the server to protect the password (and also all your other XMPP data like chat messages) inside an encrypted data stream. Some clients might show a warning that DIGEST-MD5 is not longer available on the server.
The next time you log in the password will be automaticly hashed with SCRAM-SHA-1 mechanism.
We upgraded the Jabber server from Prosody 0.8 to 0.9 today! This brings a lot of new features, I just want to name IPv6 support and a Web Admin interface for our Jabber hosting customers. :-)
After migrating from ejabberd to Prosody we had to dump IPv6, which is now coming back. We are very happy about that and cannot wait how statistics will change after we support it again. ;-)
Also we installed several new modules with some new features.
A big thank you to Matt, the chief maintainer of Prosody! :-) The server upgrade only took about 20 minutes until the server was up and running again. Without him this would not have been possible. We run some special configs which had to be taken care of.
Along with other transports in the last days and weeks Twitter was migrated to Spectrum 2 today.
With Twitter you have some more features. Instead of using the personal messages from firstname.lastname@example.org you can use your personal Twitter chatroom at #email@example.com.
Sending #help to the Twitter transport gives you this:
#status ==> Update your status
#timeline [username] ==> Retrieve ‘s timeline; Default – own timeline
@ ==> Send a directed message to the user
#retweet ==> Retweet the tweet having id
#follow ==> Follow user
#unfollow ==> Stop Following user
#mode  ==> Switch mode to 0(single), 1(multiple) or 2(chatroom)
#help ==> Print this help message