When I tested it, it worked without any changes to Adium. Only worked from GMail though, not arbitrary Jabber servers.
We could extend the Address Book importer to understand that x...@aol.com on Jabber is the same as xyz on AIM (or this for XMPP transports in general), but that's only minor, I'd say. Otherwise it all works, I think. :) Thijs On 16 mei 2011, at 20:35, Colin Barrett wrote: > This is pretty sweet. Anything we need to / can do on the Adium side? > > -Colin > > Begin forwarded message: > >> From: Mark Doliner <m...@kingant.net> >> Date: May 16, 2011 12:41:06 AM PDT >> To: Pidgin Devel Mailing List <de...@pidgin.im>, ope...@imfreedom.org >> Subject: Re: AIM <--> Google Talk Federation >> >> The interoperation magically started working for me. It's so neat! >> >> AIM users can IM "whoe...@gmail.com." The first IM will fail to go >> through and the Google Talk user will get an authorization request. >> After the auth request is accepted, messages from the AIM user to the >> Google Talk user go through. And Google Talk users can IM >> "screenn...@aol.com" or "email(domain.com)@aol.com" >> >> IMs go through immediately. Even status messages and typing >> notifcation appear to get translated between the two protocols. >> >> If you've registered a gmail.com account as your AIM screen name, and >> an IM user IMs "whate...@gmail.com," messages go to both, for the most >> part. >> >> --Mark >> _______________________________________________ >> Openim mailing list >> ope...@imfreedom.org >> http://pidgin.im/cgi-bin/mailman/listinfo/openim > >
