Home > Movable Type, Weblogs > Comment Cruft

Comment Cruft

September 29th, 2003

I’ve been slightly annoyed recently by the minor outbreak of inane comments posted by the intellectually inept who wind their way to some years old post via a search engine. Comments of this nature tend to be more annoying than offensive, and sometimes are just pathetic in their lack of basic reading comprehension.
But more disconcerting is the recent outbreak of comment spam. In the last week, I’ve deleted at least a half dozen or more advertisements for penis enlargement pills, viagra, and other questionable products that were posted to comments on random blog entries. Seems like I’m not alone either [1, 2, 3, 4, etc.].
I’ve seen a few methods [1, 2] for stopping this that involve multiple customizations to Movable Type.
For the time being, though, I’ve finally converted the backend of my Movable Type installation to MySQL* and used this close comments script (which you actually have to get here now) to close comments on all posts older than 21 days. Not only does this decrease the annoying crufty responses, but I hope that it will also limit some of the targets for the vulgar spam.
I’m seriously considering changing my policy of having open comments on every new post. I might just open up comments for the posts that I want people’s feedback on. That seems a shame, but I spend enough time filtering spam from my email inboxes. I don’t want to have to do the same with my weblog.
* That also explains why the Last Modified date for every post on this weblog is now 5:53pm yesterday. Argh.

Greg Movable Type, Weblogs

  1. September 29th, 2003 at 20:26 | #1

    This is a helpful rundown, Greg. I hope you won’t feel the need to greatly restrict commenting (also hope I won’t feel that need eventually). Though I don’t like to get into “what is a weblog” fundamentalism, I do think that commenting is one of the primary features that makes blogs such a great medium.

  2. September 30th, 2003 at 12:05 | #2

    I think an minor configuration change to Apache might help as well. I understand the concept, just not the implementation currently, but when I do, I’ll email you the details. I’m not much of a llama wrangler (I’m only slightly more proficient in Perl than Pascal), but a similar change could be done to the cgi script itself.
    Simply put, Comments are the output of calling a cgi script, which can be automated quite easily (for the spammer). All they need is an auto discovery script, which they could cobble together from the MT sources.

  3. October 4th, 2003 at 18:03 | #3

    Friday Feast #61: Unwanted Comments

    I was absolutely horrified when I read Phil Ringnalda’s comment spam alert story last year in which a Las Vegas real estate agent used a script to try to autogenerate comments to every single one of Phil’s entries, including links to the spammer’s real…

  4. October 5th, 2003 at 22:47 | #4

    Comments Back!

    Well, I think I may have found the best solution for this “spamming the comments” stupidity that forced me to suspend the comments feature last week. Now, everytime someone (or something!) leaves a comment, I get an e-mail, which contains the IP of the…

  5. Biff
    November 18th, 2003 at 14:12 | #5

    Testing if this is closed

  6. Alan Levine
    November 18th, 2003 at 14:13 | #6

    Greg,
    I think you need to make this a cron to continually close old comments from cruft (I am testing now at CDB)

  7. November 18th, 2003 at 14:50 | #7

    Cutting Off Goofballs (Maybe SpamRoaches)- Expiring MT Comments

    I’d rather be blogging about something else, but after a raft of stupid “Neat Blog”, “I agree”, “Cool Blog I’ll be back” comments, often from the same IP with faked emails, appearing on very old posts (ones that pop up…

  8. November 22nd, 2004 at 05:56 | #8
Comments are closed.