My sites that allow comments are getting hammered by comment spam. None of the CAPTCHA or Mollom modules are effective, far too much breaks through. I'm not finding that the Mollom module is terribly adept at filtering. The Spam module would appear to be my huckleberry but I'm reluctant to install a -dev release on live sites.

With considerable anticipation I respectfully ask if there is an ETA for a 6.x Alpha release of this module?

Regards,

Miles

Comments

shunting’s picture

shunting commented

Let me ask this question in another way. Is anyone out there using this on a live site? Or do I have to be the first?

jeremy’s picture

jeremy commented
Status: Active » Fixed

I'm using the 6. version of the module on KernelTrap.org as of a few days ago. It's got some bugs which I've not had time to track down/fix yet, but it's also catching quite a bit of spam at the same time.

As for an ETA for an official release, nope, there is none. But now that I'm using it on a live website it's likely to get much more attention from me.

milesgillham’s picture

milesgillham commented

Give me CVS access and I'll happily contribute some effort. :-) I've written Bayesian modules previously in Perl so should be able to pick it up quickly enough.

Cheers,

Miles

gnassar’s picture

gnassar commented

I have also been using it for a live site. If you look through the issue queue, you'll see that the current 6.x-1.x is effectively in a freeze to look for bugs and is the current release candidate for 6.x-1.0. I had actually slated to make the release at the end of this month if there were no bugs.

Jeremy, I wasn't aware of any bugs still remaining. Could you throw the issues you've found in the queue?

franz-m’s picture

franz-m commented

> ... Or do I have to be the first?

No, you haven't ;-)

I do use the current code, and I am glad about it. No spam has escaped as far as I can see it; I am not really certain whether all wanted comments have been processed in order, but I did not have the time to do all checks, So: all problems are my own ...

naught101’s picture

naught101 commented

Agree, this is stable. There are no bugs that cause problems. There are a few minor ones that make features not work. I'm using this on at least one production site, with no problems. It's definitely safe.

jeremy’s picture

jeremy commented

@milesgillham: start by submitting some patches to the queue... :)

@gnassar: yes, will do so right now. I've not had time to review them much however, hence my details will be limited.

milesgillham’s picture

milesgillham commented

Jeremy, I hate it when you call my bluff. Next you'll be saying I should be spending my efforts more productively on new releases to ad_views. :-)

Alrighty, I'll install the -dev branch and give it a whirl. Will certainly submit patches if anything stands out. Otherwise it's starting to sound much more stable than I had first thought.

Just to pin down to a fixed target, is it worth punching out an alpha release?

Cheers,

Miles

gnassar’s picture

gnassar commented

Well, I think the consensus was that 6.0 has been out for so long that we need a "real" release as soon as is practical. Hence the early code freeze and fairly long bug-fix status. Hopefully we can knock out the new bugs Jeremy identified fairly quickly and still make the end-of-month goal! I think it's doable.

jeremy’s picture

jeremy commented

@gnassar: it's certainly okay to put out an alpha or even beta release with known bugs, and that may prove helpful for encouraging more people to test the code and track down bugs. The module is certainly usable in the current state, and since you're no longer accepting new features I'd recommend skipping alpha and going straight to beta1 as soon as you're ready.

gnassar’s picture

gnassar commented

Yeah, that's the plan -- if we don't hit all the clearly defined bugs, which for kicks we'll call the "blockers," I'm just going to put it out as a beta release.

Four days to go! Fingers crossed!

jeremy’s picture

jeremy commented

We've rolled the first release candidate, meaning that the code is considered to be quite stable. Please download it, install it, and report your experiences! If all goes well, we'll be releasing a 1.0 stable next week and move onto further development.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.