Slashdot Mirror


AOL and .mac IM Not Entirely Integrated

gsfprez writes "While chatting with some Apple employee friends (with .mac accounts and iChat), we were stumped why we couldn't see each other on AIM. It seems that AOL has decided to take the opportunity -- while integrating the .mac users 'into the fold' -- to modify their AIM protocols so that Open Source clients (like Fire and Trillian) can't see those with '@mac.com' IM accounts, and vise versa. Bottom line: you can't be seen by .mac IM users, and they can't see you, unless you get the crufty, single service AOL IM client. The only positive affirmation of this is from the Fire mailing list. 'Into the fold ... sorta' is more like it." Well, it's still early, this may merely be about bugs that need fixing, rather than intent to block .mac users. We'll see.

3 of 61 comments (clear)

  1. Fire v. iChat by cappadocius · · Score: 2, Interesting
    This would seem to create a rather strange schism between OS X'x current reigning IM client, Fire.app, and Apple's new iChat offering.

    Undoubtedly, anyone who depends on running on two or more messenger systems will stick with Fire. Those who use only AIM will probably switch to Apple's offering. But if this is true, then within any circle of friends it has to be one or the other -- Fire (or your fave) or iChat.

    It would be a shame to see Fire die, but with the trend for Macheads to adopt Apple programs, that might very well be what happens.

    [Sigh] Back to running two messenging apps again. :(

    --

    omnia tua castra sunt nobis

  2. Proteus by bootc · · Score: 2, Interesting

    The other day I signed on to my AIM account using Proteus and a new contact was magically added to my buddies list: "PleaseUpgrade000". That sort of told me that I had to give up on Proteus.

    Just to add more to the discussion, I remember that even AIM had to be upgraded to work with or see Mac.com buddies, so it's just that the others haven't caught up yet.

  3. Re:Why don't you just get a REAL instant messager. by DeanT · · Score: 2, Interesting
    It has never crashed.
    Not strictly true. AT&T had a failure in 1990 due to a C programming bug.

    DeanT