Slashdot Mirror
AOL Opens ICQ? Well, Kinda.
daveuserland writes "Dan Gillmor got an email from Yossi Vardi of AOL pointing to a site where they document the API for ICQ. This is quite interesting. They have a long license agreement, so it's not exactly an open spec. I posted the agreement here so it's easy to read (on their page it appears in a tiny scrolling text box). I'm curious to know if their API is XML-based and if it is implemented in SOAP and/or XML-RPC." Wow - I just finished reading the restrictions - my favorite is the "10,000 copies" limit, as well as the continued prohibition against people under 13 years old. With "open" like this, who needs closed?
why yes, i do agree that Steve Case will do all my laundry for the next decade!
You have to understand that this wasn't AOL's idea.
Some idiot lawmakers in the US passed a law making it illegal to store information about anybody under 13. Including, ironically, the fact that they're under 13.
The only way online services can protect themselves is to forbid anybody under 13 from using the service.
The only thing Americans can do to fix this is vote for better lawmakers.
-
This gets announced the day before Microsoft's Hailstorm announcment, where Microsoft starts letting out some details to show why AOL better get their act together. Combine that with the fact that MSN Messenger now has more users than AIM, and it sounds like AOL's begging for free help from the open source community to save them from Microsoft and Hailstorm.
Cheers,
Are you talking about http://www.icq.com/api/ ? Unless Mirabilis has changed something in the downloadable zip-file since my last visit, it doesn't look like something new has happened.
The ICQ API has been for download for quite a long time, really. I remember trying it out a 3-4 months, but the documentation was nearly non-existant. This link just points to their API, not any documentation, unless it's hidden in the icqapi.zip.
As for their license... yeah, I actually read it back then (I clearly remember the part about 10,000 copies), at that one hasn't changed either.
With "open" like this, who needs closed?
Who said it was open? :)
Huh? What?!? The ICQ API has been available for quite a while on Windows, I am sure of this because a friend of mine who writes encryption based ICQ plugins told me about using it almost a year ago.
As for the protocol being XML based. It isn't if not we'd already know about it because all the ICQ clones would be using an XML based protocol instead of the ICQ protocol (yes, it's available on the web).
So I can't use the API for a chat protocol to write a chat program. So what good is it?
You copied their license agreement to a different web page? What are you, nuts? Are you trying to get sued or something?
-- dR.fuZZo
I think AOL is trying to just appease the FTC with its monthy releaseses of just so little more of the messaging specks and open-ness
In other words I think they are trying to release it so slow that it will not matter when they fully release it... but all the while releaseing just enough to keep the FTC happy.
I think the whole community has been sick of AOL picking up companies such as ICQ and just prick-teasing us with idle promises of opening it up. I'm kind of doubtful as to how much AOL will actually put out, especially having looked at the age and size limits in their "agreement." Nonetheless, at least AOL is making some effort to allow ICQ to be examined and probed vigorously by programmers and source code readers, and I think this will benefit both users and the company's reputation in the long run. As another thought, perhaps AOL is tossing the community a small bone in attempt to cover up/improve its image after all the raping of consumers and software technologies it has done.
"The most fortunate of persons is he who has the most means to satisfy his vagaries."
"The most fortunate of persons is he who has the most means to satisfy his vagaries."
- Marquis De Sade
This has to be one of the funniest and stupidest statements I've seen. For those who use ICQ/LICQ/MICQ/etc/etc when was the last time anything you did via the client was validated by the server. It sounds all good to parents and law makers who don't know any better, but my info states I'm about 12 years old, I live in Lithuania, etc., so much bogus information it'd make a wanted felon cry with envy. This is like (in my opinion) the case with some of these online cigarette companies, who were selling tobacco to kids under the age solely because they ordered with a credit card. Well sure if they have a credit card they must be legal, just don't verify they might have gotten the credit card number from their parents... Sure.... no need to verify, step right up for your Marlboros
I wonder how those who oppose Israel's (sometimes harsh) laws will feel about this. I think I'll go do some patent research and sue someone, anyone, for the sake of popularity.
vroom vroom
360 degrees of Karma
Indeed it is, and the other files are dated 1999, so no, it's not very new at all.
The API was not that very extensive either, and the code that was supplied was simply interfaces defining the methods, no code behind it.
Any slashdot readers that might find this code useful? I'm not entirely sure why it was even released, do they want people to make applications calling these methods?
It's the same document I downloaded in 1998 when I was playing around with an SMS->ICQ gateway. Read the ICQAPI.doc file, it's dated 20/2/98.
Why don't people actually check it out before debating what this all means in light of the FTC?!
This is no more open than the Microsoft Win32 API you can find on MSDN.
As for the submitter's questions about whether it uses SOAP and XML-RPC - why didn't you look at the API, with a 10-second look you can tell that it's just a Win32 DLL interface!