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
-
Show this thread
-
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
4 replies 2 retweets 15 likesShow this thread -
Replying to @Pinboard
can I make a suggestion? How about returning the bookmark entity in the POST/PUT /bookmarks/ response? This would simplified for client applications; they wouldn’t need to make an additional call to get the bookmark data. Client applications can take the response and cache it.
1 reply 0 retweets 1 like
That's a great idea; thank you!
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.