Conversation
|
While this code works on this repo and potentially adds a level of obscurity to the requests, after testing, it doesn't help the refresh rate. Happy to dump this PR if there's no need for it |
|
Hi @c-m-hunt, thanks for putting this together and trying it out. Sad that it doesn't seem to help. If it is the case that it does not help, I think we should close this PR - but I have a question first. Are you still seeing rate limiting if you keep the refetch time to 1 minute? Or are you only seeing it if the refetch time is below 30 seconds? If it's only below 30 seconds, I might ask: why do you need to do this? What I've discovered is that Twickets batch-add ticket listings to their feed, and they don't do this every minute. In fact, it seems they do this every 2-3 minutes. I guess having a low refetch time would allow you to pick up when this batch add is done sooner, but I'm interested in why you think you need to refetch that often. Sorry for my questions, but I'm genuinely interested, and I might have an alternative solution if there's a use case for this. |
It seems that rate limiting works on a combination of source IP and API key so providing a list of proxy servers can allow us to hit the endpoint ever 30 seconds per proxy. Using NordVPN's proxy list, we can hit the endpoint every 5 seconds.
For tests, set up
.envHave added new instantiation method to not change the existing interface.