- Captcha
- 29.3.2009
Bots started posting spam here this morning, so I implemented my own captcha based on FIGlet. I may eventually switch to reCAPTCHA, but it didn't work to my liking last time I implemented it.
FIGlet offers several benefits over traditional captchas at this time. First, FIGlet doesn't have to do any CPU intensive image generation. FIGlet is also a much simpler program in general, which makes it more malleable to the developer as compared to something such as PIL. And most important (at least for now), every capcha bot that I have seen is based on OCR. Because FIGlet captchas output ASCII rather than an image, the bot would first have to take a snapshot of the website and crop out the relevant portion. This would end up being quite a CPU intensive process for the malware. Thus, ASCII captchas are usually overlooked in search of an easier target.

Also - 0 and O look very similar (probably some others too), so just hit back and swap them out if you encounter trouble.
Reply
I actually just removed 0 and O from the pool of selections, so don't worry about this anymore :)
Reply
I rike it. If you're basically rolling your own, why not implement something like Akismet or Mollom into Django to avoid the captcha altogether?
Reply
meh, you know me - I like doing stuff myself. It took me forever before I trusted a free email provider to be stable enough not to break.
Also, I'll probably remove the captchas for registered users (when I get around to it).
Reply
Cool, cool. IMO that's the inherent problem with end-all-be-all CMS's that nobody talks about...coders don't code. I've been using Drupal for like 2 months and have probably only spent a couple hours with PHP. At least with Django coders can code.
Reply