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
-
-
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 -
-
-
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.
-
That's a great idea; thank you!
End of conversation
New conversation -
-
-
The 1) `GET /delta` endpoint, 2) being able to retrieve, in one call, bookmarks from a list of ids (which I would get from the delta api), and 3) having the just added bookmark in the response of `POST /bookmarks` are the things I missed the most when implementing my clientpic.twitter.com/vYnVJPchsm
-
That's super helpful feedback; thank you. I'll make sure all three are in place.
- Show replies
New conversation -
-
-
I notice no matter how many results I try to get from the current /posts/all end point, Pinboard ends up spend the same amount of time to prepare the respond. Ended up switching to /posts/recent instead and it speeds things up a lot.
-
Yeah, because the wait time is determined by the number of requests in the queue. Avoid posts/all as much as you can.
- Show replies
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.