Beginning on October 5th, some Delicious APIs will start returning URLs that redirect users through delicious.com before reaching the final link. Most users will not notice this change, as all links stored on the Delicious website are already redirected through this same pathway.
There are two exceptions for which Delicious will still return the raw (original) URLs in the API response:
- Requests for exported links
- Requests for a user’s own personal links
Why is Delicious providing redirect URLs for API responses?
Delicious currently serves 2-3,000 RSS / API requests per second, and is committed to being a free and open service that is safe for all users. Returning redirect URLs in the API response protects users by allowing Delicious to check all links against a list of spam websites and warn users before entering those sites.
Delicious currently serves 2-3,000 RSS / API requests per second, and is committed to being a free and open service that is safe for all users. Returning redirect URLs in the API response protects users by allowing Delicious to check all links against a list of spam websites and warn users before entering those sites.
What will redirect URL looks like?
To avoid returning redirect URLs with a lengthy number of characters, Delicious will use the link shortener icio.us.
To avoid returning redirect URLs with a lengthy number of characters, Delicious will use the link shortener icio.us.
Who does this change impact?
This change may impact developers who have built applications that cluster links by domain based on the raw URL. Where possible, the API will return a new field, ‘expanded_url’ , that will contain the full URL, for users that explicitly need the unshortened URL.
This change may impact developers who have built applications that cluster links by domain based on the raw URL. Where possible, the API will return a new field, ‘expanded_url’ , that will contain the full URL, for users that explicitly need the unshortened URL.
No comments:
Post a Comment