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

Feature Request: reCAPTCHA Integration #306

Open
jaswrks opened this issue Oct 26, 2016 · 2 comments
Open

Feature Request: reCAPTCHA Integration #306

jaswrks opened this issue Oct 26, 2016 · 2 comments

Comments

@jaswrks
Copy link

jaswrks commented Oct 26, 2016

A customer writes...

Wondering if there were any plans to add reCAPTCHA to the subscribe page. Currently I have one for the comments form, but the subscribe page is completely wide open to spam. If no plans, please open a feature request or if it is easy enough, possibly try to guide me in doing this.


Thoughts by @jaswsinc ...

Since email confirmation is required by the default configuration of Comment Mail, a reCAPTCHA is not necessary. However, if the 'Subscribe w/o Commenting' feature is used together with settings that effectively disable email confirmations (which is possible in Comment Mail), then a reCAPTCHA becomes a much more desirable feature.


Estimating this at 2 days work.

@alexstine
Copy link

Just to add a bit more here, confirmation is good, this will eliminate spam for sure. I would however like this feature so the spammers wouldn't even hardly have a chance to get on the Pending Subscribers list. This clears every 15 days on my install, but if I can stop spam before this point, that would be ideal.

Thanks.

@raamdev
Copy link
Contributor

raamdev commented Oct 27, 2016

@tech55541 Thanks for the feedback. I agree, an optional reCAPTCHA integration would be nice as a first-level of protection against spammers, with email confirmation as a backup.

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

No branches or pull requests

3 participants