Archive

Archive for the ‘Transports’ Category

New Transports

December 31st, 2010 No comments

Twitter and Identi.ca are now reachable via our transports.

Update: Removed Identica, they have an inbuilt xmpp service.

Categories: Features, Transports

Hello Spectrum

February 22nd, 2010 No comments

For some time now Spectrum made itself a name for being a fast and reliable transport between XMPP and “legacy networks”. After moving from ejabberd to Prosody XMPP-wise, switching away from the python based transport has been a task on our to-do list for far too long.

The most visible differences for end-users will be another domain being used and more choice in regard to supported protocols. Namely aim gg icq irc msn qq simple xmpp and yahoo. The current transports located at “im.thiessen.it” will be available under “thiessen.im” along with the new ones in the future. The necessary changes in your roster are being done automatically and should not result in more than a short disconnect.

Update: The migration has been completed successfully. In some cases users may ended up with the wrong encoding for their country. If you should experience problems please contact us in support@rooms.thiessen.im (webchat).

Update 2: We currently experience a problem where the transport suddenly stops reacting. Spectrum’s development team has been informed and we expect a fix by the end of the week. If you notice connection problems, please use the chatroom mentioned above to let us know.

Categories: Features, Transports

Restart of PyMSNt

February 16th, 2009 No comments

A few days ago we restarted the MSN transport. PyMSNt was causing a huge amount of traffic by requesting everyones avatar at login. From now on a contacts avatar will be updated only by starting a chat session.

Categories: Maintenance, Transports

PyMSNt fix & update

January 22nd, 2009 5 comments

Yesterday the PyMSNt transport stopped working. Upon a try to connect to the MSN servers, a user got to see the following:

Failed to connect to MSN servers:
[Failure instance: Traceback (failure with no frames): exceptions.Exception: Timeout]

We fixed that by editing one line in src/legacy/msn/msn.py.

Look for: MSN_PROTOCOL_VERSION = “MSNP11 CVR0″
and change it to: MSN_PROTOCOL_VERSION = “MSNP11″

Furthermore we removed the max. filesize one can transfer using the MSN transport.

Thanks to harrykar for reporting the issue!

Categories: Maintenance, Transports