Janis,

I did consider the fake field option. It’s been going around for a little while and when I have used it, it has worked well.

In this instance though I wanted to see how things would go with just this one interception technique on its own.

At the moment it is pretty easy to get around if someone really wanted to but I working on that.

Is your experiment by any chance similar to what I did recently?

You might also be interested in the Comment Spam Trap plugin (it uses preprocess_comment).

P.S.
Okay, I looked at the page source, I can see what you’re doing ;)

I had a quick look at Bad Behaviour and it looked like a Javascript based validation solution. I didn’t have much time to look in depth unfortunately.

That is certainly one way to add additional protection.

I think Spam Karma rolls the comments back as well.

I have found that there is a pre-process filter hook: preprocess_comment

This lets the comment data be filtered before it is added to the database.

Unfortunately it is still a little too late to alter the post variables.

SpamKarma2 is also quite good, and while it does process everything, it gives you numbers. :) And inserts a foot saying how many it snagged.

I’m also currently trying out a trifecta of smaller spam-stoppers on a medium-sized WPMU install.

dealing with spams waste a lot of time for me too.

I haven’t looked at Bad Behaviour, but I will. Thanks Andrea.

Doesn’t Bad Behaviour stop most spam before it gets processed? that’s how I thought it worked. Haven’t tried it much; just going by what a few users have said.