Mollom Integration

Direct implementation in the extension code
This is the preferred way to implement Mollom into your extension since it is the most easy and clean way. We tried to create an API that is as simple as possible...
Below you will find the example code to validate the content. The object values of course need to be filled with the actual values of the content you want to validate.

if(class_exists('Moovur'))
{ $obj = new stdclass();
$obj->title = 'The title data, if available';
$obj->text = 'The full text, if available';
$obj->author_name = 'The authors name, if available';
$obj->author_url = 'URL, if available';
$obj->author_email = 'email, if available';
$obj->author_id = 'Joomlas user id, if available';
$obj->author_openid = 'Openid, if available (not used)';
Moovur::checkContent($obj, 'component', 'task');
}

Keith Smith, Aug 24 02:17 pm (CEST):
Yes, according to the developer channel, by design, the audio version DOES NOT match the characters. In other words, you go to a page and get a captcha challenge. You enter your response in the form and submit, and all is well.

If, on the other hand, you play an audio version, you hear the audio for a different captcha. After playing it, you must now enter the response that matches the audio you heard; the response for the image you see with no longer work.

Personally, this seems counterintuitive to me and is not the behavior we see most often on the web, but this was implemented to solve a particular situation where one or the other (image or audio) was being gamed using the other option.

In our developer meetings, we're discussing other ways of handling this.

But for now, yes, what you see (or hear) happening is the "correct" behavior.