AOL Won't Enable Instant Messaging Interoperability

chill writes "Wired is reporting 'America Online is scaling back efforts to make its popular instant messaging system work with rivals, saying the task has proven too difficult and expensive.' That's funny, they don't seem to have a problem blocking anyone who figures out how to interoperate. Legally, they are not supposed to offer "next gen" IM over Time Warner's cable lines until they can interoperate. We shall see."

Comments

Re:Why?

[eNonymous Coward]

I use AIM, Yahoo Instant Messenger, and ICQ. I have seen MSN messenger. None of the others allow interoperability. Why should AOL make theirs that way if the others aren't following suit?

Because the government ordered them to? IIRC, part of the FTC/FCC agreements which allowed the AOL Time Warner merger to go forward specified that AOL had to open up its IM protocol (and broadband network) and play nice with others. They've allowed Earthlink to operate over Time Warner's cable lines - though arguably that isn't much competition - but they have yet to open up AIM.

Re:Why not

[reaper20]

It exists - Jabber.

Also at the reg.

[explosionhead]

The story is also up at The Register

Re:Why?

[Sparks23]

Yes, Microsoft have actually been very supportive of the Trillian software effort. (Which faintly boggles the mind.) Yahoo hasn't tried any antagonizing tactics that I've heard about (though their servers/protocol are badly-behaved enough that sometimes you don't NEED to block). Even ICQ, which is also owned by AOL, hasn't blocked Trillian.

The thing is, AIM and ICQ are by far the two biggest IM networks, and AIM is larger than ICQ by a fair amount (especially since ICQ has lost users to AIM and MSN as the client becomes more and more bloated). When AOL bought ICQ and already owned AIM, there were a lot of concerns about them getting a monopoly on instant messaging. Especially as AOL has spoken about merging ICQ and AIM into one network; they already are moving closer and closer together and using the same login servers.

When AOL and Time Warner wanted to merge, they were told to make their instant messaging network open to interoperability. AOL agreed to do this, and laid down a timeline of what they planned to do with AIM/ICQ. Among those things was 'real time video chat for broadband links'. So the FCC said 'great, fine, you have to have your servers interoperable before you hit that milestone.' AOL agreed, and then cheerily decided not to aim for that milestone.

Now, they've continued to claim that projects like Trillian 'put their users at risk' because unauthorized software connecting to the AIM networks could be hacking to steal user information. (If you can get AOL user information over the AIM protocol, I'd say they have some more serious problems than Trillian and EveryBuddy.) Or to 'spam' people (which is ironic, because ICQ - which they don't care about clients connecting to - has far more spam than I've ever seen on AIM).

So, yes...it's their servers, and their protocol. But on the other hand, they've deliberately snubbed the FCC decision, and their justifications for kicking third-party software off are fairly weak. (Ironically, I actually wouldn't object if they just came out and said 'well, we want to keep a monopoly on IM, and these are our servers'. Claiming that EveryBuddy, Jabber, Fire and Trillian are written by 'hackers' who want to compromise the AOL network to gain user information -- when they say the 'user information' being gained is by having this software trick the user into entering their password -- is just unethical spin-doctoring.)

They're being singled out because

[Andy Dodd]

AOL owns one of the largest broadband and cable TV networks in the country.

They are being singled out because they signed a merger agreements saying that they CANNOT offer next-generation IM services over their cable network until they are interoperable.

This could be one of the reasons MS is playing nice, in addition to the ones pointed out earlier. MS is worried about having MORE ammo against them in their antitrust suit due to the close ties of MSN Messenger, Windows, and MSN service. So as a result, they play nice and look like the Good Guys for once.

Re:Why?

[LBU.Zorro]

Actually that's not quite right.

They were permitted to merge, and the AIM server-to-server (noting that the FCC requires it to be server-to-server) interoperability was not an issue for the merge, EXCEPT that they were NOT allowed to provide realtime video messaging over their newly aquired cable modem networks UNTIL they had enabled that interoperability with either open published standards OR connections with three other IM networks.

They have recently stated that they are pursuing other approaches to the interoperability aside from server-to-server because there are 'key issues' with that approach. This goes against the FCC decision (assuming they provide the video messaging) if they use anything other than server-to-server AND they enable video messaging, and there may well be real valid reasons for the issues with server-to-server, although I can't see them.


Z.

TAC - Linux console Instant Messaging

[GrendelT]

for what its worth:
i would like to share TAC with everyone. Its a Tcl/Tk based shell script for *nix that allows you to chat with AIM users.
(why hasn't AOL blocked this?) i love it, small useful, dont need a GUI anymore to send a quick message...

i dont care so much about interoperability as much as i do about just opening the protocol and stop blocking 3rd party IM clients (like Trillian or TAC - altho tac hasnt been blocked). As long as i have a choice of AIM clients then i'll be happy. If every messaging protocol was open, then programs such as trillian would function more perfectly. plus if the protocol was opened, other servers might popup, and that'd take some of the load off the AOL IM servers. that's my $.02...

Re:Hmmm...

[erasmus_]

As they specifically pointed out in the article, the kind of interoperability they're talking about isn't an "all in one" IM solution, which still requires you to create multiple accounts for each IM vendor. Instead, they mean allowing users from other networks to communicate directly with AIM users. So, you have a Yahoo account and I have AIM, you can add me directly as a contact, and msg me without signing up for AIM.

Although your post, and others, are pointing out that AOL has been hostile to programs like gaim, Imici, Jabber, Trillian, etc., I believe that this is different from what AOL is being mandated to do. Now, granted, AOL should be nicer to all of these programs that provide us with at least the possibility of using other clients, but unfortunately it doesn't sound like that's something that's being made required of them.

Re:As an AIM user, I like this

[eNonymous Coward]

But now, some f*tards as using the AIM system to send out spam-like messages.

Uncheck the "Allow people to find me" and "I am available for chat" boxes in the AIM profile, and you won't get any more spam.

These settings serve absolutely no purpose other than to provide spammers with names via the "Find a Buddy Wizard." (If you're hoping that some lonely hot chick will find you by searching your AIM profile, believe me, it ain't gonna happen ;) You can still maintain your AIM profile while keeping these two options unchecked, just hit "Next" a couple times until the profile editing window comes up. That way the people who know you can view your profile, but people who don't know you (99.9% of such people who'd want to IM you are spammers, the other 0.01% are fat chicks) can't figure out your screen name.

I've been using AIM since it was released. I have never, ever received an IM spam on AIM thanks to following these guidelines.

Re:The biggest problem

[benking]

Done its called Jabber

OT: Outlook replacement

[RogerWilco]

this is OT but,
Did you ever check Pegasus Mail www.pmail.com
It's not as glossy as Outlook and needs a little getting used to, but it really does everything I want.

just my 2 cents.

Re:Even Microsoft don't do that

[BagOBones]

You can remove MSN Messenger in all versions of windows with this command in the RUN window or at the command line:

RunDll32 advpack.dll,LaunchINFSection %windir%\INF\msmsgs.inf,BLC.Remove

Quick easy and its totaly removed.. Watch those windows updates in XP because some of them will reinstall it.