wiki spam

Hi,

Does anybody have any solutions for some of the spam that's filling up
the rails wiki?

For example the development firms page is being hit with new spam
constantly; just see how many revisions you have to go back before
finding the actual content.

http://wiki.rubyonrails.org/rails/pages/DevelopmentFirms

Another page that looks like it's being hit pretty hard is...

http://wiki.rubyonrails.org/rails/pages/WorkingProfessionallyWithRails

Andrew

Yeah, actually I think there were plans awhile ago to integrate my
logic captcha into the Rails wiki. Guess it never happened though.

http://www.robsanheim.com/brain-buster

I'm using it for the local user group wiki (madisonrails.com), and its
blocking a crazy amount of spam everyday.

- Rob

Actually I thought they were porting the data to a different, more robust app...

Yeah there were planning on going to Ruse
(http://wiki.rubygarden.org/Ruby/page/show/RuseWiki) in the long term,
but I thats been "in progress" for a long time.

- Rob

Actually I thought they were porting the data to a different, more robust app...

I'm not sure what happened with the previous effort, but if someone
else would like to have a go at it, we can definitely provide dumps of
the wiki. PDI.

Michael Koziarski wrote:

Actually I thought they were porting the data to a different, more robust app...

I'm not sure what happened with the previous effort, but if someone
else would like to have a go at it, we can definitely provide dumps of
the wiki. PDI.

The previous effort is still under way. Ruse has been patched to support textile, and the data mapping between the two engines has been defined.

A large part of the problem is that (since Dan P. moved on) there has been nobody actively administering the current wiki.

Koz, if you take a look at the Wiki Cleanup project in BaseCamp you will see who and where we are.

regards

   Justin Forder

I have funds available from the Documentation project to pay for a
dedicated wiki gnome to basically be a librarian, though I think it's
a stretch to be just cleaning spam, once it's in Ruse, someone could
spend a few (paid) hours a day cleaning stuff up, converting code into
API docs as necessary.

What d'y'think? Anyone interested?

Courtenay wrote:

Michael Koziarski wrote:
>
>> Actually I thought they were porting the data to a different, more
>> robust app...
>
> I'm not sure what happened with the previous effort, but if someone
> else would like to have a go at it, we can definitely provide dumps of
> the wiki. PDI.
>
The previous effort is still under way. Ruse has been patched to support
textile, and the data mapping between the two engines has been defined.

A large part of the problem is that (since Dan P. moved on) there has
been nobody actively administering the current wiki.

Koz, if you take a look at the Wiki Cleanup project in BaseCamp you will
see who and where we are.

regards

   Justin Forder

I have funds available from the Documentation project to pay for a
dedicated wiki gnome to basically be a librarian, though I think it's
a stretch to be just cleaning spam, once it's in Ruse, someone could
spend a few (paid) hours a day cleaning stuff up, converting code into
API docs as necessary.

What d'y'think? Anyone interested?

Dan Kohn might be interested. I have no time! (Given the constraints I've been working under, I am still spending more than the time I really have to spare tracking the spam and rolling it back.)

Have to go to work now....

   Justin

I don't know if its worth it with Ruse underway, but I could pretty
easily integrate the logic captcha into the current i2 installation,
at least as a stopgap measure. You can see how the plugin works here:

http://madisonrails.com/wiki/pages/captcha+test+page

I'd just need svn access to the current i2 install. This would at
least stop the bulk of spam until Ruse is installed.

- Rob

Good idea, contributors to the wiki would then only need to learn American history to be able to answer those “logic” questions

Rob Sanheim wrote:

Michael Koziarski wrote:
>
>> Actually I thought they were porting the data to a different, more
>> robust app...
>
> I'm not sure what happened with the previous effort, but if someone
> else would like to have a go at it, we can definitely provide dumps of
> the wiki. PDI.
>
The previous effort is still under way. Ruse has been patched to support
textile, and the data mapping between the two engines has been defined.

A large part of the problem is that (since Dan P. moved on) there has
been nobody actively administering the current wiki.

Koz, if you take a look at the Wiki Cleanup project in BaseCamp you will
see who and where we are.

regards

   Justin Forder

I don't know if its worth it with Ruse underway, but I could pretty
easily integrate the logic captcha into the current i2 installation,
at least as a stopgap measure. You can see how the plugin works here:

http://madisonrails.com/wiki/pages/captcha+test+page

I'd just need svn access to the current i2 install. This would at
least stop the bulk of spam until Ruse is installed.

It definitely is worth it - I am spending an hour a day on average rolling back spam (over 12,500 rollbacks to date). This is preventing me doing more useful things (I can't do any of this in work time, and I'm working long days).

As you know I asked for your plugin to be installed three months ago.

It turns out that the current i2 install was from Dan Peterson's own SVN repository, back in July. We don't have commit access to that repository, and Dan hasn't answered any of my mail since 8th June.

I think the right thing to do in these circumstances is for David to create another branch in the i2 repository, to put the current rails wiki source in that branch, to give you commit access, and to arrange for someone to do redeployment via Capistrano when you are ready.

regards

   Justin Forder

Sounds good to me - I can integrate the plugin and tests that I have
for the Madison rails wiki. That should at least save a good amount
of your time doing rollbacks.

Let me know if/when we get the branch setup.

- Rob

> It turns out that the current i2 install was from Dan Peterson's own SVN
> repository, back in July. We don't have commit access to that
> repository, and Dan hasn't answered any of my mail since 8th June.
>
> I think the right thing to do in these circumstances is for David to
> create another branch in the i2 repository, to put the current rails
> wiki source in that branch, to give you commit access, and to arrange
> for someone to do redeployment via Capistrano when you are ready.
>
> regards
>
> Justin Forder

Sounds good to me - I can integrate the plugin and tests that I have
for the Madison rails wiki. That should at least save a good amount
of your time doing rollbacks.

Let me know if/when we get the branch setup.

I just saw Dan on IRC and he said his repo is here:

http://svn.dpiddy.net/projects/i2_rails/

I suggest you do a svn dump of that. The latest svn version allows
such tomfoolery. If you want a public svn repo and collaboa instance
I can provide that at caboo.se

Courtenay

Courtenay wrote:

> It turns out that the current i2 install was from Dan Peterson's own SVN
> repository, back in July. We don't have commit access to that
> repository, and Dan hasn't answered any of my mail since 8th June.
>
> I think the right thing to do in these circumstances is for David to
> create another branch in the i2 repository, to put the current rails
> wiki source in that branch, to give you commit access, and to arrange
> for someone to do redeployment via Capistrano when you are ready.
>
> regards
>
> Justin Forder

Sounds good to me - I can integrate the plugin and tests that I have
for the Madison rails wiki. That should at least save a good amount
of your time doing rollbacks.

Let me know if/when we get the branch setup.

I just saw Dan on IRC and he said his repo is here:

http://svn.dpiddy.net/projects/i2_rails/

Yes, and the Rails wiki is running on revision 44 from that repository.

I suggest you do a svn dump of that. The latest svn version allows
such tomfoolery. If you want a public svn repo and collaboa instance
I can provide that at caboo.se

Thanks - no need. Sorry for the brevity, once again I have a train to catch!

regards

   Justin

So, just to clarify - if I edit rev 44 from that svn instance of i2 to
add a logic captcha, it can be deployed to the production rails wiki
to hold off spam for a bit. And Justin can stop spending an hour a
day rolling back spam. Correct? :slight_smile:

- Rob

So, just to clarify - if I edit rev 44 from that svn instance of i2 to
add a logic captcha, it can be deployed to the production rails wiki
to hold off spam for a bit. And Justin can stop spending an hour a
day rolling back spam. Correct? :slight_smile:

It would appear so, we can figure out any trivial merges anyway.

Rob Sanheim wrote:

Hello all,

There is very intersting discussion going on here. My name is Robert
Dempsey, and I work for a Rails development firm in Florida. I have
been rolling back the Development Firms page on the wiki for quite some
time. Thank you for implementing the latest updates.

At the risk of sounding stupid, I am writing to get your thoughts on a
site where everything would have to be submitted and have someone look
over it? So, if a firm wants to post their information they can do so,
however, before it goes online, someone looks at it. I am also trying
to think of more ways in which Rails can be promoted, like Java or
.NET. I have some time to put into this and have begun to work on
building a site structure to support my idea.

I am very interested in your thoughts. Thank you for your time.

Sincerely,

Robert Dempsey

You want to be that guy? Good luck! You'll need it!

I am building the site right now. When I have enough created, I would
appreciate you all taking a look and giving your opinion. Obviously,
there is no silver bullet against the ever hated spammers. In trying to
think of ways in which to promote Rails and help the community, I came
upon the idea of an organization that will do just that (in addition to
the work everyone else is doing). I appreciate your feedback and vote
of confidence :wink: