Ferret Wiki Spam - Solutions Anyone?

Hi All,

As some of you may have noticed, the Ferret Wiki has been getting
spammed like crazy. And I haven’t been able to do anything about it
because I just don’t have the time. I’m getting pretty close to
releasing 0.10.0 which has been the major draw on my time for the last
couple of months so I’m going to have some time to look into this
soon. I was wondering if any of you web app experts out there could
give me some advice. The two options I’m considering are sticking with
TRAC and forcing registration to add/edit pages or tickets. The other
option I’m considering is moving bug tracking to RubyForge and using a
different Wiki for the website. Hopefully Ruse will be released soon.

Any thoughts anyone?

Dave

Yes. SpamFilter – The Trac Project.

I never tried it. But I’d be happy to help with more than just the
suggestion if needed.

My vote is to stick with Trac. I haven’t used the SpamFilter plugin,
but it looks promising.

Tom

On 7/11/06, Julio Cesar O. [email protected] wrote:

spammed like crazy. And I haven’t been able to do anything about it

http://rootshell.be/~julioody


Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk


Tom D.

http://atomgiant.com
http://gifthat.com

David B. wrote:

Hi All,

As some of you may have noticed, the Ferret Wiki has been getting
spammed like crazy. And I haven’t been able to do anything about it
because I just don’t have the time. I’m getting pretty close to
releasing 0.10.0

Great, I’m looking forward to it. Did you manage to find the source of
the occasional Index#search segfaults?

which has been the major draw on my time for the last
couple of months so I’m going to have some time to look into this
soon. I was wondering if any of you web app experts out there could
give me some advice. The two options I’m considering are sticking with
TRAC and forcing registration to add/edit pages or tickets. The other
option I’m considering is moving bug tracking to RubyForge and using a
different Wiki for the website. Hopefully Ruse will be released soon.

The trac spam filter plugin works pretty well, a few simple Regexes can
keep out 99% of the spam.

Andreas

On 7/16/06, Andreas S. [email protected] wrote:

David B. wrote:

Hi All,

As some of you may have noticed, the Ferret Wiki has been getting
spammed like crazy. And I haven’t been able to do anything about it
because I just don’t have the time. I’m getting pretty close to
releasing 0.10.0

Great, I’m looking forward to it. Did you manage to find the source of
the occasional Index#search segfaults?

Hi Andreas,

A lot of the core has been rewritten so I haven’t been fixing bugs
like this. It may still be there or there could be new problems. One
of the reasons for doing the rewrite was to make it easier to bind the
Ruby and C code and hence make it easier to find these bugs.

which has been the major draw on my time for the last
couple of months so I’m going to have some time to look into this
soon. I was wondering if any of you web app experts out there could
give me some advice. The two options I’m considering are sticking with
TRAC and forcing registration to add/edit pages or tickets. The other
option I’m considering is moving bug tracking to RubyForge and using a
different Wiki for the website. Hopefully Ruse will be released soon.

The trac spam filter plugin works pretty well, a few simple Regexes can
keep out 99% of the spam.

Thanks, I’ll try it first then.

Cheers,
Dave

On Tue, Jul 11, 2006 at 06:50:40PM -0400, Tom D. wrote:

My vote is to stick with Trac. I haven’t used the SpamFilter plugin,
but it looks promising.

Actually it seems to work pretty well. I installed it into the
acts_as_ferret Trac 2 weeks ago, and we’ve had no spam since then :slight_smile:

Only thing I had to do (besides upgrading trac and installing the
plugin) was to register for an akismet API key.

Jens


webit! Gesellschaft für neue Medien mbH www.webit.de
Dipl.-Wirtschaftsingenieur Jens Krämer [email protected]
Schnorrstraße 76 Tel +49 351 46766 0
D-01069 Dresden Fax +49 351 46766 66