Nice tutorial about XMPP over TLS (XEP-0368) from Nico of Magical Broccoli, if you are running your own XMPP/Jabber server you might be interested – if you understand German a bit or use Google Translate or something like this.
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.
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 email@example.com.
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 firstname.lastname@example.org. Please don’t use more than 140 characters. For more information type:
You can join group chats via our XMPP (J2J) Transport now.
To enter email@example.com please with the JID you use with our XMPP Transport join the following chat room:
The Twitter Transport was activated some days ago and since yesterday it is working as it should.
If you like to use it, just register with your Twitter username and password. Your Twitter contacts will appear in your roster. Authorize them.
To write a direct message (DM, the tweets with @username:), open the chat window of the Twitter contact and write the message (without @username:).
To write a normal message and to see what your Twitter contacts are writing, join your Twitter group chat at #firstname.lastname@example.org.
You cannot add new contacts to Twitter via the transport service. Please use Twitter instead.
Messages with more than 140 characters (the Twitter limit) will be split and sent in several pieces.
The migration to Spectrum also brought up some new transports:
To use the Facebook Transport just register by entering email@example.com as your user name and your Facebook password as the password. That’s it. The Facebook contacts get loaded into your Jabber client automaticly. Well, at least this should happen – the transport service does not work yet. So please be patient.
ICQ, MSN, AIM, Yahoo! and J2J (XMPP) transports were migrated to Spectrum transports yesterday evening and night.
After accidentally stumbled upon Spectrum (thanks to Flo!) I started the migration right away. The old PyXXXt transports were a huge pain long enough (PyMSNt for example created 800GB of traffic each month, alltogether the PyXXXt transports used 90% CPU when running a certain amount of time – which is the reason why we restart the Jabber related services every night) so I was very happy to see a young and well looked after project which really works a lot better. I’m quite enthusiastic at the moment. 😉
All users and settings were migrated without problems, so maybe you haven’t even noticed that something has changed on the server.
The Gadu-Gadu (GG) Transport will also migrated to Spectrum, but I haven’t managed the migration of the user data yet.
ICQ Transport users please note, that charset was set to ISO-8859-15 – which should be a good choice for European users (German umlauts, other special characters etc). If you experience problems, please change the charset (to utf8 for example) of your ICQ Transport account by clicking on “Register” in the context menu of icq.jabber.hot-chilli.net. You can find this in the Jabber service discovery.
AIM Transport users please note, that the new AIM transport service seems to be a little unstable right now and has to be restarted from time to time. I will take a closer look in the next days.
J2J (XMPP) Transport users please note, that it was not possible to migrate the remote roster data to the new transport service. But as I noticed the remote roster is downloaded during the first connect.
Until now I cannot say if the nightly restart of the Jabber services at 3am CET/CEST is still necessary. The next days or weeks will tell. Stay tuned.
If you should experience problems with the new transport services please contact us in firstname.lastname@example.org.