If a cURL call is slowing down your website, that usually indicates that there is a problem with the endpoint you’re connecting to. You can mitigate these effects by setting the timeout options in cURL, so your script can terminate cURL so you can handle the error, instead of letting the server terminate your script.
But in this case, the issue is indeed that access to the Discord API is blocked due to abuse.
If everyone wanted this white list they’re more than welcome to show code, if they’re not willing to show code then they’re not willing to get whitelisted?
We never do special requests. Special requests take a lot of staff time to review, staff time takes a lot of money, and you’re not giving us any money.
If you feel your site is important enough to warrant that kind of personal attention, it should also be important enough to spend $20 per year on for a Premium Lite hosting account at iFastNet.
Well, you’re asking us to disable security measures we purposely installed and manually dig through your code to figure out it’s safe.
Vetting code can take a long time if you need to skim thousands of files to ensure that nothing bad is being done in it. That’s more likely to take hours instead of minutes.
And that’s assuming that it’s possible at all to lift this restrictions for individual accounts in the first place. These blocks may be implemented on the server level, in which case that would have to be implemented first.
So no, it’s not just looking at your account for a minute or so and clicking a button, if that’s what you thought.