Due to massive hardware problems we will move the Jabber service to a new machine. This will happen soon, maybe already this evening/night. You won’t be able to reach the services for about an hour. The new IP address will be 220.127.116.11 – if your DNS does not update in time. We apologize for the trouble caused.
In the meantime Facebook Transport works. So have fun with it. See here how to configure the transport service.
Spectrum Gadu-Gadu Transport seems to be very unstable. If this stays that way, we will revert back to the traditional transport service. Will see the next days…
GG Transport has also been migrated to Spectrum. Only the registered users were imported into the new database. I was not able to import other settings and the buddylists to the new transport. Hopefully this won’t make any problems for the users.
The migration to Spectrum also brought up some new transports:
To use the Facebook Transport just register by entering email@example.com as your user name and your Facebook password as the password. That’s it. The Facebook contacts get loaded into your Jabber client automaticly. Well, at least this should happen – the transport service does not work yet. So please be patient.
ICQ, MSN, AIM, Yahoo! and J2J (XMPP) transports were migrated to Spectrum transports yesterday evening and night.
After accidentally stumbled upon Spectrum (thanks to Flo!) I started the migration right away. The old PyXXXt transports were a huge pain long enough (PyMSNt for example created 800GB of traffic each month, alltogether the PyXXXt transports used 90% CPU when running a certain amount of time – which is the reason why we restart the Jabber related services every night) so I was very happy to see a young and well looked after project which really works a lot better. I’m quite enthusiastic at the moment. ;-)
All users and settings were migrated without problems, so maybe you haven’t even noticed that something has changed on the server.
The Gadu-Gadu (GG) Transport will also migrated to Spectrum, but I haven’t managed the migration of the user data yet.
ICQ Transport users please note, that charset was set to ISO-8859-15 – which should be a good choice for European users (German umlauts, other special characters etc). If you experience problems, please change the charset (to utf8 for example) of your ICQ Transport account by clicking on “Register” in the context menu of icq.jabber.hot-chilli.net. You can find this in the Jabber service discovery.
AIM Transport users please note, that the new AIM transport service seems to be a little unstable right now and has to be restarted from time to time. I will take a closer look in the next days.
J2J (XMPP) Transport users please note, that it was not possible to migrate the remote roster data to the new transport service. But as I noticed the remote roster is downloaded during the first connect.
Until now I cannot say if the nightly restart of the Jabber services at 3am CET/CEST is still necessary. The next days or weeks will tell. Stay tuned.
If you should experience problems with the new transport services please contact us in firstname.lastname@example.org.
The switch to MySQL was used to test virtual hosts on the Jabber server which works really great.
Next to the primary domain jabber.hot-chilli.net this domain was added for public use:
Some time later two extra domains for public use were added:
We also offer Jabber hosting for private domains.
On December 22nd, 2008, we switched the ejabberd daemon from Mnesia storage to MySQL storage.
Migration from jabberd 1.x to ejabberd on August 29th, 2006. The transports were also migrated (to PyXXXt).