A common question I hear about sites like weblogs.asp.net and other large communities we run (as well as Community Server in general) is: Why don't you have support for CAPTCHA?
The
short answer is: while CAPTCHA isn't a feature included in Community
Server there are several different CAPTCHA implementations that people
have developed as add-ons for Community Server. You can download a
CAPTCHA add-on for Community Server from the www.communityserver.org
file gallery right now.
CAPTCHA,
which stands for (C)ompletely (A)utomated (P)ublic (T)uring test to
tell (C)omputers and (H)umans (A)part, works well for small sites but
larger 'community' sites where there are multiple SPAM targets CAPTCHA
only provides a false sense of security - it can be broken fairly
easily and serious spammers are getting more sophisticated all the time.
Just do a Google search on "Break Captcha" and you'll find several example. Below is one of the better write-ups on the topic:
http://www.brains-n-brawn.com/default.aspx?vDir=aicaptcha
This
is the reason we don't have CAPTCHA in Community Server and why you
don't see it on other large communities. Furthermore, CAPTCHA puts the
burden on the person adding the comments - if you've ever lost feedback
because you incorrectly entered the CAPTCHA key sequence you know
exactly what I'm talking about.
There are really only a handful of good solutions for dealing with comment/blog spam:
1. Dynamic Rules Engine - This is what we use for
Community Server. It's a set of rules and scores that validate content
as it comes in that is designed to change/adapt/grow as the spam
changes.
2. Bayesian filters - Really only useful if the comment
spam follows patterns. Unfortunately the type of spam seems to
constantly be changing so a Bayesian filter isn't really a great
solution.
3. SPAM Services - There are companies popping up
that offer web services that implement #1 and can help identify whether
or not something is spam or ham (http://akismet.com is one such example)
Probably one of the funnier CAPTCHA (turing tests) that I've seen though is this one:
http://hotcaptcha.com/
Hopefully
that helps shed some light onto why this site (weblogs.asp.net) doesn't
use CAPTCHA. The bottom line is: it doesn't work as well as many people
are led to believe.