Rails Wiki spam problem with solution

rubyonrails-talk
1

Okay, enough with spam already.

I wanted to clone Rails Wiki, but it doesn't have this "export" feature.

Here's my plan: 1. Get an export of current Rails Wiki (with all revisions, so we can rollback). 2. Install MediaWiki 3. (the hardest part) convert all Rails Wiki pages to MediaWiki 4. If necessary, redirect/replace wiki.rubyonrails.* to the new site/server/whatever

I'll do all of the above steps if I can get access to Rails Wiki's current i2's database.

wget/spider-ing the current wiki isn't really a solution. But I'll do that if nobody helps me. But I hope somebody does.

Please, to the maintainer of the wiki, send me the wiki database or give me some shell access to that server. Then rest assured, wait several days or weeks. :slight_smile:

Thank you.

2

You're kidding right?

What about the fact that Rails wiki is in Rails? I don't see any way how the community would allow a php wiki.

3

How does this solve the spam problem?

Chris

4

Hrm, interesting thought. I'm all for a better solution, whether using rails or not. I think you should use the best tool for the job. As it is right now, the wiki is pretty much unusable.

5

It sounds like you should check out Jim Weirich's RuseWiki http://wikis.onestepback.org/Ruse

Not "public" yet, but it's already being used.

-Rob

Rob Biedenharn http://agileconsultingllc.com Rob@AgileConsultingLLC.com

6

Why don't you email some of the wiki folks, and attempt to work w/i their process instead of starting your own? Besides, if you switch wiki engines to something that doesn't support textile, noone will want to use it. The wiki syntax that stuff like wikipedia uses is horrible.

Just search this list for "wiki spam" and I'm sure you'll find the folks who are working on things right now...

- Rob

7

Alright... Alright... I'm stepping back.

Was just trying to help...

Thanks for all the suggestions. :slight_smile:

8

What about hooking in the Akismet filter into the current Wiki? Mephisto uses it and it has been very effective for me at blocking spam.

Michael www.mslater.com

9

What about hooking in the Akismet filter into the current Wiki? Mephisto uses it and it has been very effective for me at blocking spam.

That's a great idea.

Although it requires some code.

And (unfortunately) it seems not everybody wants to code for the Rails wiki (or even manage). (especially unpaid?)

Something relatively "trivial" that doesn't require heavy implementation of login system or anything is Captcha.

Using a Captcha library or the recently online captchator, I figured out this would be one of the quickest, most effective ways as an initial effort.

The real problem is... who's the maintainer of the Rails wiki? It doesn't seem he's here. Even if he's here, where is he?

10

> > What about hooking in the Akismet filter into the current Wiki? > Mephisto uses it and it has been very effective for me at blocking > spam.

That's a great idea.

Although it requires some code.

And (unfortunately) it seems not everybody wants to code for the Rails wiki (or even manage). (especially unpaid?)

Something relatively "trivial" that doesn't require heavy implementation of login system or anything is Captcha.

Using a Captcha library or the recently online captchator, I figured out this would be one of the quickest, most effective ways as an initial effort.

The real problem is... who's the maintainer of the Rails wiki? It doesn't seem he's here. Even if he's here, where is he?

By the way, by I'm saying the above paragraphs... I'm also volunteering myself to "fix" the Rails wiki had I had a (temporary) shell account to the box.