-
-
Notifications
You must be signed in to change notification settings - Fork 97
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] Remove Captcha #287
Comments
Do honeypots even work with open-source? Anyone can just read the source code and determine the correct fields that way. You only need a captcha when login in with email every 2 weeks, resetting your password and deleting your account. |
Thats more captcha than its good :D Sure, why not? Its just a field of the form thats made invisible to the regular user through various forms. Same colour as the background. Or just |
There are already people manually setting up catfishing accounts with the captcha in place. I'd be careful about making a decision to remove it because bot signups would increase. Yes, there are other ways to get around it, but for better or for worse, CAPTCHA is one of the more common ones. |
Well, this issue is about captcha and bot-accounts. Honeypot forms are a proven possibility to reduce the bot-registration by a high margin. Depending on how the captcha is integrated it would be possible to disable (not remove yet) captcha, integrate a honeypot field and monitor the registrations for a bit. Honeypot combined with a "that was too fast for a human" would probably plenty enough to get rid of bots. |
For a possible solution see: ip6li@c995bfe |
Captchas seems to be obsolete now because AI solutions are able to solve captchas better than humans can do. |
Maybe a captcha could be added to the signup page and removed from the login? |
If my pull request will be accepted I can modify code to make captcha configurable for each page which uses captcha. |
That would be awesome! |
See #310 |
Currently only password related services require CAPTCHAs. I plan on removing all passwords, and therefore CAPCHAs, see #314. Moving all future discussion there. |
Is your feature request related to a problem? Please describe.
Captcha is annoying. There are multiple other ways to combat spam-bots. The question is - did this get implemented "just because" or because it was a growing problem?
Describe the solution you'd like
This article has some ideas on what to do https://datadome.co/bot-management-protection/stop-bots-without-captcha-anti-spam-honeypot/
A regular honeypot-field should be enough to get plenty of spam-bots, of course it will not reduce manual registrations. See https://www.getvero.com/resources/add-a-honeypot-to-website-forms-to-reduce-spam/ or https://wordpress.org/plugins/registration-honeypot/ for example.
So, think of some steps that may be possible to take and include an open source captcha as last resort as well. Start with honeypot form and time-detection for example. That should get rid of a lot of bots without having to use captcha.
The text was updated successfully, but these errors were encountered: