Source: https://scholar.google.com/scholar?cluster=14914487445955020...
283 karma · joined November 18, 2009
Source: https://scholar.google.com/scholar?cluster=14914487445955020...
My grandma was 20 when a guy named Claude Shannon in 1949 invented/popularized the concept of a "bit" and described what information is, the way Newton described matter and how to model physics with mathematics.
Really, "information" was a just vague concept until Shannon and this was just 70 years ago!!1
It's only natural that a lack of generations of craftsmanship in this industry makes it pretty low quality/hard to master. On the other hand, imagination is the limiting reagent, since (arguably) the bottleneck is good ideas, specially with all these decades of Moore's law.
It makes a number of errors, most notably, calling the hashing power spent on securing the network "donations" (quotation marks sic).
Bitcoin has one job: securing the network of transactions.
Bitcoin is a mechanism to aggregate hashing power in order to make it possible to semi-objectively measure the risk of a block being reverted, in fact, this is the only formula in bitcoin's white-paper.
The paper examines a system of economic incentives, and somehow dismiss its key activity as an altruistic "donation". The article goes downhill from this statement onwards, and I couldn't feel like it makes a huge (yet ineffective) effort of deconstructing Bitcoin's governance model.
Some quotes that reinforce the superficial understanding of the Author:
> There are times, however, when two miners can find the correct nonce for a new block within a few seconds of each other and both broadcast their valid block of transactions (nigh on) simultaneously to the network. This causes a split, or fork, where miners go ‘rushing off’ to mine on top of two competing blocks. Because this form of divergence is endemic to the blockchain’s mechanics it is referred to here as a systematic fork; the discrepancy should be quickly resolved by network mechanisms (this happens, on average, two or three times a week). Systematic forks are temporary glitches...
These forks are essential to maintaining decentralization as a mechanism to make the network secure: trust the info, not the people that delivered the data, trust the signing mechanism (hash power spent), not the people running the machines.
> Furthermore, the political strategy of a user activated soft fork still requires code developers to create a client that reflects the political will of the market and thus demands the obligatory passage point of a Lead Developer found in version control systems.
Not true -- the UASF measures were not merged into the Bitcoin Core branch. Some code was merged to protect users from potentially problematic interactions with Bitcoin Cash fork.
Modeling Bitcoin's governance system is a daunting task. The author essentially confuses the power developers have with regards to miners: developers know there are things that would never fly with miners, and miners are way more powerful than what is described in the paper.
It feels way more human than a big corporation's effort, and way more direct.
* Discouraging the use of the webapp (if any available) in favor of a browser application (chrome app, firefox app, etc)
* 2 factor auth to login
* Bitcoin "multisig" transactions: require at least N out of M valid private keys (allowing the storage of these keys to be on different devices/services/media) before releasing funds
And of course encryption before storage.
"Hey, take my credit from X gateway" "Sorry, I don't trust X"
And let me note that making my app work on IE took me two days of work. That is what IE doesn't get and why web developers are mad at IE.
It slows down the pace of amazing UX growth in the web.
(edited: typo)
Marketing using the word "open" is the new fashion.
I've been using gcc for a while now, and every time I use it I found a new feature. It's rock solid and had never let me down.
Most of them in my case are software development-related stuff. Before being so afraid of “the power that google has” just check you history: it’s less frightening than what commercial made you believe.
You are right, one gram is the weight of one cubic centimeter of water at 4ºC (a little away from 0ºC so you don´t solidify by mistake).
I heard that imperial units used to change a lot, that the patron was the current king at the throne. Do you know if this is true?
I've read HN for two years now... made an account just a few days ago... I don't write a very good english (I understand it really well though) so I've never felt like commenting...
I've been a IOI participant twice -> and twice a looser.
The ones that I found more interesting were the ones on line sweep and geometric algorithms.
On Fenwick's Trees; this tutorial http://www.topcoder.com/tc?module=Static&d1=tutorials... is really good. Although, the original paper is well-explained: (link to the author's website) http://www.cs.auckland.ac.nz/~peter-f/ ("A new data structure for cumulative frequency tables")
And on bit manipulation; I highly recommend you read this... you'll be thinking in zeroes and ones for a while... http://www.topcoder.com/tc?module=Static&d1=tutorials...