There was an outage of our Jabber services the last hours. Unfortunally the hard disk ran completly full because of a faultly backup job.
Everything is back online. Sorry guys!
Categories
Twitter Transport upgraded
With today’s development version of Spectrum the Twitter Transport got upgraded. The package pidgin-twitter is not developed anymore and caused dozens of crashes daily. Spectrum now uses pidgin-microblog instead.
Please delete all old Twitter contacts in your roster, exept twitter.jabber.hot-chilli.net. (Maybe we will delete the old contacts in the near future for our local users.)
Then please allow Spectrum access to your Twitter account. When first connecting to the new Twitter Transport, you will receive the following message from twitter.jabber.hot-chilli.net:
Open following url and send the PIN number from the web page back to Spectrum.
https://api.twitter.com/oauth/authorize?oauth_token=tokenid
Follow these instructions and post the PIN number into the chat window which shows the above message and send it to the transport.
Then approve the authorization request for twitter.com@twitter.jabber.hot-chilli.net.
This contact will post all tweets from your twitter contacts.
If you want to post a tweet to Twitter, just post it into the the chat window of twitter.com@twitter.jabber.hot-chilli.net. Please don’t use more than 140 characters. For more information type:
/help
Categories
Upgrade to ejabberd 2.1.5
During this night (CEST) we upgraded the Jabber server to ejabberd 2.1.5 – this time the Debian package came available very soon. :-)
In the next days, weeks or months (it depends when the feature will be ready in Spectrum) we will implement white-/blacklists for our Facebook transport. After this the transport can only be used for Facebook – as it should be used. But as the Facebook transport is a “normal” XMPP transport many people use it for XMPP.
After the setup of white-/blacklists we will delete all non Facebook accounts out of the transport. Maybe we will move the non Facebook accounts to our XMPP/J2J transport, we’ll see.
So if you use our Facebook transport not for Facebook, please move to our XMPP/J2J transport.
BTW: Is there any need for a second XMPP transport as many of our users connect to more than one foreign XMPP account?
Categories
Upgrade to ejabberd 2.1.4
At about noon CEST today I just upgraded the server to ejabberd 2.1.4, which is a bugfixing release. Finally the Debian package is available. Sorry for the less than five minute short service downtime. ;-)
Categories
IRC transport migrated to Spectrum
We just migrated IRC transport to Spectrum. Before it was a core feature of ejabberd, the software we use for the Jabber server itself. Spectrum has more features, so we switched.
If you experience any problems please let us know.
Once again the server was hit. At around 8pm yesterday evening the services were unreachable for about 30 minutes, the transports for about 60 minutes.
For sure there will be another incident, but this time everything will get logged. From what we then read out of the logs we will choose how we react. If it has something to do with Nimbuzz, we will block Nimbuzz completely.
Again we suffered a DoS attack. The Jabber services and website were down from ~10:45pm to 00:30am.
For sure we have to do something about this. We are already digging into this, also recieving feedback from other Jabber server admins. Maybe abusive Nimbuzz accounts are the reason and, if this turns out to be true, we are also thinking about firewalling Nimbuzz.
What would you think about blocking Nimbuzz? Are you having friends from Nimbuzz in your roster? Tell us your opinion.