I was slightly younger than fourteen when my fifth-grade teacher staged a bridge-building competition in the class. She priced the raw materials (mainly toothpicks, glue, and string; I can't recall what the various exotic items were), and graded us based on ineffables such as teamwork and empirical metrics such as how much we spent on materials and how much weight the completed bridge supported.
As is often the case, this review can be recommended instead of the book; anyone who still wants to read the book after the review, is quite likely to enjoy it.
Last I checked, there's a single blessed node dishing out verifiable data. It's nicer than having a remote API that just hands you a trusted number, but it's a far cry from Nakamoto Consensus.
Seems like a good opportunity for a company that genuinely cares about employee health to make it easier for them to eat well by stocking the kitchen with healthy snacks.
People asking questions, lost in confusion
Well, I tell them there's no problem, only solutions
- John Lennon
The other solutions proposed here work at the wrong level. The approach taken by I2P[1] does away with the concept of globally squattable names[2], leaving public keys as the global identifiers and letting individuals define local nicknames or delegate to trusted lists.
PS: I had a chance recently to talk with a "DNSquatter": the doorman at a building I frequent. Poor guy bought tens of thousands of domain names, years ago, with money he had available for investment, and asked me for advice on how to cash out his investment. It seems to me that he's the victim of a chumpatron[3], rather than the scammer himself; although his actions do help keep the scam alive. I advised him to consider the money lost.
One of the advantages of it is that it can be used to mimic the DNS/SSL model or any other PKI just by imposing the right priority calculation rules, so you at least don't lose any capabilities with it.
