Usually they will just get a cease and desist.

If they are profiting off their work to the extent that it actually makes business sense for the game company to sue them for damages, then that is the action they can expect to get.

Qihoo bought Opera too. CRAP :(

just want to ask if there's anything a home user could do to detect unusual routing behavior/phenomenon? I'm envisioning something like a browser plugin that logs/monitors outgoing connections and traceroute data

With that, instead of just looking at 404s we can make more informative observations like this request got stuck at this node, or that request is routed through a new node which has never been seen before recently..

I never knew the gems were not subjected to version control at all on the server. Can't they put everything into a git repository somewhere?

Have you stopped beating your wife? Are you now aware of the mass assignment bugs?

Aside from the fallacy, it is a false argument to pose all risk as bad. Given what is presumed to be your idea of acceptable risk, I would expect you to surf the net behind 7 proxies: http://knowyourmeme.com/memes/good-luck-im-behind-7-proxies

The tests using put and delete do not work if session-based authentication is used (one of the exercises). using page.driver.put will redirect to http://example.com with seemingly the correct path, testable using have_selector, although I wonder if there are better workarounds.

Not sure if you are aware of this...for the first edition of your tutorial, webrat is required for many of the tests (I tested on ubuntu/windows), but inclusion of webrat will actually break some of the new tests (like those using have_selector) in the second edition. You might want to add a warning to those who have followed the first edition and are trying to incorporate the additions in the second edition.

The 2nd edition explicitly uses Capybara instead of Webrat. As long as people pay attention to their Gemfiles, they should be fine.

It would be nice if you can discuss the differences, like how Capybara is meant for integration tests, and replacement for have_template etc. At some sections the tests are still referred to controller tests (Listing 10.46) although it looks like you intend to convert them all to integration tests.

Also, 11.37 tests do not work with valid_sign_in (using session authentication), but works with the controller.sign_in method introduced in 1e.

Incidentally, I just completed the first edition of the tutorial and screencasts recently, and thought I might as well try to integrate the new testing tools in 2e beta. Unfortunately, guard-spork does not work on Windows and I wondered what happened to autotest (it works really well with Growl on Windows)

Also, the guard command prompt is unusable on Windows now: https://github.com/guard/guard/issues/204.