Open AIM 2.0

Over two years ago we launched Open AIM by releasing the Windows Software Development Kit that allowed developers to write custom clients, bots and plugins for the Windows AIM client. Since March 2006, we have released SDKs for the Mac, Linux and PocketPC platforms, as well as AIM Web APIs that allowed developers to build AIM onto websites via embeddable widgets, javascript, or XML.

Today we are adding more exciting ways of integrating and leveraging the AIM network. First, we are documenting the AIM protocol, known as OSCAR. Doing this will allow clients built using libraries such as libPurple, and other open source solutions to be enhanced to take advantage of all our protocol. Second, we are simplifying our license agreement, and removing restrictions to allow you to create the applications you and your users want. For example, we will now allow developers to build clients that incorporate other Instant Messaging services, using our SDKs, protocols and libraries. Third, we will allow developers to build compelling mobile applications for all different mobile devices. Fourth, we are removing limitations on developers from building business and enterprise applications. Fifth, AIM Web APIs now support php and AMF3 return formats for easier server and flash integration. Lastly, we are giving our developer website a huge face lift. On the new site, you will find better message boards, easier to navigate documentation and samples, and additional APIs that AOL has to offer. For developers the new website also will include some basic statistics of your application, plugin or bot.

After listening to you, the Open AIM Developer Community, we have also streamlined the process of building applications, plugins and bots. In the past we required developers of custom client applications, plugins and bots to provide a key and fingerprint to get their application authenticated on to the AIM network. We have simplified this by making the fingerprint check optional. In addition, all keys have unlimited usage. For the AIM Web APIs we are removing the requirement for URL referrer checks, which also means fewer hurdles to develop applications and makes for a better user experience.

By further opening up the AIM developer program, we are providing a better experience for all our users whether they are using the flagship Windows AIM client or Meebo in a Firefox browser. At the same time, we are giving developers the opportunity to build applications using best in breed tools and protocol. In order to best support these efforts and ensure that our users receive a high-quality AIM experience, we do require that developers include some specific elements in their applications. However, we have done our best to keep these requirements to a minimum, resulting in greater flexibility for developers and an enhanced AIM experience for their users. We have created a list, from which developers can pick a minimum of 2 items to integrate into their Web AIM or Custom Client application. The list includes:
– displaying advertising
– providing a link to installing the AIM Toolbar
– displaying a users expression/buddy icon as well as providing a link to letting the user set their expression
– displaying a user’s buddy info
– displaying the AIM Startpage

Developers can change out these items as they determine what best suits the needs of their users and their application. We will be adding new options to the list to further increase the flexibility available to the developer, and in the near-term will be adding other beneficial enhancements such as a revenue-share program for displayed advertising.

In conclusion, over the past two years we have seen tremendous growth and excitement over the Open AIM program, and today is just another step in giving developers the best messaging and synchronous communication platform in the world to build on. We know that for our users this change will continue to give them the choice in deciding what is the best AIM experience for them.

17 thoughts on “Open AIM 2.0

  1. Wow…great news..for once it seems like AOL is really behind the “Open” bandwagon. It will be interesting to see how this plays out with the partners you have announced. Good luck

  2. NEW FROM AOL the same company that now has to give away everything for people to use it. Oh wait… HEY wasn’t this totally reverse engineered about 10 years ago? Just like AOL about 10yrs late yet again. Wow this release is just so open…. NOT… You only have to choose 2 of 5 evils to use it. I can see a lot of 0x0 pixel ads integrated into clients. Oh wait that would mean we would actually have to USE the SDK. Why would you want to make your users suffer through something like this when there are better REALLY OPEN solutions. I can’t see why AOL cannot just wake up. (AOL is currently sinking like a lead balloon YAY) Open should mean “OPEN” and by open I mean no list of evils to pick from.

    Whenever someone asks me for my instant messenger name I NEVER give out my AOL one and will only give it out if there is absolutely no way I cannot talk them into installing ANY other form of instant messaging. I currently have 2 people on my AOL buddy list. I currently have 139 buddies on every other messenger service out there.

    Avoid AOL it is the DEVIL.

    Yet again thanks for this awesome 10 yr late release of some worthless obsolete code. How about next you release that treasured code to AOL 1.0????? I’m sure the open source community will be excited about that… NOT

  3. Pingback: Greg’s Mind » Blog Archive » Stats for Your Open AIM Apps

  4. Travis thanks for the feedback. Yes the protocol was reversed engineered about 10 years ago, but in those 10 years we have moved the protocol faster than these guys can reverse engineer it. We want to help libPurple, jOscar, and others implement the protocol properly as well as keep them as up to date as possible. More important is if your application is not open source you can always use the Open AIM SDK, since that will be the most up to date implementation of our protocol.

    The 2 of 5 evils as you call them are already supported by the most popular non-AOL built messenger clients. Buddy icons/avatars and buddy info are already implemented by these applications.

    In terms of the advertisement, that is an option for every company and developer to make for themselves if under 100K peak simultaneous usage. We will be launching AIM Money in April that allows application developers to share in the revenue with AOL. If over 100K peak simultaneous then an ad is required through AIM Money, however that usage limit would only be expected to be reached by a community in the 8-figure range.

  5. Pingback: Greg’s Mind » Blog Archive » AIM on the iPhone

  6. Pingback: Greg’s Mind » Blog Archive » A Twitter Plugin for SXSW

  7. Pingback: Greg’s Mind » Blog Archive » Bebo and ILoveIM

  8. Pingback: Greg’s Mind » Blog Archive » Blogging from Banaglore

  9. Pingback: Greg’s Mind » Blog Archive » AIM Express 7.0 Beta

  10. Pingback: Greg’s Mind » Blog Archive » Open AIM Developer Contest Results

  11. Pingback: Greg’s Mind » Blog Archive » Making some AIM Money

  12. Pingback: Open AIM gets recognition for being industry leaders | Greg's Mind

Leave a Reply

Your email address will not be published. Required fields are marked *