[TheMilkCarton]

This can return a false positive if somebody messes up their registration info, gets an error message, clicks back, and then quickly changes whatever was wrong and hits Submit again.

However, installing the AjaxReg hack has helped this infinitely, since it uses AJAX to check every field. I do have one field though that requires A-Z input, and I'm thinking about removing it from the registration page so that this won't happen EVER.

Is there any way to keep the time from recounting itself if a user were to click back upon getting an error message?

What about putting is_bot_time1 on the Verify Age page instead? If a user clicks back to fix an error, the time won't be recounted anymore. The only problem I can see is if a bot could keep clicking back and then they'd go past the time limit, but I'm not sure how bots handle an error message?

I was also thinking how does this work with "Time Zone Registration Prevention" hack? I thought about changing the execution order so this hack goes first..

--------------------------

Well, I changed the execution order of that hack to go after this one.. but I can't really test it out since I'm not a bot..

I do want to say that I think this mod is great. In the past 11 hours it has blocked 30 registrations, although CAPTCHA would have stopped all of these. HOWEVER, for the sake of testing this I've disabled CAPTCHA on the registration page! I have a few other measures in place though, so I really doubt any bots are going to get through even with CAPTCHA disabled. If all goes well over the next few days I may keep CAPTCHA disabled entirely.. I think not having CAPTCHA makes the registration page a little less daunting, especially with the settings I had for it. (I could hardly ever read the letters myself!).

I was thinking about possible expansions to this mod... How hard would it be to add a query that updates the "Banned Email Addresses" field with the domain of the spammer when they've been denied registration? It would of course check to make sure it's not already listed, it could be turned on/off, and also have a whitelist of emails NEVER to ban, like @gmail.com or @yahoo.co.uk. I've been brainstorming and it doesn't seem that hard to do.. I think adding a query right to the register_addmember_process plugin could work. The value for the email is passed through that plugin, and that's all we'd need to write an UPDATE query to add the email.

------

Haha, in the time it took me to edit this it blocked another spammer.