jzila
Yes, ad blockers work. But they are susceptible to the tragedy of the commons: it's always advantageous to install an ad blocker. Then, as they proliferate, companies must insert more and more intrusive ads. This encourages more people to get ad blockers.
Allowing a tiered economy for content will enable those who wish to pay to do so, and those who don't to see ads. The ads can become less intrusive because the companies are no longer playing a cat-and-mouse game with their inventory. That should decrease the incentive to use an ad blocker, allowing that revenue stream to stabilize.
We give a little bit of detail here: https://keybase.io/docs/kbfs#frictionless-sharing
But the basic model is that when you share or chat with someone@twitter, that content is only encrypted to your devices. When that Twitter account posts a proof, and announces that proof on a Keybase account, Keybase's servers will notify your devices including a link to the tweet. Your device will independently verify that the cryptographic proof is validated by the keys of the Keybase account claiming it, after which it'll re-encrypt the keys to that data for the newly verified Keybase account.
This all happens seamlessly in the background.
I hate to use HN for bug reports, but since you asked about roadblocks (thank you for asking!):
For one, we use build triggers to ensure downstream dependencies are tested as well as the current project. I would have expected some kind of pipeline integration between those in BO (displaying the triggered build pipeline in the parent pipeline as a whole), but instead BO actually makes it more difficult to get to downstream builds.
Classic:
https://jzila.keybase.pub/classic_downstream_build.png
https://jzila.keybase.pub/classic_downstream_build_detail.pn...
Blue Ocean:
https://jzila.keybase.pub/bo_downstream_build.png
Note that in BO it isn't clickable, so I have to either manually type the URL or go back to Classic.
Some display bugs in the pipeline view:
- Issues with display of pipeline nodes in running builds that make what's happening pretty confusing: https://jzila.keybase.pub/running_build_display_bug.png
- Issues with display of pipeline nodes in finished builds (falsely reporting node failure): https://jzila.keybase.pub/finished_build_display_bug.png
Minor grievances:
- Nodes run in parallel don't have their hierarchy preserved: e.g. parallel(a: {}, b: parallel(c: {}, d: {})) all get collapsed into a, b, c, d parallel nodes in the BO pipeline view (as you can see in the bo_downstream_build screenshot above).
My contact info is at https://keybase.io/jzila if you need more details.
It also switches your default GitHub links to Blue Ocean. If you only want to try it out, you'll have to tell your users to switch their Notification URL back to Jenkins Classic in their user configuration page. (If there's a way to do this for everyone, I'd love to hear it.)
I think most people can agree that sex trafficking is terrible, and we should pursue approaches to minimize it. Studies have shown that existing attempts at legalizing prostitution do not at all curb trafficking: in fact the increase in demand cancels out the increase in supply, keeping the market open for traffickers and abusers [2]. Given what we know so far, it's probably worth keeping prostitution illegal if we can't figure out a better way to keep sex trafficking down.
That said, there is a fascinating paper that analyzes the economics of the regulatory approaches that have been tried in various countries, and makes a recommendation for a legalization framework that might benefit all parties [3]. The authors note that while criminalizing supply (prostitutes) has no downward effect on trafficking, criminalizing demand does, and in fact trends toward 0 when the penalty is severe enough. They recommend a hybrid approach that regulates and licenses voluntary prostitution, while heavily criminalizing consumption of unlicensed prostitution.
If nothing else, this is a fascinating topic with plenty of room for further research. Conflating prostitution (transactional sex) with human trafficking doesn't serve to further that discussion, and they should be reasoned about separately.
[1] http://www.seattletimes.com/seattle-news/crime/online-site-w...
[2] http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1986065
[3] http://lsr.nellco.org/cgi/viewcontent.cgi?article=1303&conte...
The approach you detailed is the way to go once the filesystem is in the wild. Such power!
So, yes, dry-ice level temperature, but incredibly high pressure.
That said, re-reading Elon's article, he did explicitly say _kinetic_ energy in the 120GJ figure, in which case 0 is the right number for New Shepard at 100km.
Your visualization makes it clear how everything from time dilation to length contraction can be derived from simply knowing the Pythagorean theorem and the constancy of c.
Of course, that isn't advice specific to your situation, but at least it shows you a general direction you can use to guide your thinking. There are also plenty of resources online that talk about the potential tax consequences of various exit scenarios.
Normalizing performance between the two interview types will be challenging, but I think the benefits to be reaped far outweigh the difficulty of the challenges.
You can accept the author's implication that discrimination based on intelligence, charisma, good looks, etc is immoral. You can even accept that business and commerce are inherently unfair because they discriminate on such characteristics. Despite all that, a business-based (capitalist) economy is the best way we know to align the interests of the individual with the interests of the society. The author's philosophy completely fails on that front.
There are other failures to this philosophy, but I think that one is the most egregious.
Right now, engineers search through many companies to find a job, and companies search through many engineers to fill a position. The traditional way this is done is an interview gauntlet, whose primary purpose is to verify technical ability. Since that's something that should only be done once per engineer, TripleByte seems to be providing that intermediary service. Then a much shorter set of interviews can be used to check fit, thus saving each candidate and company an incredible amount of time.
hired.com is another company trying to do something like this, albeit using a slightly different methodology.
edit: I accidentally a word.
Her ability to process information and distill critical data is unparalleled: she'll find out everything she needs in 2-3 questions tops. I've seen her do this in front of both highly technical audiences and less technical ones: she perfectly tailors her speech to exactly the level that her audience needs. She sets a great example for how to communicate in a work context.
I think this is what makes her such a fantastic engineering leader: she uses her unique skillset to help remove as many barriers as possible. This enables everyone who works with her to be a better version of themselves, which pays huge dividends.
The Dangers of Ubernomics
Here's the HN thread on that topic: https://news.ycombinator.com/item?id=7695621
The Wikipedia articles on telomeres and telomerase have plenty of further resources[2][3].
[0] http://learn.genetics.utah.edu/content/chromosomes/telomeres...
[1] http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3370421/
[2] https://en.wikipedia.org/wiki/Telomere#Cancer
[3] https://en.wikipedia.org/wiki/Telomerase
edit: formatting