When trying to request the following endpoint from a DigitalOcean server, you are immediately rate limited (returning response code 429) after 1 request. When running the app hosted on the server locally, or just by requesting the API through a browser, this rate limit is not nearly as heavy. Is it intentional that this endpoint is essentially completely blocked from DigitalOcean servers?
It could be possible, though I did try paying an extra $25 a month for DigitalOcean’s “Dedicated Egress IP Address” feature which to my understanding should eliminate this possibility, though this issue was still occurring. Since the exact same issue was occurring for other endpoints in the other 3 posts I linked above, I assume the “Too Many Requests” error is actually inaccurate.
Funnily and coincidentally enough, I just decided to implement my own follower tracker Discord webhook on my DigitalOcean API and I can reproduce this exact issue. I’m going to do some investigation to see if modifying any of the request data and/or using a proxy can solve the issue.
Yeah, seems like they’re blocking any DigitalOcean IPs so nothing in the request can be modified to bypass it. As you spent $25 on DigitalOcean’s dedicated IP address feature, I’m assuming you’ll be happy to purchase some proxy IPs from https://proxy2.webshare.io/, which I highly recommend. You can then route the requests through them to avoid the rate limits - just tested this myself and it works. Note that you’re given 10 free proxies as soon as you sign up, so even just these could work for small-scale applications, but I’m assuming you’re using it to check if user A is following user B (for Kohau?), so you’ll probably need to purchase more IPs/bandwith for that use case. An alternative solution is passing through an account cookie in the request, as logged-in users get lesser rate limits than logged out ones.
Engineers: this is a temporary workaround and the issue at hand should still be resolved
If you need any further help with this, let me know in PMs.
