requestors

If instead requestors get balance, adjust and then send a set balance, you have a classic race condition.

It's a good mitigation when you have legit requests, and some requestors create far more load than others.

But a solid question of how to handle multiple requestors but there’s only one body to go around.

Sometimes getting it right is the sensible solution even if it doesn't fit the requestors timeline.

If the techies were paid for responding to off-hours requests, and the requestors were billed, only urgent requests would be made.

Have you thought about letting review requestors add a comment to guide the review toward a specific question they're trying to ask?

Whoever was maintaining it kept doing things at the whims of issue requestors.

All retailers such as Amazon would become Token requestors in this concept.

I think the way described above, of listing top requestors, doing statistics and then automating blocking is indeed the best way.

There's little downside in doing this, especially against small requestors.

Mesos delegates it back to the requestors, as I understand it.

MTurk requestors must have a US address.

I'm not against trying to make things more "private by design", e.g., proxying to scrub requestors before the CDN sees the hit, or replicating resources locally.

I think the author understands that "have a little empathy" is a request to modify their behavior, but expresses their frustration that the request is unclear and (in the author's experience) the requestors won't clarify the request.

I had the idea of sending requestors a challenge like "Flip the bit at position i of the large chunk of stored data, hash the result and include the hash in your headers".

Granted, that system can be initially gamed by serial refund-requestors - but those people are further along the spectrum of "will not pay" anyway, but at least they've taken the step of purchasing, that's one step closer to making inroads into the pirate instead of purchase segment.