Rethinking Digg: please don’t forget the API!

There’s now an open survey at RethinkDigg (and rethink manifesto) for the planned revision of Digg after the Betaworks sale – it’s great to see open doors to ideas and thoughts from fans – especially since it’ll no doubt be a huge product challenge – also see the ongoing thread on hackernews and (also see coverage on places like Mashable).

One thing that isn’t mentioned anywhere though is the Digg API – and it would be sad to loose it (either in it’s current form or in some evolved way) in the mix. Digg launched it’s original API back in 2007 and was one of the early API pioneers – with a lot of mashups of the V1 API showing what could be done with social news information. The API was then relaunched in August 2010 and and also added a pretty cool streaming API similar to twitter’s. Although it’s not clear how many apps use the API today there were more than 60 mashups using the old API which was put into read-only mode in February 2010 (in the developer zone there are 100+ posts in the forums and the @diggapi Twitter feed has 700+ followers).

So far, there’s no mention of the API anywhere and Digg API twitter feed is silent on a some intermittent outages.

Even if traction on the new API isn’t high a Digg API, with the Face.com API recently mothballed it would be sad to see another API go so soon.

No doubt the betaworks team will have it’s hands full with development but I’m sure Digg developers would appreciate a heads up on where the API might go + an API seems like it would be a valuable asset to the new Digg too. Hopefully we’ll see some good news over time – if there’s a way we can help out on Digg API front, we’ll do what we can!

Whatever happens hopefully developers will get kept up to date.