Hey everyone—an update on API slowness today. The immediate issue is that the site is getting a lot of API traffic and once things bog down, it's difficult to identify the cause of the problem, as all queries get slow. So I'm doing my best to figure out which Jenga piece to pull
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 idlewords.com/pinboard_api2_…) that I've been building
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
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
• • •
Missing some Tweet in this thread? You can try to
force a refresh
