Though, Twitter would need to make the layoffs random, force co-workers to escort the laid off off premises, and take away perks for a few weeks... If that's what they were angling for.
"Note that, with careful optimization, only 14 gajillion messages are necessary. This is still too many messages; however, if the system sends fewer than 14 gajillion messages, it will be vulnerable to accusations that it only handles reasonable failure cases, and not the demented ones that previous researchers spitefully introduced in earlier papers in a desperate attempt to distinguish themselves from even more prior (yet similarly demented) work."
So, I guess the question becomes.. is there a (or what is the) difference between:
1. [0, ∞)
2. (0,1]
when it comes to a currency?
I think that the traditional "boil the frog" approach of monetary inflation is psychologically easier for people to take.
A central authority just sort of wills new currency into existence as it is demanded.. Which, presumably, allows for price stability.
To me, the fact that it is hard to get "1 bitcoin" makes it too unstable. Someone could will 0.001 bitcoin into existence and pay $1 for it.. but, that 0.001 bitcoin may be worth $0.50 tomorrow (but then worth $3 the next week). So.. what's the point (presuming I desire an alternative currency).
One needs a clever way to create an "algorithm" (seems people think this stuff is as magical as the idea of a central bank).. that people trust to sell currency units.
The system would just run and sell 1 bitcoin (or 1 mystery coin or whatnot) for $1 to anyone who wanted it. The goal would be to achieve parity with the dollar (and maybe any other currency).
The thing this magic algorithm would NOT do is.. it would not BUY its mystery coins back. It would just create a verifiable.. non-counterfeit coin for anyone who desired one for a set price.
If a deflationary spiral set in on the dollar.. well, magic algorithm learned from Soros and the Bank of England.. you don't fight that..
I don't know... sounds like they just shifted the 'single point of failure' to the Zookeeper cluster. Is it somehow sexier to have your SPOF be things running Zookeeper instead of things running loadbalancer or DNS software?:
"The achilles heel of SmartStack is Zookeeper. Currently, the failure of our Zookeeper cluster will take out our entire infrastructure. Also, because of edge cases in the zk library we use, we may not even be handling the failure of a single ZK node properly at the moment."