Submitted by Bryan on

For our Wordpress 2.0 sites, we have been using the Akismet plugin to fight off the spam thrown at us through our comment pages. We've been impressed with the results with over 550 spam filled comments blocked since early 2006 and only two spam comments slipping by Akismet's filters. With these impressive results, we have been hoping to see an Akismet Drupal module also developed. Now both Drupal and phpBB users have access to an Akismet module for their CMS.


Markus Petrux from phpmix.org announced at Drupal.org:

After several days of work and tests at phpMiX.org, I'm proud to announce the immediate availability of about 2000 lines of code compiled into Akismet module v1.0.0 for Drupal 4.7.

You are encouraged to visit the Akismet site to learn more about it. In just a few words, when new content is submitted to your site, the akismet module sends a real time request to Akismet where hundreds of tests are applied to get a thumbs up or thumbs down kind of response. It may finally that tell us if the content is spam or not. If it isn't, the content is published, if it is, then it is placed on the moderation queue. Moderators may opt-in to receive e-mail notifications for all content, just content needing approval or nothing at all. The module is fully customizable, almost everything is optional. It also keeps track of a counter that you can use to show your visitors how many spam has been caught by Akismet in your site.

Also announced, was a module for the phpBB forum software. You can visit either Akismet or phpBB for more information. If you check out phpBB, you'll likely get a kick when you see that they are calling the mod the "Akismet Spam Butcher". Hopefully both Drupal and phpBB users will find the Akismet modules as useful as Wordpress users have found the plugin for Wordpress to be at their sites.

There is one caveat to using the Akismet modules though. You'll need a WordPress.com API key that is available, as far as I know, only by opening an account at Wordpress.com . I'm not really sure why the API key is only available at Wordpress.com and not Akismet's own site, but that's what they've chosen to do. For non-Wordpress users, Wordpress.org is the site you can download the actual open source software and Wordpress.com is a service that provides users a free Wordpress blogging account.

 

CMS Topics: 

Comments

Akismet module v1.1.0 for Drupal 4.7

Markus's picture
Hi! Just wanted to mention that I have just released version 1.1.0 of the Akismet module for Drupal 4.7. It's been just 8 days from 1.0.0, but it was then when I realized that the moderator queue had to be improved to allow operations against multiple items. It also includes an experimental set of options to prevent DoS situations caused by certain spambots. That's it, happy blogging!

Once I wrote

James's picture
Once I wrote on your blog about spam on forums and blogs. It's very easy to get rid of without any scripts. Just hack that can check or send you comments to moderate with more than one link.

Wordpress and Akismet Conspiracy

Eric Gawaterr's picture

I was excited when I installed my blog at my host and it came with a few plugins already installed. WP-Cache and Akismet. I was excited about Akismet because it seemed like it would do all the work for me catching all the spam comments. Mainly because my last blog was bombared daily and the useless Captcha code seemed to make it worse. Then I had to get a Wordpress API key. I wonder why. Hmm. Smells a little fishy to me. Wordpress.com is spying on us just like Myspace is.

Eric

Don't delete spam, prevent it (as much as it possible)

Sigurd Magnusson, SilverStripe's picture

Instead of deleting the spam, tell the submitter that you think the post is spam. If you're a human then you will then tweak the content and resubmit. If you use AJAX to check for spam, then the user experience is still good. This means only a small fraction of people (the false positives) ever have to bother with an interactive spam prevention measure. Sure, it allows the occasional undiagnosed spam in (and I do know this happens), but it is occasional, as you said yourself. (And my opinion is that the occasional spam let in is better than the pain of a capcha, or moderation)

Using AJAX to inform the user their post is spam is what we do with our ajax blog system (direct link to demo).

To catch the last robot

orican@drupal.org's picture

To catch the last robot bypassing your filter and even prevent paid human beeings from hacking spam into your premium site's comment sections (who knows), you should install the spam module. It contains a links treshold filter that will fit another 98% of the comments coming through. The rest will be catched by spam module's learning filter.

Note the spam module makes use of a comment's links section. So this should be outputted in your comment template file, at least for comment administrators. I myself commented this out a while ago and it took me months to figure out how to mark a comment as spam...

Another idea is to change the name of the captcha field from "edit[captcha_response]" to - say - "edit[i_love_squirrels]". I didn't test this, though.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| don't buy World of Warcraft Gold, make'em. |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -