Another API developer contest has launched: Google’s Desktop Gadget Contest. Here’s how they describe it:
Do you have what it takes to create a great Google Desktop Gadget? Have you been waiting for some motivation to prove it? Well, good news — the Google Desktop Gadget Contest is here to spur you into brilliant action.
The contest runs until July 31st, 2006 and, while supplies last, each developer who submits an approved gadget will receive a limited edition Google Desktop Developer T-shirt and have their gadget shown to millions of Google Desktop users around the world. A panel of judges will also award three prizes based on popularity, visual appeal, use of new features and creativity. We’ll award $5,000 to the first place winner, $2,000 for second place, and $1,000 for third place.
Now added to the /contests page.
Remember Microsoft Passport, er now Windows Live ID? Google has just introduced their entry in the space, which is now more of the Identity 2.0 space. For details see thier new Account Authentication Proxy for Web-Based Applications page. And check Garett Rogers post at ZDNet for a concise summary.
It was only earlier this week there were a couple of interesting posts on Web APIs and authentication worth reading: Julien Couvreur’s piece on Web API authentication for mashups with follow-up by Dare Obasanjo. As Dare notes, “The devil is in the details when talking about authentication, authorization, and Web APIs.” This is indeed one of the biggest obstacles in making mashups a more serious business.
Continuing this week’s review of good new mashups, here are a few built using Amazon’s API:
Our review of the best new mashups continues and even includes some good non-Google-maps mashups (yes, they exist):
More tomorrow.
Here’s a sampling of the best new mashups added at ProgrammableWeb recently (go here for the full list of 789 mashups):
More best-of coming this week.
Yahoo! this week introduced a new Plug-in SDK for Yahoo! Messenger. It is a JavaScript and C++ API for building features to run inside their IM client. Some initial plug-ins are over in the Yahoo! Gallery.
There is a new Messenger API entry on the ProgrammableWeb site.
In AOL news: Open AIM continues to expand functionality, now with AIM bots, location-based services, and PC-to-PC calling. Since AIM supports SMS you can access the bots via your phone (like the Wall Street Journal bot). The location service is also designed for mobile devices — it can use the network to determine location and, at the user’s discretion, allow buddies to see this data.
The AOL AIM profile is here and AOL Presence here.
As noted by Amazon’s Jeff Barr over in the good Amazon Web Services Blog there have been some updates to the Mechanical Turk and S3 APIs. Interesting feature enhancements. For S3 this includes virtual hosting and hierarchies of keys and for Mechanical Turk this includes event notifications (email or web service call) and rich media HITs. The S3 Updates are here and the Mechanical Turk updates are here.
You can view their API profiles and see some early mashups in the ProgrammableWeb database: S3 and Mechanical Turk.
Marc Hedlund over at O’Reilly Radar points out an interesting discussion at FlickrCentral. The gist of the initial question revolved around whether a competing photo service should be given an API key so they can directly use Flickr’s API to move a customer’s data directly out of Flickr and into theirs. After some back-and-forth and internal debate, Flickr’s Stewart Butterfield said “we definitely should approve requests from direct competitors as long as they do the same. That means (a) that they need to have a full and complete API and (b) be willing to give us access.” Marc calls it API parity and notes that the basic questions revolve not so much around APIs but freedom and ownership of data.
More on the discussion from Dave Winer, Marc Canter (with comments from Stewart), and Nick Carr.
The photo search engine Riya now has their own API. Nice, clean REST model API includes access to their well regarded facial recognition search. More on the API itself from Dan Farber at ZDNet. They will soon release version 2.0 of the core service, an upgrade that moves them towards a more generalized visual search engine. Good details on that upgrade at at TechCrunch.