Recent submissions

Comment · 9 years ago
Comment · 9 years ago
Nit: recipient is the correct spelling for the book. Will keep eye on this.
Comment · 10 years ago
There's a stackexchange with technical answers to most of these questions, such as:

http://ethereum.stackexchange.com/questions/191/how-can-i-se...

For #3, an introduction is:

https://blog.ethereum.org/2015/12/24/understanding-serenity-...

and the improvement proposal is: https://github.com/ethereum/EIPs/issues/28

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?

https://github.com/ethereum/EIPs/issues/26

Comment · 10 years ago
Comment · 10 years ago
Perhaps Github Issues itself should be available as a mechanism for people to provide feedback about Github itself.
Comment · 11 years ago
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.
Comment · 11 years ago
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?
Comment · 11 years ago
Comment · 11 years ago
With crashes, though rare in Chrome, when one does happen it usually kills all my Chrome windows instead of a single tab as is touted :/
Comment · 11 years ago
Comment · 11 years ago
Nothing to be sorry about; you made me look up 'dublicate' because it would be good to know if it was a real word. We're about sharing knowledge here.
Comment · 11 years ago
Note: since you wrote it twice incorrectly, the word is spelled 'duplicate'. 'Dublicate' could be an interesting word since it resembles double, but it doesn't exist yet.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton