I guess I complained to soon. The solution was simply taking out all spaces in the honey pot field name and honey pot error message. I also deleted the question mark in the honey pot field name. I’m not sure which of these “three” changes was the answer, but it worked!
I do have one question about the hidden field idea…
If WP armour knows to only show the extra field to bots, then why is a “Hidden field” necessary? Wouldn’t it make more sense to just filter out the bots based on what told you it was necessary to present the hidden field.
Or is it necessary to let them fill out the hidden field so that they get a false positive and are none the wiser? And therefore don’t know that they need to work on perfecting their hack.
Another question is how would i ever know if WP Armour filtered out a real customer? this has always been a concern with any anti-spam software, not just WP armours.
Sorry about the rapid consecutive messages, and thank you for your insight.
-
This reply was modified 4 years, 7 months ago by
schmekis.
-
This reply was modified 4 years, 7 months ago by
schmekis.
-
This reply was modified 4 years, 7 months ago by
schmekis.
@johnmecham ,
Our honeypot uses javascript fields. And they are auto filled by javascript for real users. But the spam bots doesn’t uses javascript and can’t see and fill those fields. This is how we filter spam.
Regarding submission, in our Extended version there is option to see what spam bots are trying to submit.
Thanks