For #1, there are checksums now, but the more interesting question and challenge is how would a decentralized registry/DNS be designed, that has reasonable anti-incentives for squatters?
Both editions of the book were before the invention of blockchains. Integrating it in the next edition of the book would be solid work: not just explaining a blockchain but really integrating it with existing parts of computer science.
Why? Interested in your reasons. One plausible one is that trusting an author you know can be more practical than examining every line of a massive open source code base. Could that be a reason? Others?
Shotgun blast: open source software is easier to read. Is the quality higher? Depends: there are some terrible vendors, and there are some very shoddy open source security projects. Open source software, with a couple of exceptions, are rarely audited professionally. Widely used open source projects get shaken out for memory corruption and XSS. They do not as a rule get thoroughly evaluated for cryptographic flaws.
A more precise way to state my preferences:
I trust _crypto_ from Microsoft, Apple, or (especially) Google more than I trust _crypto_ from a developer I've never heard of before. I do not as a rule trust rando closed-source projects.
It depends which process crashes. Usually and rare a sub-process crash which means a few tabs need a page reload. If your main process crash (which should be very very rare) then I would suspect you have a faulty memory module in your device or you have little free memory or your operating system has not optimal scheduler (e.g. server OS on a desktop).
I've seen it irregularly on multiple machines, Windows 7, Windows 8 and now Mac OS X. It's actually really soured me on the whole idea of a multi-process architecture. I understand the theoretical benefits, but I don't see messages that a particular tab crashed that much more often than that the entire browser crashed.
"Little free memory" means that Chrome has eaten all my ram though.
Chrome is really lagging behind Firefox in this, as it has no backgrounding / unloading process that I'm aware of to maintain a reasonable memory footprint.
It also attempts to render every tab at once when restoring after a crash - another obvious problem.
Or maybe not, I think they have automated crash reporting (I even used their library, breakpad) but my Chrome has been very consistent in crashing on Windows wakeup for over a year now.
It's not clear what parts the author modified last month, since the bulk of the article is from the past. A separate, additional article would be interesting to hear author's recent views and experiences.
For something upcoming, http://www.augur.net is an attempt at a decentralized prediction market.
https://bitcoin.stackexchange.com
https://ethereum.stackexchange.com