Spam Prevention Techniques?

As a bit of a follow-up. I re-installed the Spam module (the latest development version - as that seemed to kill the errors I was getting previously from the "stable" release) and haven't noticed even a remote improvement in the spam the site gets (between 5-20 successful spam link submissions a day).

Ultimately, I believe the most effective solution in solving this would be to have:

1. An adaptable and intelligent spam module that uses stories/links reported as spam to make an educated guess on whether something being submitted in spam. If it is, it puts it in an "unpublished" queue for moderator review/deletion. Upon review, if the suspect spam is deemed "spam" and deleted, the module would then use that information as further knowledge to better guess spam the next time. I *thought* this is what the spam module claims to do, but if so, I've not noticed a decrease in the amount of spam.

Ultimately, this method would also allow an admin to define a role for some users (based on karma, perhaps?) to see a "report as spam" link beside each article. The article, if reported, would then be put in the queue for review by an admin.

2. User Moderation: I'm trying to figure out how to return the vote count for display in the template. With this I can set a simple "if" statement in the node-drigg.tpl.php file to only display the article if the article has more than say -2 or -3 votes. Of course this method leaves stories open to attack from regular users and legitimate stories may be hidden. But with an active Drigg site, that should be negligible.

-Ryan
__________________________________
Hao Hao Report: All the best English-language news and blog stories about China.