kevincador
commented
1 year ago Hey @vankasteelj,
I have had the same kind of issue in my app. Instead of introducing a delay, I'm looking at the "retry" info int he response and I retry after the amount of time that info gives me. IMO it's better that way because it's not working on some hardcoded artificial delay. I'm of course never showing a 429 to the end user, it's just use internally to know I have to queue the request and restart after X.
Cheers,
Kevin
Hi, I recently introduced comments/reviews on my own app based on trakt api, by displaying a popup that said "you watched X episodes of this show, would you rate and review it?" or "you watched this movie, would you rate and review it". Sadly, it often errors with a 429 "Too many requests" because I try to simultaneously send a comment and a rating (there's probably a few ms here and there for V8 to process the two requests, but still, it's "almost" simultaneous).
Would you consider adding a way to add a rating to a comment and/or disabling the rate limit on some call, maybe /rate and /comment specificaly? I cant be the only one that sees the common denominator in those two calls.
In the meantime, I will introduce a 1sec delay between the two requests, but still, it's annoying :) Thanks!