jabber.fsinf.at Jabber for everyone!

Due to updates to our server, the server will be down for some time on Monday, August 23, 2010 around 1 am. We will use this time to upgrade our operating system from Ubuntu 9.04 to Ubuntu 10.04.1) and ejabberd from 2.1.4 to 2.1.5.

Update: Ubuntu 10.04.1 apparently has again been delayed until Tue, Aug 17th. Lets see if their promise holds this time.
Update 2: Please see the most recent article for up to date information.

Update: It seems that both the problems with gmail and jabber.org (which both were totally unrelated) are now resolved. If you have any more problems, please contact us.
Update 2: Since the problems with connecting to gmail.com seem to be somehow DNS related, we tried naming the gmail.com XMPP servers explicitly in our hosts file and at least I haven't seen any problems in the last few days. Please contact us if you still have problems.

We are currently experiencing some server-to-server connection problems:

We had some downtime during the night and in the morning. During the night, our DNS provider was at fault, this morning some broken firewall rules made the server unreachable from the outside. We apologize for the inconvenience.

We are currently experiencing some network-related maintenance by our "provider", the Vienna University of Technology. It seems our service was unreachable for many users for at least two hours or so. For now, the network seems to work fine, but you may or may not experience some further downtime. We apologize for the problems.

We will update ejabberd to version 2.1.4 at the June 6th, 2010, at 0:00 CET. There will be a short downtime, sorry for the inconvenience.

Update: Because of the massive abuse we are forced to implement this for the XMPP-transport right away. If you really want to use our XMPP transport, you have to create a local account.

These past few weeks our Apt repositories have seen a few updates, read on for a complete list:

Update: Because of ever growing memory usage, we are forced to temporarily deactivate the Twitter transport. We will reactivate it as soon as the problems seem fixed.

Again thanks to Spectrum, we now offer a Twitter transport. The developer of Spectrum tells me this is still rather untested, so if you find any problems, please submit them to the issue tracker.

I've just took the time to reactivate our MSN transport. The Transport is no longer provided by the somewhat unmaintained PyMSNt but Spectrum. It seems the conversion went through smoothly, if you have any problems, please report them.