With Jabber transports, all your foreign accounts follow the Jabber ID. When you log into another machine, software, OS, you see all your friends: configure once, use everywhere.
With a multiprotocol IM client, you have to configure ALL your accounts EACH TIME you change machine, software, OS, etc.: configure once, configure everywhere... as many times as the number of accounts you have!
I used to do this for a while; it was nice because I could SSL to my jabber server from unencrypted wireless networks, since none of the commercial IM services care about security.
But it had two main problems: jabber.org had several hours of downtime each week, and transports can't handle anything beyond simple text messaging and presence. (It's bad enough that Pidgin doesn't support voice chat/webcams/games/IMvironments and all the other useless crap that everyone on yahoo want you to use)
Discussion (3)
With Jabber transports, all your foreign accounts follow the Jabber ID. When you log into another machine, software, OS, you see all your friends: configure once, use everywhere.
With a multiprotocol IM client, you have to configure ALL your accounts EACH TIME you change machine, software, OS, etc.: configure once, configure everywhere... as many times as the number of accounts you have!
I used to do this for a while; it was nice because I could SSL to my jabber server from unencrypted wireless networks, since none of the commercial IM services care about security.
But it had two main problems: jabber.org had several hours of downtime each week, and transports can't handle anything beyond simple text messaging and presence. (It's bad enough that Pidgin doesn't support voice chat/webcams/games/IMvironments and all the other useless crap that everyone on yahoo want you to use)
Jabber cada dia se vuelve mejor