Slashdot Mirror
AIM Now (Mostly) Open To Developers
gregsblog writes "Today is a historic day at AOL as we announced a software development kit for AOL Instant Messenger. Open AIM will empower you, as the developer, to write custom clients and plugins.
For now, lets concentrate on the Open AIM SDK and get into what it can do for you. First, the development kit is written using COM, so plugins and custom clients can be written for Windows in languages like C++, VB, C#, and eventually J-Script. In the near future we will have solutions for LINUX, MAC and Windows Mobile devices. Why is this important? We now have a solution to provide all AIM users and consumers to build their own IM clients and to extend the features of Triton via plugins. Of course all of this is free of charge. How do I get started? Well my team has provided a quick start guide, and tutorials, in addition to numerous coding examples, from the simple to the complex. Our examples are in C++ and C#.
What are the limitations? Basically anything goes, with the exception of writing multi-headed clients."
Without advertising, how do they reach step 3?
... I mean, we've only been using Gaim for about five years now...
Real Daleks don't climb stairs - they level the building.
GAIM allows you to write plugins in a variet of languages including python and C++ (and anything else that can link to dynamic libraries). Of course, I don't really see a massive need for IM plugins. All this announcement means is that we will see a million COM host AIM clients with crappy UIs.
I can interface with it on the hardware level? Cool...
Fleur de Sel
Maybe they'll offer AIM certifications. Like you could be an CACC... Certified AIM coder and configurer. They'll offer classes for $1200 a pop and provide stats on what the average CACCs make each and every year.
In the near future we will have solutions for LINUX, MAC and Windows Mobile devices.
Wow. That is really cool that they are planning to embed AIM capabilities directly into the Media Access Control sublayer. That should make AIM even more ubiquitous. It's a shame they have no plans to get this AIM SDK up and running on Mac OS X, though.
BTW, what does "LINUX" stand for? I've never heard of it.
The overall effectiveness of this will of course be determined by the users who are writing their own clients/plugins. Your mileage may vary. However, I do see this as a positive step forward, if only in an academic sense. With a major company making such an effort to have their software available for community modification, with tutorials and examples, I'd have to say that this is a nice step away from the monoculture software development. Even if you can't get anything truly useful out of it, it is interesting to take a look at what is offered and see what you might be able to learn from it. Never hurts to experiment.
Randimal: AT-CG-CG-AT-CG-AT-AT-CG-CG-AT-AT-CG-AT-CG-CG-AT-CG-AT-AT-CG-AT-CG-CG-AT-AT-CG-CG-AT-CG-AT-AT-CG
"Developers are not permitted to build Custom Clients that are multi-headed or interoperable with any other IM network."
The definition of "almost, but not quite totally useless" seems more appropriate.
-Charles
Learning HOW to think is more important than learning WHAT to think.
I've been using Fire for years now, and from what I can recall, I can't think of a single person who actually uses AIM. We've been going over their network, yes, but I don't know of anyone actually using the software AIM to do so...
And as far as that goes, same thing for MSN.
About all this means, from my POV, is that we don't have to worry about them sporadically changing how their server works to disrupt every other client out there.
Z
until you start charging me a cent a line to text multiple people?
Everyone's saying that stuff like GAIM and whatnot is already out, that's true..
but with AOL releasing the AIM protocol specifications, the existing unofficial clients and support official features properly and will be able to interface with all other clients the way they're supposed to be.
And this'll make it easier to make AIM bots without having to pay the people who make bots like SmarterChild hundreds of dollars for their service.
I can see a lot of useful functions for this. I run an enrichment program for kids. I already collect IM data for each student. I could see using this to create a bot to make anouncements to my students. Water pipe broke, tonights class is canceled. Pop it into the bot. Wait a few hours. Check to see who did and did not get the message, then call the remaining few.
Want your grade on the last exam? IM the bot, it matches to your username in the database, perhaps gets a password and gives you the data.
I can see a lot of uses for this.
From the Gaim Wikipedia article:
Recently, the Gaim developers have started to separate the core code--which handles things such as network connections and messaging--from the GUI code, which controls how these actions are presented to the user. After the code split is complete, it will be possible to write client programs using a developer's GUI library of choice. The core library produced by the split will be called libgaim; an in-development but stable version of this library is already in use in the Adium, Fire, and Proteus clients as well as the Meebo web-based application.
So, in other words, AOL are going to have something much more limited than libgaim (AIM protocol only) available in the "near future"? Uhhh... congratulations AOL! Now bugger off, you jerk-burgers!
Mac (in the sense that it is used in this article) isn't actually an acronym, it's just short for Macintosh (a type of Apple computer). MAC (the acronym) usually refers to Media Access Control, which is a networking layer.
Linux is not an acronym, either, just a derivation of "Linus' Minix" (Linus Torvalds being the creator of the Linux kernel).
We don't need no stinkin' SDKs.. why not officially document and open up the API instead? That way we can call it and do what we want on any platform without having to worry about SDKs.
Wow...this is completely assinine. They could have spent the past year by actually making AIM open. The IETF did release XMPP/Jabber as an RFC nearly a year ago. AOL should have dropped this library and added support for server to server XMPP connections. They could also have made client to server connections use XMPP. Not only would that allow them to connect to Google and everyone else, they would have no need to release a library that only the script kiddy next door will use in his new VB botnet controller.
"I was given a bottle of wine. I could see the wine, and they said it was open. I knew better because I was never given a bottle opener to taste the oh so sweet wine."
Is this the first step to a true IM system that is complementary system to email?
;-) ) more developers will integrate IM into their applications. In a few years we should have one dominant protocol, and from then on IM will finally become as transparant as email is now.
If more IM vendors start opening up (Jabber, my personal favorite, has always been open, ofcourse
then again i'll be driving with 4 scandily clad girls in my newest lexus besides copacabana beach.
Still, it's a good fantasy
Exercise caution when modding this message up: the author acts like a jerk when his karma is excellent.
Yes, it would be just terrible if something like that were to happen...
Real Daleks don't climb stairs - they level the building.
I, for one, am very glad they're making steps to opening the API to outside developers.
But one critical question comes to mind: In the past, AOL has been very picky and fussy about "non-authorized" tools and processes accessing their "IM network infrastructure." Their TOS does not (or, at least, did not) allow anything other than genuine AOL AIM clients to access their infrastructure.
Does this new development opportunity change the TOS such that non-AOL AIM clients can now access the infrastructure (while remaining within the boundaries of acceptability)? Several companies have banned anything other than genuine AIM clients because of AOL's AIM TOS. Has this changed?
A Passionate Independent Musician
Thanks for clarifying that - this being Slashdot I had never heard of any of the terms used there...
First step: rid of that kissy face emoticon and replace it with something that's a little less... whoreish. :*
Nice job being a smartass to someone who's trying to provide accurate and useful information to a person who is curious and obvsiously doesn't know any better.
How do you find the time to make these posts between your busy schedule of kicking kittens and shoving nuns into traffic?
asswipe.
Evil Walrus >83=
Yeah, I know it's early, but AS IF AOL will just allow developers to make their own AIM clients without some kind of fine print somewhere. 5 years ago or so it was battle of the titans on Trillian vs Gaim vs AIM trying to keep open source aim clients off their network, and now they are open arms? I am wary....
From AIM's FAQ:
Q: Are there any restrictions on what I can build?
A: We tried to make the Open AIM Program as restriction-free as possible, but in order to help protect our network and users, certain rules apply. We have highlighted some below, but please refer to the Developers License Agreement for details.
* Developers are not permitted to build Custom Clients that are multi-headed or interoperable with any other IM network.
* Custom Clients developed for use on a mobile device or via a wireless telecommunications carrier's network and/or wireless services require separate licensing and business agreements with AOL. Any inquiries regarding mobile applications should be sent to AIMCommercial@aol.com.
* Custom Clients designed for sale to a corporate customer base or to serve a corporate employee base require separate licensing and business agreements with AOL. Any inquiries regarding enterprise use should be sent to AIMCommercial@aol.com.
Here come the AIM bots.
Anyone else having trouble registering for a Developer Key on their site? I keep getting the message: "Key was not added since you have reached the maximum number of keys for this type and class.", which appears to be zero, since there's no keys listed under my account...
Is J-Script and Javascript the same? Or is it Javascript with MS quirks?
I'm guessing this will be their version of what normal beings call a compromise, sure you can have your own clients, but you have to use our SDK. We'll fill your client full of bloat, and shut it down if you dare to make it useful.
Our greatest enemy is neither a single man, nor is it a nation, it is, as it has always been, our own greed.
I think the original poster knew very well what Mac and Linux are, and was making a crack about the capitalization in TFA..
WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
There's only one plugin I use regularly, and I think it's quite useful: Off-The-Record Messaging. Great when you don't want a pesky, bored sysadmin reading about your private life.
Program Intellivision!
I think that iChat is the "official" AIM client on Mac OS X. Back when it first came out, there was much hoopla about Apple having reached some sort of agreement with AOL, which I assume probably involved a gym bag stuffed with cash or a horse's head in somebody's waterbed, that allowed them to make a non-AOL but still completely interoperable client.
You'll notice that unlike Gaim, and like the official AIM client, iChat does all the file transfer and direct connect stuff without problems (almost all the time, so basically in the same situations that the AIM program would).
I think this is why AOL's Mac OS X efforts have been effectively suspended -- Apple is doing it for them.
And frankly, given what a pile of turds the AOL client always was, I'm quite happy that they leave it this way.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Try enabling uPNP on your nat device and using one of the 2.0 betas with uPNP support. It seems to have fixed a lot of issues for me.
With the limitations imposed by the license, there doesn't seem to be much value to this. Thinking out of the box though, perhaps it is a setup for new lawsuits against the other clients cracking into the network. By opening up, even to this limited extent, they may be countering some of the arguments anticipated where other clients are claiming that AOL left them no viable alternative other than reverse engineering the protocols and cracking in.
Well this would hinder Microsoft from including AIM support in its IM client, and I guess that is quite important to aim?
From my blog
"Fundamentally, the newly announced (and extended) Open AIM SDK will enable developers to enhance the AIM network's reach and functionality.
What can you do with it: - Extend AIM Triton at a low level - Embed AIM functionality in your own applications - Create your own version of the AIM client - Embed presence functionality and communications touchpoints in web applications
To be clear: there are some restrictions and limitations on the ways in which you can leverage the AIM services we've made available, as we feel our way through the operational and business implications. But this should open up a broad set of possible applications on top of the AIM network and namespace immediately.
In particular, Open AIM does NOT provide IM network interop with other Instant Messaging networks, at this time."
graphically speaking
We're pretty fucking worried about the new MSN Messenger/MS Office/MS Outlook integration that's going to be available in a few months.
Yeah. Because they wouldn't lose 100% of their non-aol users the day they started charging for aim. Plenty of instant messaging protocols out there that people can switch too. Right now, no one bothers to look for anything else, but the moment they're told to get their credit card, you can bet they're going to hit google to search for something else. And tell their friends.
They're not doing this out of the goodness of their heart. Most of us who use third party clients don't even realize this, but the official clients has ads. Annoying ads. I'd guess from my failed attempt to convince people to use gaim that most of their users don't care, and use the official client anyway, so they're getting money for it. I'm not implying this is a bad thing, mind you. Good for them. Just saying they're not doing you any favors.
And they stopped deliberately breaking other clients for the most part.
Yeah, surprisingly good business decision there. First, it was futile. They would pay their developers to keep breaking the clients, and it'd last the better part of a day before all the other clients were fixed. Big deal, a lot of money wasted. Also, before other clients worked reliably, there was a big deal about cracks to the aim client to remove all ads. Now the people who care about this things, unlike the people I mentioned above, go to the superior third-party clients. Which means they're reasonably sure that everyone using their official client is seeing the ads.
Again, they're not doing you a favor. If they could get rid of all third party clients for good, they would.
Warning: Opinions known to be heavily biased.
For the masses at large, this means you cannot use ANY GPLed code, or any code that causes you to redistribute your code freely.
This makes sense in the context of custom clients as you would be required to redistribute the client and the associated source code (which you cannot do because of closed source nature of the AOL libraries.) But as a consequence, it's worth paying attention to and will have some nasty effects on code reuse.
Ah, but will this enable programmers to implement methods that circumvent AOL (or Big Brother) from monitoring your messages (ie: encryption)?
If you read the updated TOS, they clearly state that your conversations can be monitored, etc. This, amoung other reasons, is why a company I worked for went to Jabber.
Comment removed based on user account deletion
... and millions of virus writers rejoiced.
Comment removed based on user account deletion
libgaim doesn't EXIST, you fool!
Ok so this is a wrapper for the AIM Client...
How is this 'Open' or even beneficial. You could write a wrapper around the exising AIM Client and strip or add features as you wanted, just not with AOLs blessing.
IE is more 'open' than this, as you can at least write an HTML rendering applicaiton around the system DLLs, and not have to license crap, or 'conform' to not integrating with other services.
Give me a freaking break. Everyone here that thinks AOL has done something good, needs to be slapped up side the head.
This is true, however you can get a plugin for $8 USD that does this.
It's called iChatter, and it does a nice job of translating acronyms back to phrases using a customizable dictionary, etc. (So you can program "LOL" to be spoken as "ha ha" or anything else you want.)
http://www.ecamm.com/mac/ichatter/
I can't personally vouch for it, but it's out there. I use Adium (or AdiumX, I'm not clear on what it's 'official' name is) as my day-to-day client, and iChat for file transfers and on the very few occasions I've wanted to use audio or video chat.
My killer feature is multiple-protocol support, because I always seem to have a few people who I can't talk out of using MSN Messenger or Yahoo Messenger, and I don't feel like running three clients all the time. The OTR encryption is fairly slick, too; I'd be nice if Apple took a hint and included that in the future as well, although they've seemed reticent to provide any kind of iChat encryption in the past.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Obviously, this move was motivated by the Google Talk threat of open instant messaging network(s). And also obviously, AOL think they can throw sand into the eyes of the OSS community and hide the fine print. This half-hearted "opening up" reminds me of the "open-source" move of Real with their Helix player not opening up their codec. I can only say just another short-sighted greedy company to be washed away sooner or later. And again, THANK YOU GOOGLE!
any more than "Linux" or "Mac" are, and should not be written as if it were.
See the FAQ.
Hey! This could be great news! They say they'll soon be supporting Media Access Control devices! (Or was that Message Authentication Code devices?)
I just did a reinstall of Windows XP and held off installing AIM for a few weeks. As soon as I installed AIM, I realized it was the new Triton Beta...and I couldn't log into my own SN, and it seemed to slow my system down. Way to go AOL! I got the older version and it works fine though.
I can tell you one factor in this move is that AOL is losing IM users in chunks. I do contract work for HP and a few weeks back they shifted their entire IM traffic from AIM to an internal, and much more secure, Jabber system. I suspect AOL has been and will continue to see this type of mass migration. HP has over 100,000 employees.
Of course, I recommend using our SDK. It's robust and fast, and is way ahead of libgaim and other libs in terms of functionality.
Unless one of the following applies:
Fuck yeah, solutions! I could use some solutions!
Its all well and good to allow people onto the AIM network legitimatly.
:)
BUT, until you change the licence, most of the popular alternatives will still be considered "illegal" by AOL.
Specifically, if it really IS possible to connect to AIM (and use full features) from an alternative client without using the AOL SDK (e.g. what clients like GAIM and Miranda use), there needs to be legal say so from someone at AOL (not just a random slashdot posting from someone who may be an AOL employee or may be impersonating one).
Also, the restriction about using GPL etc code needs to be changed so that it only applies if:
A.The client is linking to code/modules that are (C) AOL
and B.The licence applied to the client requires that the (C) AOL modules are open sourced. (e.g. "This program is under GPL with an exception that lets you link with the official AOL SDK modules" would be ok)
This change would basicly mean that any licence for the code is OK as long as such licence does not require that the AIM libraries are open sourced.
And, most importantly, the restriction that prevents one from making "legal" AOL clients that also talk to ICQ, MSN, Yahoo, XMPP, Jabber, IRC or other IM networks must be removed.
Since I doubt AOL will be willing to make this last change, clients like Miranda IM (which I use), GAIM and Trillian will likely remain "illegal".
Also, the restrictions on building "wireless" clients might hurt open-source prjects, especially with the (IMO) vague definition of what counts of "wireless" (Does using AIM on my PC at home connecting to my WiFi router count? Does using AIM on my laptop in a WiFi hotspot count? Does using AIM on my laptop with a wireless data card or mobile phone with internet access count?)
I think the intent of the rule is to prevent people writing AIM clients for mobile phones, PDAs, Smartphones and other things that have "mobile phone" functionality built in (both because AOL makes so much $$$ from licencing AIM to the manufacturers and because the carriers demand limits on what AIM on their network can actually do) but regardless, a clearer definition of what counts as "wireless" under the licence would be nice
Also, its not clear what is required to be "fingerprinted" for the purposes of getting a development key, the client EXE or the AOL plugin DLL (or both)
I'm fairly sure AOL provided this developer kit to diffuse the anger of people revolting over their two-tiered email plans; the plan to offer spammers the chance to guarantee delivery of their spam for a fee. "They're just geeks, distract them from the creamed corn by throwing them the steak and you'll be on the front page of Slashdot in seconds." "Piffle," as one AOL "advocate" put it.
In a world with hundreds of free Jabber servers, one free AIM server means dick.
Yes, but jabber.org goes down.
Also, just one day, someday, I'd like to be able to successfully transfer a file from gaim using *any* protocol to another user. I've tried and tried and never succeeded. I'm sure that somewhere, someone must have functioning file transfer, but I've never actually observed it with my own eyes. These days, I'm behind one of those damn NAT routers (though I have a SOCKS server running) and still can't manage it.
Any program relying on (nontrivial) preemptive multithreading will be buggy.
OTR is great. Multi-protocol, easy-to-use, widely-supported end-to-end encryption. If you aren't using it under gaim, you should be.
For Fedora users, you want the gaim-otr package, available in Fedora Extras.
Any program relying on (nontrivial) preemptive multithreading will be buggy.
Yes you might not have license freedom but you have technical freedom. I don't see how this cannot be a step in the right direction.
With Jabber/XMPP I already have both technical freedom and license freedom. How does OpenAIM address the issues of my other comment better than Jabber?