Codeposting - Tumblr Posts

it seems like tumblr's api has two ways of responding to too many requests. One way will actually respond with a 200 OK and set some error metadata stating that I made too many requests. The other way is a proper 429 Ratelimited, at which point my client will attempt to recover the same way it handles the not-429 429. I'm not sure if this is what tumblr is intending to do, or if they've made changes to the API under the hood throughout the day to keep knuckleheads like myself from causing too much trouble.

I've been.. testing the limits of the API, gradually increasing the length of time between booping. This morning I was able to do 500 ms between boops, then it started ratelimiting me like crazy, and so I increased it to 1000 ms. That went fine for the majority of the day, and now every 10 boops or so, I get ratelimited.

I also, just for sanity sake, introduce a little bit of jitter to the delay time. It's not precisely 1000 ms each time around, it's somewhere between 1000 and 1500. Just to see if I can throw off the API a little bit.