You might notice SpamFilter already has some code for SpamAssassin
type scoring; but this was never really finished.
I only have really two requirements for SF: it works and it does not
intrude to the editing process. The techniques we currently use are
extremely effective: 98% of all edits to jspwiki.org are stopped with
the current incarnation, and there are very few false positives.
What I'm not very happy about currently is spambot registration
recognition. We need to hook SpamFilter somehow up to our
registration... Which suggests that SpamFilter should really become a
separate component (a WikiDaemon?), and SpamFilter itself would just
be a thin layer which uses this component.
/Janne
On Sep 18, 2009, at 15:13 , Andrew Jaquith wrote:
Good points. I do think it makes sense to have a reCaptcha option
among others that might arise.
On a side note, I'm fooling around with SpamFilter to make it a lot
more extensible. I have this idea about stackable "Inspector"
objects that extract the current (rather complex) logic into
separate implementions, but which collaborate on the outcome. The
driver for this was the need to have better integration with the
view layer and additional captcha systems.
I'll run the design by you when it firms up, but my initial
experiments look very promising. I think you'll like it a lot.
Andrew
On Sep 16, 2009, at 17:21, Janne Jalkanen <[email protected]>
wrote:
Google is well known for their embrace and extinguish -tactic. It
would be unlikely that ReCaptcha will get any new development.
The captcha system we have is designed to be pluggable, so it
should be possible to add other systems as well. More the merrier;
then we won't be subject to corporate whims...
/Janne
On Sep 16, 2009, at 23:31 , Andrew Jaquith wrote:
Any thoughts on ReCaptcha? Google just bought them. I thought this
might be a nice addition to what we offer now (Asirra) -- maybe
even a
replacement for it.
Andrew
