2 ms·
"I don't know what I did wrong, but I've angered one of the titans of the internet!" Why would anyone need to know what they did "wrong"?^1 That would mean th
by 1vuio0pswjnm7 4y ago
"I don't know what I did wrong, but I've angered one of the titans of the internet!"
Why would anyone need to know what they did "wrong"?^1
That would mean they could correct their choice of software and usage patterns to conform with what Cloudflare believes is "right".
IMO, anti-"bot" (anti-automation measures) can effectively identify
(a) computer users with something of value to offer to website operators (usually, that means personal data/metadata at no cost), as distinct from
(b) computer users who
(i) do not send personal data to and/or generate metadata for website operators that indicates the user has something of value, and/or
(ii) are not using the software preferred by website operators (usually, that means software that requires interactive use that generates behavioural metadata for website operators).^2
The measures taken by Cloudflare presume any automation by computer users is "wrong".^3 Meanwhile, websites and CDNs are free to use automation however they wish.
Of course automation can be used in a way that poses threats to websites. It can also be used in ways that do not pose any threats. The "protection" measures used by Cloudflare cannot distinguish between the two. IMO, these measures are deemed acceptable by website operators (Cloudflare's customers) because computer users blocked accidentally are more likely to be in catogory (b) not (a).
A more egalitarian approach IMO would be to publicise detailed rules for website usage. That is, provide an explanation of what the website operator/CDN considers "wrong". For example, a list of permitted software, the maximum allowable number of requests in a given time period, etc. IMO, the rules would likely be incriminating. For example, they might be discriminatory and/or anti-competitive and subject to legal challenge.
1. Another interesting question is why the website operator/CDN believes it is "wrong". It appears the OP's www usage is not posing any "threat" to Cloudflare's customers or partners. As such, there is no justifcation for blocking the OP.
2. For example, software that sends personal data to website operators, software that prominently displays advertising, software that provides "payment handlers", and so on.
3. Forcing computer users to choose "interactive" software that is generally unsuitable for automation, such as popular web browsers or mobile apps.