| Hi there! Original commenter . > So who is to say that the people complaining in the original post were using Turnstile or not? I'm sorry if that wasn't clear, but they were all using Turnstile (either in a Cloudflare Challenge or implemented in Turnstile individually). By the time of the original post, there was no difference between the two. > I didn't really see anywhere in the post where it discussed why they were getting so many false positives, and blocking real humans If you take a look at the section on what we learned in the beta, we mention the two biggest sources of false positives we received during the beta period are 1) incorrect system time and 2) privacy settings that restricted the execution of third party scripts entirely. In both case, there wasn't an easy "just fix it" option, but we surface the issue obviously in the managed challenge and via a Turnstile error callback, which should allow users to see clearly what the problem is. We've also finished rolling out (update on the blog article, which states this was in progress) our challenge feedback reports, so we can better track when groups of users are impacted in ways where they can't render the challenge in the first place. This was an area where we had difficulties understanding the scope of a problem previously, because our telemetry relies on the widget to load in the first place. We'll continue to use the new data we're gathering to continue making reliability improvements when we find issues. Ensuring we can accurately identify human users is fundamental to the success of Turnstile as a product, so this will always be a high priority for us. |
It all makes sense now, but I guess my biggest "hurdle" was knowing if those people in the original post were using Turnstile or not, and the blog post being relevant or not totally hinges on whether or not they were using Turnstile.