Throttling Comment Spammers

Distler has a plugin for comment throttling which may be useful if you use MT. Got link from Matt. Thought to share this after Frank J. got hit by porn spam. Then there’s the Moonbat(tm) spam, must control that.

If I got spammed, would just turn on comment moderation and all would have to be approved. It would be nice thou for it to kick in if a certain if one got flooded. I bet Matt could do it too.

From my use of WP and my very brief use of MT (guest blogged once, k), WP is far superior in it’s interface. There are a couple things in earlier builds, one from b2 also, that I would like to see put back in. When it’s all done, expect WP to totally smoke MT. For one thing, it doesn’t have that dreadful page rebuild problem. Only thing that slows it down is if one is using Blogrolling and Blogrolling is down. WP’s link function is better IMHO than Blogrolling. I wouldn’t have paid to upgrade Blogrolling had I known what was in store from WP. See, I was using b2 at the time, flimsy excuse I know.

This entry was posted in blogosphere, web design WP. Bookmark the permalink.

3 Responses to Throttling Comment Spammers

  1. It’s worth pointing out that Matt’s blog, hosted on a burly dual-processor Xeon was (for a few hours, anyway) knocked out of commission by the trackback flood. My puny 466 MHz Macintosh G4 (the *bottom of the line* model when it was purchased 3 years ago) kept right on humming when they flooded my blog. I didn’t even know I was under attack until I checked the server logs.

    As to user interface, it took 3 mouse-clicks to remove the 43 trackbacks that made it through my throttle (out of some 500 attempted).

    I spent *much* more time assembling the data for the abuse report.

  2. mog says:

    Love those Macintoshes especially mine. I haven’t needed to either throttle comments or close comments yet. I did note when I upgraded, comment moderation was the default which I changed. People that have commented here have been, with only one rare exception, civil, nice, spiffy and all that and most definitely blogrollable.

  3. Well, like I said, I think throttling is a good precaution which should be in anyone’s weblog setup.

    Even WP, which is a pretty robust implementation, running on a burly server can get hammered by a flood. My lowly machine didn’t even hiccup, but only because I had throttling in place.

    Hopefully, you will *never* hit your throttle limit. But it’s nice to know it’s there…

Comments are closed.