Slashdot Mirror
AOL Adopting Jabber (XMPP)
sander writes to tell us that AOL seems to have decided to make their AIM and ICQ services compatible with XMPP. A test server is up at xmpp.oscar.aol.com, and while it's still buggy most major Jabber clients seem to work.
Man, I have to feel sorry for bob@aol.com.
I've been using that account for various spammy registrations since 1998.
3 cheers for Bob!
If you don't know what AltaVista is (was), get off my lawn.
AIM support in GMail Chat (not the GTalk client) still uses the standard AIM protocol, not XMPP. In order to use it, you must have an AIM account. If AOL eventually fully support XMPP what that will mean is that you can use your XMPP account to chat with AIM users directly without having an AIM account yourself.
I was introduced to IM through ICQ back before AIM existed. I remember Aim being ok, but ICQ was much better...well naturally AOL bought mirabilis for 300M-odd dollars way back when and then did the "standard operating procedure" (see the story of Netscape, Nullsoft, et al) of just letting it fester without updates while they pushed their product.
AIM was pretty much the only game in town after that for me...I had my people on AIM, and didn't see any reason to move to yahoo, let alone Msn.
Then everything seemed to stay the same for liek 5 years. The only thing AOL really seemed to be working on was adding loud video ads and fighting against the people who tried to make their crap usable -- like deadaim and it's ilk, gaim, etc.
Over the past seemingly decade, there was talk of cross-network integration...a la msn meets aim, etc. As far as I got was logging into multiple networks in gaim--which is NOT what I was hoping for.
Then google finally put out google talk, a great implementation. Easy enough for my parents to use, no ads....less spyware concern because google doesn't have an evil time warner overlord. And there's a web version of gtalk which beats the PANTs off of the aol crapfest they've called aim express. That's good for those who run different OSes or who don't want to be committed to installing software locally. To their credit aol did put out some token linux release, which i appreciated.
Call me old school but I like the TSR windows client. I don't want my IMs getting lost in browser tabs...I wish they'd port it to linux.
Anyway I read todays news as AOL is losing customers, so they're finally getting their protocol straight and using a standard.
Anyway, Google. PLEASE, please please grab AOl off of time warner...they've been dying to get rid of it, although they're too proud to admit it. Take their user base and merge it with yours. Get rid of their crap....get the media company bias out of their products...I'll take google's signature embedded ads over just about anything that's ever come out of AOL
While you're at it, take nullsoft too...and release all the source code....it might be best to release the code from before the AOL merger, btw.
And as such, this is a clear admission that Google Talk was putting a serious dent in their business. They had no interest in standards until they had competition, but now that they do, they'll certainly want to make sure that their competition isn't the only one that can claim universal access (which is exactly what Google can claim now for their Web-based client).
the real question is -- are they going to support XMPP S2S (server to server federation)? Currently it looks like port xmpp.oscar.aol.com:5269 is NOT accepting connections (that's the XMPP S2S port).
Without S2S, this announcement is pretty much useless -- I mean, sure I can use my jabber client against AOL instead of the AOL-branded one, but I pretty much can do that already via the reverse-engineered joscar libraries (e.g. libgaim)
XMPP would allow you to have a jabber account on your corporate network, and talk to somebody on AIM, ICQ, or another company's japper network, without having to have accounts on those servers. Think of it like email, you have yourname@yourisp.com, and I have myname@myisp.com, but you can send me an email without signing up with myisp.com. Well now we get the same flexibility with IM. The only thing I see missing is an MX-like DNS record for IM servers.
http://www.mhall119.com
And then you still have AOL, MSN, or Google logging your chats, if you're talking to someone on one of their networks. If you're the only person using your chat server, it's really like just using a very complicated client program.
E.g., if you're "joe@homenetwork.net" and you run a XMPP server at messaging.homenetwork.net, but all the people you talk to are on Google or AOL, every message you send goes from your client, through messaging.homenetwork.net, and then over to Google's or AOL's servers (where presumably they log them), before going to the destination.
Unless you can convince your friends to use your chat server (messaging.homenetwork.net) rather than AOL's/Google's, you're not getting any additional privacy.
Frankly, I think privacy isn't really the goal we should be aiming for with this. If you want privacy, get OTR encryption (the easiest way is just to use Adium on the Mac), and then it doesn't matter quite so much whose servers the messages are passing through. The switch from OSCAR to XMPP is all about interoperability.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
http://www.mhall119.com