Spamblock Bayes: No Spam without Akismet

[onli]

The spamblock_bayes-plugin is intended to serve as an alternative to akismet on classifying comments as spam. It sets up a local database with spam and valid comments (ham) and compares every new comment with that data.

To fill that database it can import the log-database of the normal spamblock-plugin and it fetches comments from serendipitys database. To adjust the ratings manually, e.g. if a new type of spam is not recognized at first, a new entry is added to the admin-area (based upon the comment-view but with "spam" and "valid" buttons).

The rating-logic is based upon b8, authors of the plugin are kleinerChemiker and myself.

Let me know if it works for you or if you found an error.

[yellowled]

Let me know if it works for you or if you found an error.

I already told you via Jabber

Just for the record and the public, I have been testing this for a few days now, and it looks very promising. In fact, I haven't felt that calm about comment and trackback spam in quite some time.

The plugin might have a few quirks and still could use some work, but that's probably because it's author's haven't had much feedback since not that many people actually use it yet.

YL

[onli]

Yes, feedback is very valuable. The bug in the admin-frontend is typical for developer-blindness. Thanks again

[Don Chambers]

The methods I have in place using akismet and whatever else seems to work fine for me... what is different about this plugin, or what would it add if already using akismet?

[kleinerChemiker]

It's a bayes filter, which mean it can learn from your spam for better filtering.

[onli]

Maybe a little more detailled: If Akismet works just fine for you, an additional spamplugin won't give you anything. But as the bayes-plugin learns only by the comments from your blog, it should perfectly fit to the spam and the comments which arrive at your blog, whereas akismet is influenced by many comments on many blogs (which has it pros and cons).

Akismet is not perfect. I was told that comments from myself on wordpress-blogs were marked as spam by it (something which of course could also happen with the bayes-plugin, but then one could react easily). And of course it's an external service, so the usual question arise - what if it goes down? Is it legal to submit the comments to them (in germany was a broad discussion about that without a clear conclusion)? So a local solution for spam has its benefits

Anyway, I made a bugfix-release, there was a typo in an english language-file and the formular in the frontend lead to the comment-section.
sincerely

[yellowled]

Reminder: please insert duplicate previous/next buttons at the bottom of the comments list. Thanks!

YL

[onli]

Done (and a cleanup of the html)

[yellowled]

Yup, works. Thanks

I keep forgetting: Should this thing be logging to the specified logfile every time I classify something as spam? 'cause it doesn't seem to do that.

YL

[onli]

It doesn't and it shouldn't log the classification. I think it's unnecessary: The "Done" in the frontend shouldn't appear if an error occurs. If a comment gets caught as spam, the message of moderation or rejection will be logged.

Garvin: You think that plugin may be added to spartacus?

[garvinhicking]

Hi Online!

Sure , go ahead, feel free to upload it to spartacus!

Regards,
Garvin

[onli]

Instead of creating an own menu-entry, this version adds the controls to the comment-page. Fetching the comments for learning is improved, it fetches them directly from the database instead of reading them from the commentpage - so less modifications to the comments get included.

I'll wait a few days before updating spartacus so anyone can give feedback.