Category Archives: Transports

Remote roster feature renames buddies in Jabber roster

We noticed that buddies in Jabber roster are now renamed into the original names from the legacy networks, e.g. ICQ or Facebook.

This affects just local transport users as remote roster only works on the same server.

Sorry about that… But now the rosters are synced and renaming the contacts will also rename the contacts in the legacy network roster. If renaming in the legacy network is not supported the databases of Jabber and the transport service are synced anyway.

ICQ transport problems

We experienced problems with ICQ transport the last days. According to the developers of Spectrum this is a “glib poll” issue. epoll unfortunally does not work with glib (yet).

Therefore Spectrum ICQ transport now uses libev3 and epoll.

It looks good at the moment, I hope it stays that way. We will see what happens during the next days as our server is the only server which runs this configuration. Not even the Spectrum developers were able to test it, yet. ;-)

Remote roster

We just restarted the server to activate Remote roster. What is that?

What’s Remote roster?

Remote roster is protoXEP which allows your server to synchronize legacy network contact list with your users’ rosters. Currently it works only for local users (users registered on the same server which supports this protoXEP). It’s available for Ejabberd 2.1.x and Prosody.

Why should I use it?

It allows to your users following features:

  • When they register their account and login for first time, they won’t receive lots of subscribe presences or Roster Item Exchanged stanza. All their legacy network buddies just appear in their roster with proper groups and nicknames.
  • When they will unregistering their account, buddies are just removed from their rosters without need of unsubscribing them.
  • When they rename some buddy in their Jabber roster, it’s renamed also in legacy network.
  • When they move some buddy into different groups, it’s moved also in legacy network.
  • All changes made in legacy network when transport is disconnected are synchronized with Jabber account once they become online in Jabber.

Taken from Spectrum website.

Facebook & second XMPP transport

Sorry for posting just now. Facebook transport was blocked for Facebook use only on the day we posted about it, which means October 6th. We did not delete the old contacts for local users, as the user should get unsubscribe messages as all other users. If you still have old users in your roster, please delete these entries manually.

The second XMPP transport is online since since October 6th as promised.

Second XMPP transport and Facebook transport for Facebook use only

As mentioned here we finally have the feature which allows us to limit our Facebook transport for Facebook use only. We will delete all non Facebook accounts from the Facebook transport later today. You will be able to recreate these accounts on our second and new XMPP transport called xmpp.jabber.hot-chilli.net. We created this second XMPP transport because we noticed that more than one XMPP transport seems to be important for many people.

If you used Facebook transport for general XMPP usage and are a local hot-chilli Jabber user we delete all old contacts containing @facebook.jabber.hot-chilli.net in your roster for you. If you are a non-local user you might have to do this by yourself – which means that you have to delete all contacts containing @facebook.jabber.hot-chilli.net. When unregistering the accounts Spectrum sends unsubscribe notices to the Jabber servers, local and non-local. But all of you (local and non-local users) have to delete any leftover and obsolete contacts which might be left in your roster and/or the Jabber client.

We will announce when we finished the chances on the server here in the blog.

To activate the second XMPP transport the Jabber server will be restarted at 5:50 CEST today.

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

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?