Why is honeypot field your first stop when I just said that it was too unreliable? (Especially as my site was not even worth spamming).
JS verification can be bypassed completely by bots, so what do you have in mind? My question/answer solution is better than a simple honeypot field, so didn't you like that idea? On Saturday, 15 June 2013 20:29:42 UTC+1, Niphlod wrote: > > honeypot is the first stop, javascript evaluation is the second.... > another step that is almost impossible to break is to require registration > for everything (on google and facebook), but that can scare off users > (although probably not users of web2pyslices.com) > > On Saturday, June 15, 2013 9:10:51 PM UTC+2, villas wrote: >> >> I started to get bot spam. So I introduced the non-displayed honeypot >> field that the bots would complete. This worked great at first, but the >> bots seemed to learn the trick and started leaving it empty. So the spam >> returned. >> >> After a little research, I decided that I liked those questions that >> humans can easily answer, but bots cannot. >> >> Only problem with the questions is that there can be several 'right' >> answers eg. zero, 0, none, nil, nothing -- might all be acceptable >> answers. Also the questions needed to be selected at random. So my >> solution needed to be not only simple but flexible too. >> >> Anyhow I wrote that code and I have not been troubled by spam since. If >> anyone is interested in this idea I will extract the code from my app and >> post it. >> >> Regards, D >> >> >> >> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
