What are the best methdos to prevent those bots, while also having a frictionless UX ? I've heard of Cloudflare. Will that pop for every user or only for those who are trully suspicious ?
Thanks
What are the best methdos to prevent those bots, while also having a frictionless UX ? I've heard of Cloudflare. Will that pop for every user or only for those who are trully suspicious ?
Thanks
Happy to talk more details about PoH (disclaimer: I'm a cofounder and this is my YC S23 company)
Asking because as a dev I hate when sites don't allow bots... however can appreciate that automation should be rate-limited. IOW, isn't preventing bot access actually an anti-pattern since rate-limiting is sufficient?
I see a lot of marketing which bashes Turnstile [detection] rates and tries to leverage this misunderstood nuance. And, it seems to be a dishonest point of contention but am willing to hear opposing arguments.
Thanks.
Cloudflare is really good at network bot detection. Rate-limiting is super helpful here, for example during DDoS attacks.
Our customers are a little different. They sometimes struggle with high-volume bot attacks (e.g. SMS toll fraud in ticketing marketplaces), but we specifically focus on online platforms that want to verify a human is on the other side of the screen. For example, survey pollsters and labor marketplaces want to stop a slow agent that can complete traditional CAPTCHA even if it's solving it a human speed
The downside is that their silly anime girl mascot is displayed whenever the challenge is running, which I think some people might find off-putting.
Edit: Are you going to announce the search engine on hacker news?
2nd edit: If you are making a search engine, this is probably a good article to read: https://archive.org/details/search-timeline It talks about various search engines that have disappeared mysteriously over the years.
reliefcrew•1h ago
https://developers.cloudflare.com/turnstile/concepts/widget/...