3 ms·
It's not (just) about load: it's about unwanted scraping, retail bots grabbing inventory before humans can, credential stuffing done slowly and widely. All mann
by jgrahamc 5y ago
It's not (just) about load: it's about unwanted scraping, retail bots grabbing inventory before humans can, credential stuffing done slowly and widely. All manner of unwanted interaction with a website or API.
- lucasyvas 5y agoThere are other solutions to at least one of the cited problems. I added an anecdote above and I'm hoping to see what you think. I would challenge that there is no such thing as unwanted traffic if it's publicly accessible - If you want it to be stricter, you should be requiring accounts with strict purchasing limits matching that of a normal person by default. No "anonymous" purchases, and a more appropriate identity vetting on account creation.
- yunohn 5y agoI think the weakness in your assumption is that CAPTCHAs exist solely to solve retail scalping by bots. It serves a much larger purpose - mitigating bot load in aggregate across an entire domain or network. Maybe you’re assuming that DDOS/bot attacks are rare? Because they’re not (1). If you let all of them continue willy-nilly, obviously it’ll get overwhelmed at some point? Plus, why waste so much server energy/time serving malicious load… (1) https://blog.cloudflare.com/network-layer-ddos-attack-trends-for-q4-2020/ https://blog.cloudflare.com/network-layer-ddos-attack-trends...