I'm attempting to build a web-based rich client and hitting some issues, in particular attempting to set the capabilities in order to allow new features.
Making a call to presence/setState with the parameters as listed at:
http://dev.aol.com/aim/web/serverapi_reference#setState
(Passing the capabilities as a 32-char hex string, as suggested, single or multiple, comma-seperated, custom or even copied directly from a query to the official AIM6 client)
The server seems to totally ignore the assertCaps and interestCaps parameters, it returns a user item without them, and accessing the user's presence through another client it's clear they have not been set.
Anyone have any idea what's going on or how to set these capabilities through a web app?
Edit: FWIW, requests from both my custom client and directly through a web browser using the sid from an established session return the exact same result, so it shouldn't be a problem with the client.
Re: Getting a developer id
Thanks. I'm surprised to get an answer since I know AOL Pictures is pretty much dead or dying. Good thing somebody is keeping an eye on this forum regardless.
I looked at the XDrive APIs. No thanks, unless somebody can give me a couple of lines of perl equivalent to this simple HTTP GET to, for example, fetch my public gallery pictures tagged "snow": http://api.pictures.aol.com/gv1/pictures/getTaggedPublicPhotosByUser?f=json&devId=MYID&h=THEHOST&locale=en_US&t=waistmanager&tag=snow
Want to bet on whether the XDrive APIs have more or fewer bugs than do the AOL Pictures' APIs? And how long till those XDrive APIs get extended far enough so I can accomplish the simple request above? Oh, and what do I do when Bluestring dies and something else rises up to take its place? At least maybe that would be AOL Pictures, resurrected, and I'd have at least a prayer.
Sorry I'm so bitter. Vote for Hillary.