Why use CAPTCHA on the site?

Due to the enormous increase in SPAM bots visiting the site, I've been forced to add CAPTCHAs to the sign-up page. On some days recently, we've had as many as 150 bogus signups. The bots can't get in because they never reply to the emails sent out but they bog down the system with useless database entries and queries.

In addition, there have been actual humans signing up for real accounts then using bots to populate bogus spam comments. One enterprising fool a few weeks ago left sixty pieces of spam in just a few minutes before I found them and suspended their account and locked them out by the firewall. So much of this is done from probably remote accounts in Moldova and the Ukraine that I have actually locked those countries out of accessing BigCloset via the firewall. People who live there who have accounts through ISPs based in other countries can still access BC but not if their ISP has a Moldovan IP address or 90% of the Ukrainian ISPs. Large groups of Russian, Belarus, Latvian, Estonian and Chinese ISPs have also been locked out. One Italian ISP has been firewalled, too.

But because of human involvement with getting accounts, I've also added a CAPTCHA to the comment system. For people who aren't trying to flood the site with bot generated comment spam, you should see the CAPTCHA only once, or possibly once per machine/ISP/IP address you use. That is, if you have a dynamic IP address or get here through WiFi, you may occasionally be asked to fill out a CAPTCHA to leave a comment.

These are the simplest, easiest to use CAPTCHAs for Drupal I can find, just hard enough to cause 99% of bots to fail. To anyone who is visually impaired enough to make this system difficult, I apologize and I am searching for audio CAPTCHAs and/or logic CAPTCHAs that are sufficiently secure to replace this current system. The current logic CAPTCHA offered by Drupal is not secure.

Hugs,
Erin