Look I'm just trying to distinguish "active circumvention of blocks" from pretty much everything else. Because the former is what destroys the usefulness of protocols while the vast majority of other things can be trivially resolved by blocking the offending party. Including { corporate service } that I don't use sending me { unwanted thing }.
If a bot that sends a fixed set of headers and is behind a single static IP is behaving poorly and slowing down your server you can block it and move on. Whereas when an abhorrently selfish operator with a client that actively hinders fingerprinting rapidly rotates through hundreds of thousands of IPs you end up with mass adoption of solutions like Anubis.
Look I'm just trying to distinguish "active circumvention of blocks" from pretty much everything else. Because the former is what destroys the usefulness of protocols while the vast majority of other things can be trivially resolved by blocking the offending party. Including { corporate service } that I don't use sending me { unwanted thing }.
If a bot that sends a fixed set of headers and is behind a single static IP is behaving poorly and slowing down your server you can block it and move on. Whereas when an abhorrently selfish operator with a client that actively hinders fingerprinting rapidly rotates through hundreds of thousands of IPs you end up with mass adoption of solutions like Anubis.