DeliciousAPI 1.5.0 is now compatible with delicious v2

I have finally succeeded in updating DeliciousAPI to work with the updated delicious website/API. All users of DeliciousAPI should (actually: must) update DeliciousAPI as the versions prior to 1.5.0 will not work anymore.

DeliciousAPI 1.5.0 comes with some enhancements (e.g., the full public bookmark collection of a user can be retrieved now, or the title of a URL as stored on delicious) but also with some changes to its methods (e.g., get_number_of_users() and get_common_tags_of_url() have been removed due to changes on delicious’ side; however, get_url() provides the same data now). Similarly, I have chosen to parse the new JSON feeds instead of the corresponding RSS feeds where appropriate because the former have proven to be much faster in practice – at least in my experience. This switch from RSS to JSON also means that DeliciousAPI’s dependency on Universal Feed Parser is void; instead, it requires simplejson.

I’m still working on an issue with get_user() when it is called with both username and password. In this case, it uses delicious’ official API at api.del.icio.us. The method allows you to make a full backup of your personal delicious bookmarks. For an yet unknown reason, I end up getting lots of 503 errors, which indicate throttling. I’m quite sure that my tests shouldn’t have ended in throttling as DeliciousAPI complies with delicious’ API requirements – e.g. it does wait 1 second between queries – so I suspect that there is something else to be discovered. To make a long story short: I’m still investigating.

That being said, I have also some other features in the pipe, such as retrieving a user’s network members and fans. Stay tuned!

Update 2008-08-06: I have received several comments from readers (thanks!) who experience the same kind of throttling. Some are developers on their own, so it seems not to be the sole effect of how DeliciousAPI works.