jzila

There are those of us who look forward to exactly that: the ability to own our participation in the content we consume. When you pay for content, you are the customer. When someone else pays for the content, you are the inventory.

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.

Thanks for the feedback! We've recently implemented some pretty big performance improvements in the filesystem, including prefetching files, caching them encrypted to your local disk, and journaling for writes (allowing us to sync them over some period rather than blocking on your network connection). If you're still experiencing poor performance in the filesystem, please file a ticket on github.com/keybase/kbfs or contact me on Keybase chat (keybase.io/jzila).

We give a little bit of detail here: https://keybase.io/docs/kbfs#frictionless-sharing

Great question!

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.

First of all, congratulations on an excellent job with the design and UX of Blue Ocean! There's tremendous potential here.

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's great and beautiful. However, it isn't yet as powerful as Jenkins Classic. So if you've been using Jenkins for a while, there's a good chance that Blue Ocean doesn't have the power/granularity you'll need.

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 can't seem to enable indexing for my team's public repos, only my own. Other sites with GitHub login (e.g. Travis) allow you to login as your team rather than your individual user. Can this be enabled?

There has been at least one high-profile sex trafficking bust in the Seattle area recently [1]. That seems to correlate with an uptick in opinion articles decrying prostitution and all its problems.

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...

I actually wrote something like that for Keybase before KBFS was announced: https://github.com/jzila/kb-login-ext

The approach you detailed is the way to go once the filesystem is in the wild. Such power!

From the article: "...hydrogen sulfide under a pressure of 1.5 million atmospheres exhibits phonon-mediated superconductivity at 203 K".

So, yes, dry-ice level temperature, but incredibly high pressure.

I think the point was to illustrate the difference in energy requirements for the rocket to impart to the payload.

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.

Sure, but it's energy that a rocket needs to impart nevertheless.

Potential energy is energy, so it's not quite correct that New Shepard had 0 joules at 100km. At 100km and 0 velocity it'll have about 1 gigajoule of energy per metric ton of mass.

This is beautiful. It's the first time I've been able to understand special relativity in terms of geometry.

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.

Sam Altman talked about this in his Employee Equity post: http://blog.samaltman.com/employee-equity. "The idea is to grant options that are exercisable for 10 years from the grant date, which should cover nearly all cases (i.e. the company will probably either go public, get acquired, or die in that time frame, and so either the employee will have the liquidity to exercise or it won’t matter.)"

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.