Moderatie

On the 1st of september, kids go back to school here in Belgium. And so, with a week to go, I was able to get a new release out. I intended it to be a bugfix release with version number 0.5.3, but I got a bit carried away and some feature creep happened. So I decided to give it version number 0.6.0.

Here’s the changelog:

• fixed: html is preserved in a comment when the visitor is confronted with the captcha
• fixed: handling of session id’s in show_captcha() en check_captcha() follows the API flow better.
• fixed: broken bulk moderation of comments is now fixed
• fixed: the IP adress was incorrectly passed to the ‘mollom.checkCaptcha’ call
• fixed: the session_id is now passed correctly to _save_session() after the captcha is checked.
• improved: more verbose status messages report when using the Mollom Manage module
• improved: cleaned up some deprecated functions
• improved: handling of Mollom feedback in _mollom_send_feedback() function
• added: approve and unapprove options in the Mollom Manage module
• added: link to the originating post in the Mollom Manage module
• added: if a comment had to pass a CAPTCHA, it will be indicated in the Mollom Manage module
• added: plugin has it’s own HTTP USER AGENT string which will be send with XML RPC calls to the API
• added: detailed statistics. You can find these under Plugins > Mollom

My personal favourite are the new statistics. I like shiny bar graphs. Dries and Benjamin let me use the flash object to generate statistics based on the data of their Mollom services. But I decided to keep some statistics on the ‘client’ i.e. your site’s side.

It took me the better part of June to prepare a new version of Mollom. But today I released version 0.5.0. You can download the package here.

So, a lot has changed since version 0.4.0…

• I rewrote the SQL after this suggestion on Pressed Words. Mollom now uses it’s own table to store all it’s data instead of fumbling with the WordPress data model.
• I fixed the incompatibility issues with WordPress OpenID plugin.
• Improved the error handling.
• Status messages are now a lot more verbose
• Added the mollom_moderate_comment($comment_id) tag for use in templates and themes. This allows direct moderation of a comment without first having to go to the dashboard.
• … a lot more!

So download, go forth and protect your blog against those vile spammers through Mollom!

Hum. The plugin in WordPress doesn’t support trackback checking yet. No big deal? Well, I have 24 spams in my moderation queue, the majority of them are trackback spam.

So… yet another feature to implement. Just wondering how the flow of operations should look like. Moreover: how/where do I implement a CAPTCHA? Is it necessary to do this implement? Given the 99.8% accuracy Mollom claims, is it a bad thing if a trackback would be identified as a false positive and the CAPTCHA step is skipped altogether? One can retrieve the false positive through the moderation queue altogheter, no?

Yesterday, I made a last codingscram and implemented the entire feedback/moderationqueue in the dashboard. It works acceptable enough to put out a very rough betaversion out to the testers. Which I did yesterday-evening. I’m very curious about their feedback. I’ve already listed some points that will need improvement.

If you’d like to participate in testing please mail me!! Remember Eric Raymond’s famous aphorism: give enough eyeballs, all bugs are shallow!

A little progress update on my Mollom for WordPress plugin. The past ten days some unexpected real life events kept me back from programming. No worry, I hope to do some hacking in the upcoming long weekend.

So, where do I stand? Well, I just need to implement the last necessary feature: the moderation queue and feedback module that catches the last 0.1% of (unsure/spammy) messages that Mollom can’t process itself. Shouldn’t be much more than an afternoon’s work though.

Zo. We zijn een half dagje verder. Dit is de tussenstand: 0 spammers door de mazen van het net gegelipt. 7 spams in de moderation queue waarvan er 3 door jullie werden achtergelaten. 1 spam (Houbi) per ongeluk in de moderation queue blijven hangen. Niettegenstaande de mens legit is.

Kijk, voorlopig laat ik alles daar even hangen. Ik moet nog een feedback module in mijn plugin hangen zodat ik de Mollom servers kan terugsturen waarom iets wel of niet spam/profanity/unwanted/… is.