But, on the basis of our discussion, i would deduce you attributed the attempt to cloudflare, which is probably innocent and automated in such occasions.
All i meant is that it was either heavy traffic due to the particular day, or the a third party ddos causing it, or both at the same time.
But the captcha, i bet is a built in feature for those occasions, so no wrongdoing on their part. (being a dev, cloudflare always appeared to me as one of the most neutral startups ever, as well as prepared. This, on the occasion, is to me completely understandable on their side, in service of customer, in this case thedonald.win).
I just meant to separate between the requests to server and the server handler. I'm sure too, that the first could easily have been abused. All cloudflare can do in these cases to not charge or overcharge is such a thing.
This does not alleviate my feeling that something is going on.
I didn't say something wasn't going on.
I said that if this thing was a doos, cloudflare was doing his thing to make sure users could access anyway.
k, but I didn't mean to confront you anyway.
I didn't mean to confront you either.
But, on the basis of our discussion, i would deduce you attributed the attempt to cloudflare, which is probably innocent and automated in such occasions.
All i meant is that it was either heavy traffic due to the particular day, or the a third party ddos causing it, or both at the same time.
But the captcha, i bet is a built in feature for those occasions, so no wrongdoing on their part. (being a dev, cloudflare always appeared to me as one of the most neutral startups ever, as well as prepared. This, on the occasion, is to me completely understandable on their side, in service of customer, in this case thedonald.win).
I just meant to separate between the requests to server and the server handler. I'm sure too, that the first could easily have been abused. All cloudflare can do in these cases to not charge or overcharge is such a thing.
Cheers!