In a previous post I noted that the transfer of Delicious from Yahoo! to AVOS had caused the WordPress Delicious widget to break. Having been slightly ‘out of the loop’ for a day or so, due to an out-of-the-office development strategy meeting, yesterday, I returned to the office this morning to discover Delicious’ beta status blog.
It’s encouraging to see all the progress that Avos is making in resolving the issues that so many people have encountered during the transition, but there’s no mention of the WordPress widget issue that I (and so many of you out there) are having.
At this point I should state that here I’m considering the Delicious widget in the hosted (free-to-use) WordPress system, not the roll your own .org version.
I did a bit of sniffing on the requests made by the widget when the page is loaded, and it’s hitting the Delicious feed URL requesting JSON formatted data in return. In my case, the url is ‘http://feeds.delicious.com/v1/json/adycoles‘. This is returning a (very pretty, but useless) Page not found HTML page, which isn’t going to help a script, let alone a human being.
I’d like to point this out to the Avos people – that there is a JSON version of the API that they’re seemingly not considering (all information in the aforementioned blog discusses only JS endpoints) – but the blog is not open to comments.
I’m going to send an email and see whether that gets the wordpress.com community any further attention (or, indeed, any attention at all).
Watch this space.
Update: 4th October 2011
I’ve decided to replace the Delicious widget with an RSS feed. Not ideal, but a work-around. See later post about it.