OK, we're taking things to the next level. As spam registrations continue to climb through the roof, I'm adding more utilities to help prevent them from getting through.
Since it takes a human being a wee bit of time to read the registration page and fill in all the blanks, I've added a timer to the page. If a registration is submitted in a very few seconds of the page being served, the user attempting to register is going to be re-directed to an off-site page. In other words, if a robotic script submits a registration attempt much faster than a human being could do it, then the bot will be stopped in its tracks.
As you can see above, there is no way a human could enter a username, an e-mail address, a password, a confirmed password, date of birth, gender, time zone and agree to the forum rules in just 7 seconds. That was clearly a robot that ended up visiting a remote site, after the registration failed.
I've also updated the tool that checks new registration attempts against some spam registration databases.
- If a registration page is submitted too quickly (which has already happened six time in the last 24 minutes), the registration will be blocked.
- If a user attempts to register from an IP address that is already in one of three spam databases, the registration will be blocked.
- If a user attempts to register with an e-mail that is already in one of three spam databases, the registration will be blocked.
- If a user attempts to register with a username that is already in one of three spam databases, the registration will be blocked.
And if a spammer manages to get around all of those measures, they will have EX JUNK to deal with.
To be sure there still is a chance for a human to register, I went through the registration with the above spamtest account. I sailed right through with no problems, at all.
So everything is working, according to plan.
I also updated the Donation Manager, this morning. It was causing some database errors, until I managed to get the .xml file uploaded and the update script ran. Apologies for that issue, but it didn't last terribly long.