Removing cloudflare on api
Cloudflare antibot on your api doesn't make any sense, i have a python discord bot with your api implemented and because of cloudflare i cant use the api anymore and i have quite a few users who use the function.
Anonymous
shared this idea
Cloudflare is absolutely essential for protecting the API from abuse. The only time it should get in the way of legitimate use is if you consistently exceed the rate limit and cause a 24 hour JavaScript challenge to implemented against the offending IP address.
-
There are multiple factors that can cause Cloudflare to reject the connection and unfortunately, some of them are beyond your control such as other parties being abusive and your IP being caught up in the pattern being blocked. Cloudflare is an essential part of the defences of the site and this idea will definitely remain closed.
-
Anonymous
commented
I also experience the same issue where for requests made on the API I get 503 even though I either make them at > 1000 ms diff from one another or even if it's the first request from an IP
-
I don't clarify this precisely as I don't want to provide information that could be used to circumvent the controls, but clearly if you continue to exceed the rate limit and ignore the 429 response then you're going to get given a temporary ban.
-
Anonymous
commented
Can you clarify what constitutes "consistently exceed[ing] the rate limit" ? I made a code error (putting a thread sleep after the call to download rather than before, meaning no rate limit was applied if a download error occurred) that meant I issued about 12 requests with only 200 ms each, and now every request is met with a 503. How many hammered requests are required to activate the 24h ban?