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

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “Twitter Transport upgraded”

  1. Sometimes I need to disable messages from twitter.com@twitter.jabber.hot-chilli.net, and I am able to do so using “Log Off” function for the Twitter transport.

    The problem is that the transport becomes active again after the client restores from afk or n/a status. Please let me know if that’s transport or client-related problem? I’m using Psi.

    Another question: is it possible to implement “/on” and “/off” commands for controlling the incoming messages stream?