Sorry, I missed your earlier question. Your guess is correct about first_name. In fact, I think it would be fairly easy to use a snippet to select from a series of attractive names for the field and change it constantly.
I dislike testing the user also and wouldn't do it unless I was desperate and then I would make users log in before entering a post and only give the test to newly registered users.
You could certainly use JS. I use it in SPForm to require use of the mouse or keyboard and enforce the time window. With the time window, the hidden fields, and the mouse/keyboard requirement, I've been spam-free for over a year, but then it's a contact form, so there's no opportunity for posting links.
Thanks BobRay. Tell me, can you explain the benefit to us of dynamically changing the Honey Pot field's name, or even changing it manually every so often)? Does that cause the spam bot to fail (whether it's using the form each time or using previous information) until it figures out where the Honey Pot field is.
??? Sam
Does that cause the spam bot to fail (whether it's using the form each time or using previous information)
That would be the hope. If the bot keeps a record of which fields shouldn't be filled in, changing the name of the field might confuse it. OTOH, if it's smart enough to just keep a list of fields that *should* be filled in, changing the name might not help. In theory, you could continually change the names of all the input fields in the form, though it would take some effort.
