-
Notifications
You must be signed in to change notification settings - Fork 15
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
Honeypot issues #60
Comments
I'm also getting spam every now and then. |
The honeypot is indeed a very basic protection that probably most of the bots nowadays are able to bypass. I included it at the time because.. whynot. The only fireproof solution that I knew of were advanced captcha, and without enabling that the sum of the default mechanism that I implemented seemed to filter most of the spam. I didn't study the subject for a while, but feel free to give insights about possible improvements. |
I think honeypots are still a good basic protection. But I also think that a text field would be better than a plain checkbox. My gut feeling tells me that bots are trained to fill out text fields but don’t care too much about checkboxes. So, perhaps let’s try to change the current checkbox for a text field (or even have both?) and see whether that helps? |
I’m getting spam emails despite having the honeypot setting checked, so I was going to see what I can do. Is the honeypot field that hidden checkbox with name “p01-contact_fields[totally_legit]”? I have no idea how spam bots work but isn’t a plain checkbox a little too simple to get around?
Also, I tried to uncheck the setting to use a honeypot field out of curiosity but apparently this isn’t working, i. e. after saving the settings it will still/again be checked.
The text was updated successfully, but these errors were encountered: