Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google recaptcha - option threshold in config #48

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

miloslavkostir
Copy link
Contributor

No description provided.

@aryehraber
Copy link
Owner

Hi @miloslavkostir, thanks for the PR!

What exactly is the threshold config for? I was under the impression this was introduced to reCAPTCHA V3 (which Statamic Captcha does not support).

@miloslavkostir
Copy link
Contributor Author

OK, I overlooked information about not support reCAPTCHA v3.

I use this with v3 anyway - it works. If you use v3 keys (sitekey & secret key) you get score in response. Then you can compare it with threshold in config.

So, you can implement support v3 and use my solution or close this PR. In my web I extend Recaptcha class - it is functional as well.

@aryehraber
Copy link
Owner

No problem, I appreciate the PR anyways. And interesting to know that the addon works with only minor changes for reCAPTCHA v3.

I'm completely open to supporting it, it would make Statamic Captcha more well rounded too. My issue with reCAPTCHA v3 is as follows (and I'm hoping you can perhaps shed some light on it for me):

I implemented reCAPTCHA v3 on a client site a few years ago, thinking it was basically just an upgrade of v2. What ended up happening, however, was that we noticed real users were also getting blocked, for some reason Google was returning a low score for a % of actual customers/leads. And unlike reCAPTCHA v2, there is no way for a user to "redeem" themselves by solving a captcha/puzzle, they simply can't continue at all and therefore could not submit forms.

Since I don't want to over complicate Statamic Captcha to handle these types of cases, I've been hesitant to support v3.

What has your experience been? What do you do in the above scenario?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants