Categories
Features How-to's Transports

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
Features Transports

Facebook transport for Facebook only

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
Features Transports

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.

Categories
Downtimes Features Maintenance Transports

Server offline due to maintenance work this morning

The server was offline this morning because of Kernel and MySQL upgrade. It would have happened faster if the server rebooted cleanly after “shutdown -r now” which it didn’t. So we had to send someone there to reset the machine manually.

We also upgraded Spectrum to support JID escaping. If this works after our tests (there seem to be some problems with clients who don’t support the unofficial % character which is used for @) I write more about this here.

Categories
Transports

Spectrum transports “ghost” contacts issue is fixed

The thing with contacts appearing to be online after a Spectrum transport crashed (mentioned here) got fixed on May 23rd.

Categories
Problems Transports

ICQ Transport stable again

We had stability problems with ICQ Transport starting yesterday morning. This was caused by a certain version of libpurple. Issues should be fixed now.

Please note that with Spectrum transports crashes (not “normal” stops or restarts) it might happen that your client thinks it’s still online. Therefore some contacts appear online even if the client is not really logged into the transport at the moment. Spectrum developers are working on this issue. Until then I just hope that the Spectrum transports run stable. ;-)

With the new libpurple Gadu-Gadu transport should finally be stable, too. We’ll see how this works out in the near feature.

Categories
Transports

Facebook changed JIDs

It looks like Facebook changed their JIDs from u1234567890@chat.facebook.com to 1234567890@chat.facebook.com. For our Facebook Transport users this means that you might see all Facebook contacts again in your roster, maybe twice, old and new. Sorry for the trouble, but lucky for us this is a Facebook issue.

Old transport contact on facebook.jabber.hot-chilli.net:
u1234567890%chat.facebook.com@facebook.jabber.hot-chilli.net

New transport contact on facebook.jabber.hot-chilli.net:
1234567890%chat.facebook.com@facebook.jabber.hot-chilli.net

Categories
Features How-to's Transports

Group chat via XMPP Transport

You can join group chats via our XMPP (J2J) Transport now.

To enter chatroom@jabberserver.tld please with the JID you use with our XMPP Transport join the following chat room:

#chatroom%jabberserver.tld@j2j.jabber.hot-chilli.net