The deeper issue is that the API is not equipped to handle an obvious case (has anything changed for user X since time Y) that would reduce the need to fetch all bookmarks, an expensive query. That's the focus of V2 (draft here https://idlewords.com/pinboard_api2_draft.htm …) that I've been building
-
-
Show this thread
-
I'm trying to find a balance between keeping the punch-drunk V1 of the API on its legs and getting V2 to a state where it can go into experimental deployment and then take over some of the load. Once it's up and running, the pressure on the original should lessen a lot
Show this thread -
There's no plan right now to sunset V1 of the API (which is just the old delicious API from 2004), but I anticipate that enough users will switch to the newer version to ensure that no problem happens ever again in any part of Pinboard
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.