Conversation
|
Hi, I've now tested most of the API functions. The delicious API docs are not always consistent with the implemented delicious API itself. This is an overview of what I found: posts/update
posts/delete
posts/all
posts/add
posts/get [Done]implemented versions are bold
posts/recent
posts/dates
Other functionsposts/publicThis function does not exist anymore in delicious (and docs) posts/suggestionNot implemented in semantic scuttle tags/getsemantic scuttle returns tags with underline tags/renameSeems broken in delicious. Semantic scuttle works according to docs tags/deleteSeems broken in delicious. Not implemented in semantic scuttle What now?Many of the changes would not be backward compatible. So I think it would be best to offer the new API at a different location (e.g. Also I will inform delicious about the differences between their documentation and their implementation that I've found. EDIT: The timezones don't seem to be a problem at all. Everything is stored in UTC. I removed the corresponding lines from the problem and will undo my "fixes". |
Hi,
It seems, that the Semantic Scuttle API is not up to date with the current delicious API. Some new features (like
hashes) are especially useful for client synchronisation.With this pull request I want to update the API to be fully compatible with delicious again. It is not finished, but I want to share the progress to allow early feedback.
Status:
So far, these API functions have been updated:
posts/all, including?hashesposts/get. See comment belowDifferences:
This is a list of functions, which are not fully implemented, because I'm unsure, whether they are usefull:
Compatibility:
The changes in the API are mostly backward compatible, as new features are added. I will list the incompatibilities here:
posts/all. Clients expecting all bookmarks to be returned will not show all Bookmarks (if there are >1000).posts/all: An empty result (no bookmarks) now returns<result code="no bookmarks"/>instead of an empty<posts>-tag.posts/getdefault date has changed and UTC is used instead of server timezoneposts/getthedtinpostsattribute does not contain the time anymore (just the date)About the XML header:
In delicious the header of the response is
<?xml version="1.0" encoding="UTF-8" ?>In semantic scuttle it is
<?xml version="1.0" standalone="yes" ?>I'm not sure if this is intended or even important. However, I used the header of delicious here.
Cheers,
David