Yep, thanks ryan.
Thanks, Ryan for your hard work... Might as well leave comments off since at this point they are worthless. I used to glean knowledge from the comments, now it's a waste.
I agree with Iar but sometimes people really share something of worth in the comments. I think adding a captcha would help a lot.
great tutorial as always, very helpful for some of the people who haven't jumped ship yet. But my goodness the spam is getting overwhelming here, I'd suggest at least adding some sort of comment filter.
I'm with Florian here. I sometimes go through the older 'casts and just to keep things clean, I pick off all the spam. Hope it helps Ryan and thanks for the railscasts!
I agree with the people here. I find the comments also very helpful. Captcha is very easy to add right? I imagine that Ryan is already busy. Ryan do you want some of us fork your site and add captcha to it or something?
Btw this episode becomes really handy!
I was wondering what theme you use in textmate. I really like the way it looks, does anyone know where I can find it? Thanks a lot!
Also, awesome screencast, super useful! Best rails screencast site I've been to.
You can find info on the railscast textmate theme and fonts here:
Thanks a lot dude! Really appreciate it!
I asked the same question, read comment 14 for the answer, it has a download of the theme and everything.
This was really useful. Thanks Ryan!
Captcha in place?
Err... I assume this is going to ask me something anti-spam in a second... If not sorry for posting rubbish but the obvious reason why SPAM is so high is because it's so easy to post it.
I assume you know there is no anti-spam on comments which would explain any recent SPAM :(
My 2 cents comment about the Spam problem: those tiresome "comments" are only posted because they allow the target site to increase their visibility to search engines by adding a few more links pointing to them.
Remove the "Website URL" field and it will make railscasts.com's attractiveness to dicrease by 100% for the spamers while the rest of the comment functionnality will remain the same for the real users (except perhaps, for those of us who also use this field to improve the visibility of their own blog/corporate website ;-) but I'm pretty sure they will be OK to trade this little "feature" for some reading serenity, won't they?)
@de_an777 (Aug 12, 2010 at 03:22):
This is a typical spam comment: a partial copy/past of a previous comment (here, from the comment you did last Wednesday at 17:28), with the poster name linked to the spammer website.
No need to reply to such spam messages, just use the "Report as spam" link to eradicate those irrelevant posts.
@Frederic (Aug 12, 2010 at 15:20):
I agree with you, that railscasts.com is abused as a linkfarm. Removing the URL would be one step (and I second your recommendation).
But I think those spam comment are automagically generated. So these comets would be posted anyway. But without links.
I don't think, that those spamers care if some of their messages don't work as intended.
For forking and improving:
Trying to follow thru the rspec parts.
Ran the generator (new spec_helper etc) - but rake spec is still giving
no such file to load -- spec/rake/spectask
Not sure where to go with this - am finding some hits on google about the task moving to rspec/core/raketask (http://github.com/rspec/rspec-core/blob/master/Upgrade.markdown) - but I can't see how to apply changes to fix it.
I still can't get this to work, rake spec fails with 6 errors, with the railscasts app from github:
#6 is related to the PST time zones, #4 and #5 seems to be a fixture load order thing, no idea wtf #2 and 3 are, and same for #1.
When I run 'rails g rspec:install' I get a new rails project. Why does this happen?
Good article keep writing
It is a very nice thing to see your excellent work and I like your article very much. With your rich knowledge, we can learn more from your wonderful post. Thanks so much.
It is so lucky to read your blog,it is full of useful message.I wish we both can do better in the future.It great honour if you can visit our website,and give us some suggession.
First sign in through GitHub to post a comment.