27 ms·

Or you could mess with a random percentage of the requests: tarpit them, drop random packets, reply with malformed answers etc. If you keep the percentage low t

• toast0 4y ago
  If the rate limit is high enough, and pooled across all matching requests, you'll get different effects depending on the (global) concurrency, which might be tricky enough. And it might lead people into the right direction anyway.
• chitowneats 4y ago
  Seems like there's no need for this. HTTP spec covers "too many requests" already. Why further antagonize things rather than clearly state the problem?
• qwery 4y ago
  While amusing, responding in this way seems overly antagonistic/escalatory. i.e. the behaviour of a poor citizen of the web. It also would be likely to result in an increased number of requests? Drew's actions so far (as far as I can tell) are not only inoffensive/reasonable but overtly good-willed and presumably result from a considerable amount of effort.
  • xigoi 4y ago
    As if Google's response (that they, the largest tech company in the world, can do nothing about it) wasn't antagonistic…