Yeah, I had the same question myself. I think that's what you would want to do to make it airtight (plus some amount of rate limiting or flagging for devices that are part of dedicated device farms).
replyBut even if not, there's still value in raising the barrier to entry. For example, you can buy 1000 reCaptcha solves for $1-2 from various captcha-solver services. And yet that $0.001-per-request fee does discourage mass-scale bot attacks.
... You... think... it would be a good thing.
replyDon't you...
I do. It has downsides of course, but what's the alternative at this point?
replyDepends on your specific problem. Usually redesign your system not to need to care if the other end is a bot or not.
replyHow though? Can you also avoid DDoS simply by designing your system to not care if the requester is a bot or not.
replyLet's say I'm running https://grep.app/ for example. AI bots start heavily using it, costing me a ton of money. How would you magically design this so it doesn't matter if the end bots are using it?
Rate limit individual clients.
replyLet's play this out: how do you determine individual clients? By ip? By seasionid?
replyI suspect that the HN crowd is somehow insulated from the river of crap and fraud that is the internet experience for a majority of the population.
replyJust show us your face and transactions history, it's about the kids.
reply