To view parent comment, click here.
To read all comments associated with this story, please click here.
Currently there are some problems with IM services like AIM/ICQ & MSN blocking well-known or activily-used Jabber servers that support transports to them. I guess Google got an agreement that they will not be blocked when using the AIM/ICQ transport. I hope that also means AOL is not going to block other Jabber servers anymore (or even better: move to jabber themselves!).
The problem with that (to me anyway) is that you send your account name and password to the Jabber server that is acting as a gateway to the other network.
AOL I think it was who claimed they were blocking Trillian because of the security implications of entering your AOL password in a 3rd party app (Trillian).
The thing of it is though that Trillian doesn't send your password in to Cerulean, it is stored locally and sent to the AIM network to log you in. Assuming on trusts Cerulean to not have your password sent to them, you are good.
With Jabber it is different, your (AIM, ICQ, MSN, whatever) password actually goes to the Jabber server. I'm not sure I trust some random Jabber server with my ICQ password. If you have a server you know you trust, great, but the fact remains that a third party has access to your password. I refuse to use Jabber as a gateway to ICQ/AIM/MSN for that reason.






Member since:
2005-06-29
Most people don't know that, but you can do that now using jabber and transports. Transports run server-side and users from other networks appear to your jabber client as normal contacts do, but in reality they aren't using jabber "directly".