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.
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.
The Spectrum transport services are down at the moment. It will take one to three days until these services are up again. Mostly because we are about to move all Jabber related services to a new machine. So please stay tuned.
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.
Because there are problems/bugs with ejabberd 13.x connecting to our transports we just replaced the certificate for our main virtual host jabber.hot-chilli.net. This host also does service our transports.
Until then we had used a certificate with the common name *.hot-chilli.net, now we have one with jabber.hot-chilli.net and *.jabber.hot-chilli.net common names which does not lead to the problem.
Some days ago we already replaced the *.hot-chilli.net due to the OpenSSL Heartbleed bug.
Some weeks ago we removed the MSN transport from our list of transport services. Microsoft stopped supporting MSN, so the transport did not make sense anymore.
We installed two new transports: Novell Groupwise and SIPE (for Microsoft OCS/LCS Messaging). We did not test these transports as we do not have access to Novell or Microsoft instant messaging chat servers. If you test these transports please give us a short feedback.
The captchas of our registration forms (account and transport pre-registration) work again.
There was a session management problem which now is solved. Sorry for the time it did not work.
The web forms for changing passwords and removing accounts are not available, yet. Also there will be forms to reset passwords by sending out a mail. Therefore there will also be a web form to bind mail addresses to Jabber accounts. Please stay tuned.
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