<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Queue on Netsensei</title>
    <link>https://www.netsensei.be/tags/queue/</link>
    <description>Recent content in Queue on Netsensei</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>nl-NL</language>
    <managingEditor>matthias@netsensei.nl (Matthias Vandermaesen)</managingEditor>
    <webMaster>matthias@netsensei.nl (Matthias Vandermaesen)</webMaster>
    <lastBuildDate>Fri, 23 May 2008 17:00:48 +0000</lastBuildDate><atom:link href="https://www.netsensei.be/tags/queue/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>To moderate… or not?</title>
      <link>https://www.netsensei.be/2008/05/23/to-moderate-or-not/</link>
      <pubDate>Fri, 23 May 2008 17:00:48 +0000</pubDate>
      <author>matthias@netsensei.nl (Matthias Vandermaesen)</author>
      <guid>https://www.netsensei.be/2008/05/23/to-moderate-or-not/</guid>
      <description>&lt;p&gt;Today, I had an e-mail discussion with Dries and Benjamin over the use of a
moderation queue within the context Mollom provides. I have on implemented in my
plugin. The idea is that ‘unsure’ comments that don’t get
through the CAPTCHA test, land in a moderation queue… sort of.&lt;/p&gt;
&lt;p&gt;Mollom was actually designed to get rid of the queue. Checking if a commenter is
human or a spambot happens through the CAPTCHA test. Early on in the process of
posting a comment. That makes a queue where an administrator has to do the check
after the facts quite unnecessary.&lt;/p&gt;
&lt;p&gt;The problem is that the way I designed the plugin forced me use a moderation
queue altogether. ‘Unsure’ labelled comments happen to land in the
database, before the CAPTCHA check. Two months ago, that seemed the logical way
out to me. Dries gave me some more insight in the workings of the Drupal module
and was able to convince me to seperate the CAPTCHA check from the moderation
queue. (I am not nearly into Drupal as I am into the workings of WordPress!)&lt;/p&gt;
&lt;p&gt;So. It’s a bit back to the drawingboard for me as this means some parts of
the plugin need to be reviewed.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Mollom for WordPress III</title>
      <link>https://www.netsensei.be/2008/05/09/mollom-for-wordpress-iii/</link>
      <pubDate>Fri, 09 May 2008 10:47:08 +0000</pubDate>
      <author>matthias@netsensei.nl (Matthias Vandermaesen)</author>
      <guid>https://www.netsensei.be/2008/05/09/mollom-for-wordpress-iii/</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;More important: it’s testing time! I’m in need of people who want to
put the plugin to the test and who want to send me some feedback. Areas that
need testing are: effectiveness of the spamfilter, usability (easy install, easy
use), code (did I write it properly? What could/should be optimized?)&lt;/p&gt;
&lt;p&gt;You can drop me a line on my mailadres &lt;em&gt;matthias apetail netsensei dot nl&lt;/em&gt; if
you want to take part, and I’ll send you the plugin. Important note: you
need a stand alone installation of WordPress. The plugin doesn’t work with
wordpress.com hosted blogs.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>