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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/7/07, Andrew Kaspick <akaspick@gmail.com> wrote:> > 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 > > AndrewYeah, 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/7/07, Rob Sanheim <rsanheim@gmail.com> wrote:> On 1/7/07, Andrew Kaspick <akaspick@gmail.com> wrote: > > > > 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... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/7/07, Courtenay <court3nay@gmail.com> wrote:> > On 1/7/07, Rob Sanheim <rsanheim@gmail.com> wrote: > > On 1/7/07, Andrew Kaspick <akaspick@gmail.com> wrote: > > > > > > 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
> 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. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/7/07, Justin Forder <justin@j-m-f.demon.co.uk> 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? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Courtenay wrote:> > On 1/7/07, Justin Forder <justin@j-m-f.demon.co.uk> 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/8/07, Justin Forder <justin@j-m-f.demon.co.uk> 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 ForderI 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/8/07, Rob Sanheim <rsanheim@gmail.com> wrote:> > > 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. ... > I''d just need svn access to the current i2 install. This would at > least stop the bulk of spam until Ruse is installed.Good idea, contributors to the wiki would then only need to learn American history to be able to answer those "logic" questions </irony> -- Mislav --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Rob Sanheim wrote:> > On 1/8/07, Justin Forder <justin@j-m-f.demon.co.uk> 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/8/07, Justin Forder <justin@j-m-f.demon.co.uk> wrote:> > Rob Sanheim wrote: > > > > On 1/8/07, Justin Forder <justin@j-m-f.demon.co.uk> 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 ForderSounds 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
> > 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
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.seThanks - no need. Sorry for the brevity, once again I have a train to catch! regards Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/9/07, Justin Forder <justin@j-m-f.demon.co.uk> wrote:> > 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 > > JustinSo, 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? :) - Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
> 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? :)It would appear so, we can figure out any trivial merges anyway. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Rob Sanheim wrote:> On 1/9/07, Justin Forder <justin@j-m-f.demon.co.uk> wrote: >> 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? :)Yes, that would be excellent :-) :-) Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
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 received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/20/07, Robert Dempsey <robertonrails@gmail.com> wrote:> > 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?You want to be that guy? Good luck! You''ll need it! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
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 ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
I failed to mention the scope of my project. I do not intend to recreate the wiki (as my earlier description may convey), rather, I am focusing on the promotion of Rails, and the developers and firms that use it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/22/07, Robert Dempsey <robertonrails@gmail.com> wrote:> > I failed to mention the scope of my project. I do not intend to > recreate the wiki (as my earlier description may convey), rather, I am > focusing on the promotion of Rails, and the developers and firms that > use it.Isn''t it what http://www.workingwithrails.com is doing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
They are, however, I have a different approach to the promotion. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Good morning all. We have launched the initial Railsforall.org site, located at http://www.railsforall.org, with a full launch planned within the next month or two. Visit the site and sign up to be notified of the official launch. Railsforall.org is dedicated to the promotion of Ruby on Rails in the developer and business communities. ** We need your help! ** We are looking for case studies. Case studies will show the business community at large that Ruby on Rails works, and is useful for a variety of applications. Not only does a case study lend credence to Rails and its uses, it also provides an advertising opportunity for you, your firm, and the application. Shoot us an email (info at railsforall dot org) for further details on what is required. I look forward to your responses and case study inquiries. Sincerely, Robert Dempsey Founder Railsforall.org http://www.railsforall.org --------------- Promoting Ruby on Rails to the developer and business communities On Jan 22, 2:44 pm, "Robert Dempsey" <robertonra...@gmail.com> wrote:> They are, however, I have a different approach to the promotion.--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Hello, I emailed DHH and asked him if I could fork I2 wiki that is used by Ruby on Rails wiki b.c it seemed no one was maintaining it... DHH granted my requested thus, I have created a fork these past couple of days, called RaWiki. I have integrated the captcha_validation plugin into RaWiki to prevent spammers. I also implemented a 10 chances and you''re banned for 24hrs with the captcha_validation to prevent spammers from brute-forcing the captcha. I plan to keep developing RaWiki b.c I am also working on another project, http://techniwiki.com, to create a community of docs, and hopefully offer free documentation hosting for other projects.... eventually the idea is a central repository of docs. You can see RaWiki working at http://techniwiki.com and test it out, if you like. If any of this sounds like it may be useful to the Rails wiki, let me know and we can work out the details. __ Donnie Jones Justin Forder wrote:> Rob Sanheim wrote: > >> On 1/9/07, Justin Forder <justin@j-m-f.demon.co.uk> wrote: >> >>> 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? :) >> > > Yes, that would be excellent :-) :-) > > Justin > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Justin Forder wrote:> Rob Sanheim wrote:>> 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? :) > > Yes, that would be excellent :-) :-)I set up another repository, and we moved rev 44 into that, then applied some changes that had been made locally on the deployed wiki. Chad Johnson integrated your BrainBuster CAPTCHA, and Ben Rockwood deployed it last night (this morning for me, UK time). It seems very effective! Chad made some changes so that a wrong answer to the CAPTCHA doesn''t lose the data in the form. You can find the code here: http://svn.jufo.org/i2_rails/trunk/ Thanks for your excellent code! Justin Forder --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Great, thanks for letting me know. Sorry I couldn''t help out on it, been way too crazy with my job lately. - Rob On 2/10/07, Justin Forder <justin@j-m-f.demon.co.uk> wrote:> > Justin Forder wrote: > > Rob Sanheim wrote: > > >> 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? :) > > > > Yes, that would be excellent :-) :-) > > I set up another repository, and we moved rev 44 into that, then applied > some changes that had been made locally on the deployed wiki. > > Chad Johnson integrated your BrainBuster CAPTCHA, and Ben Rockwood > deployed it last night (this morning for me, UK time). It seems very > effective! > > Chad made some changes so that a wrong answer to the CAPTCHA doesn''t > lose the data in the form. You can find the code here: > > http://svn.jufo.org/i2_rails/trunk/ > > Thanks for your excellent code! > > Justin Forder > > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Rob Sanheim wrote:> Great, thanks for letting me know. > > Sorry I couldn''t help out on it, been way too crazy with my job lately.That''s OK. The CAPTCHA is making a huge difference - spam on the wiki had been peaking at around 3000 page changes a day, and now it''s down to a handful. - Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---