Hi everyone, my name is Jay Allen and I am the Product Manager for Movable Type. I'm writing today to address—what else?—comment spam.
This is an issue that, as many of you know, I have spent several thousand waking hours working on since its first appearance back in the fall of 2003, both as the author of MT-Blacklist and as the maintainer of the Comment Spam Clearinghouse. This is an issue which Six Apart takes very seriously, as evidenced not only in the improvements in Movable Type v3.x but also, in some part, by my hiring to this position.
Over the last month, we have been devoting a great deal of resources to solving the comment spam problem once and for all and making it a non-issue, not just for us in the Movable Type/TypePad world, but also for all weblogs regardless of publishing tool. Our preference is towards solutions that scale to the entire weblog medium, not those which merely move the burden from one site to another, from one tool to another, or from spammers to users.
Identifying the Problem
Recently, however, there have been a number of reports about the escalating effect of comment spam on Movable Type installations, especially evident in shared hosting environments. At first, we assumed that these problems were caused mainly on legacy systems (i.e. MT 2.x) running without the benefit of the modern anti-spam measures (e.g. TypeKey, comment moderation, MT-Blacklist v2.x, etc.) built to protect Movable Type installations. After further analysis and load testing, we've actually found that this is not the case.