skysight-inc/HackerNews huggingface dataset:
> Does anyone commonly set their priors to be a distribution? Perhaps a range or actually a normal distribution to represent a prior with uncertainty?

Almost everyone does this, and the solution is a posterior probability distribution. Most uses of Bayesian techniques that I'm familiar with are based on Monte Carlo simulations, where priors are drawn from the specified prior distribution, processed in some fashion, and result in samples of the posterior distribution.

This is especially helpful when you don't view the problem as having a 'true' single answer with some 'uncertainty' but instead have actual variability in the system, which is described by the posterior distribution.

Thinking about it, I'm really not sure in what instance the prior wouldn't be a distribution. It is, by definition, a probability. I suppose you could have a singular value, where the pdf is a delta function, but what's the point of doing the Bayesian inversion or estimation then? If you have a single value with prior p(x) = 0 or 1, you should end up with the posterior p(x|d)=0 or 1.

So the simplest case is where the prior is a binary: Say p(x=yes) = 0.6, p(x=no)=0.4. Or something like that. It's not a continuous distribution but it's still a distribution. The sum/integral of all cases has to be 1.
I think your view of car ownership and the suburbs is the wrong way round.

In my experience, people in the suburbs own cars because they have to in order to live in the suburbs. They don't move to the suburbs because they own cars, and want somewhere to store them.

The traditional appeal of the suburb (or the 'countryside') will endure. More space, lower crime rates, fewer neighbors, more privacy, better schools, a stronger sense of community, etc.

If anything, the self-driving car will make the suburbs more attractive, as fewer cars will litter the place, paved-over front gardens can be returned to nature, etc.
Looks like the reason their blog is down is because... it's now being targeted by a DoS:

http://status.linode.com/incidents/kldhjpjnfnkj

Attacking a blog talking about the hack? It sure seems that someone has a grudge against Linode. :-/
> Both Ripple and SCP create money out of thin air.

So does fiat, and fiat works. It may not work well all the time for 100% of use cases, but in general it works well.

As long as the mechanisms by which money is created out of thin air are well-understood by the people receiving this money (which they are for fiat) and the recipients give informed consent to that (which they... sorta do for fiat), this doesn't seem like a negative.
Considering your resume, you aren't in a position of power in salary negotiation. You have nothing other than good education.

If I were you, I would ignore salary negotiation, and consider employment in terms of learning opportunities and getting right experience.
Phone plans have gotten to the point where no lock-in is a compelling feature. What's keeping Apple at the point where people don't mind lock-in?
SpaceX's Falcon 9 Passes Tests
What's old is new again https://en.wikipedia.org/w/index.php?title=Plan_file
I'm sure their algo writers are looking for new work now lol
No damage to SpaceX's Falcon rocket
Even if its only 10% (and 10% of a billion is still 100 million dollars) do you really think its reasonable that 100[1] years after my death my family should still be spending the money that I myself earned?

To put that in perspective, people who died in 1916 are:

Hetty Green - the 'witch of wall street' one of the first ever successful women investors

Charles Taze Russell - the creator of a religion that would later be called 'Jehovahs Witnesses'

Saint Albert Chmielowski - a Polish religious leader who was made a saint in 1989

Grigori Rasputin - a faith healer and friend of the last Tsar of Russia Nicholas II

So we are talking about the modern day descendants of these people, still holding 10% of any wealth amassed over 100 years ago.

If you honestly think it would be reasonable for the descendants of these people to still be living off the wealth amassed by their forebears, I guess I just disagree.

[1]Wikpedia says a generation is in the low 20's in years, i'll assume 20 to keep from being seen as inflating the numbers
If I include things like Medicare, Medicaid, Social Security, Education, etc... all social welfare programs add up to maybe $1.5T a year.

There are about 320M people in the US. Let's leave out anyone under 18 (23%) that leaves us with about 250M people.

Assume that somehow, all of these welfare programs are dismantled to be replaced by a BI. It's totally politically unfeasible, but let's imagine it happens. That leaves $1.5T to be distributed yearly among 250M people, which comes to about $500 a month. That's as a replacement of all medical aid, all social security, all public schooling, etc...

Proponents of BI cite higher numbers, and political reality means many of these programs will stay. This suggests that BI will not come about without a dramatic increase in taxation.
Reminds me of the very early days of the web when people would post htplans, hypertext versions of their .plan files.
The cofounder Michael Scanlon has a neuroscience PhD.

http://www.lumosity.com/about/our_team
Then I'm OK with not working with you.

Even if you are exactly as you claim, MOST people who claim "I can code but don't care to demonstrate it during an interview" are actual disasters as co-workers. I've been there, done that, cleaned up the messes, and would prefer to pass on some good people to avoid that.

And yes, you do have to pass on some good people. There are competent programmers who freeze up during interviews. You do what you can to make the interview as accommodating as possible, but some people can't show what they've got. However the opportunity cost of passing a good person by is far less than the damage from hiring a bad one. This leads to being risk adverse.
1. The additional cost is insignificant thanks to increases in CPU performance. The cost of 60 fps 4K videos is also high, and YouTube does this as well. You're confused about how good companies view costs and benefits.

2. Content filtering can be done in other ways, more effectively. HTTPS does not prevent this.

3. Everyone needs security and privacy.

You don't seem interested in learning, so I'm done trying. Keep believing whatever you want while the entire web moves to HTTPS-only for very obvious reasons.
You are not taxing them again (since they are dead) you are taxing their children/relatives who get the money without having done anything for it.

Plus if you are rich enough a lot of those money were not taxed like a normally family but most probably through things like capital gains or just appreciation (real estate) which rarely is a product of your specific work but rather societies work to turn an area into something thats valuable by building infrastructure etc.

When I buy something for my taxed money, whoever I give purchase it from is also being taxed on those already taxed money.

So by your logic its not fair to tax that either either.

If you buy the argument that we should tax businesses for the things they sell you are basically approving taxation of inheritance too.
I mostly meant the parallels with Tor (which is also openly government funded)
Exactly, unless the false positive is causal some how, testing again will reduce the uncertainty some amount. Though that amount may be less than if the false positive isn't completely independent.
Cloudless: Open Source Deep Learning Pipeline for Orbital Satellite Data
A customer warned Linode team about the exposed CF folder. CEO aggressively shrugged it off. "That doesn't matter, it's nothing, that's a non issue." Dev who was a bit of a suck up parroted the same telling support to shut up about it. This was six months before HTP happened.
They could cut through a tank. I saw it on the internet.
A cite for that if anyone cares:
https://blogs.msdn.microsoft.com/oldnewthing/20121218-00/?p=...
Ask HN: Looking for compression algorithm that took 6GB to 800MB. Anyone know?
Looking for a good media compression & archiving algorithm for an app I'm building. More specifically, I'm looking an algorithm I had used 10 years ago but had totally forgotten the name of. Description: It was a self-extracting archive (about 800MB) that spat out a folder of over 6GB (mainly media: movies & audio). Now, the media files themselves were already in compressed format (MP3, MP4, etc...) so I was really impressed. Only drawback (as expected) was that it took over 1 hour to decompress on an Intel dual core. Does this kind of performance ring any bells for anyone? I just need a name.
Testing React Components with Shallow Rendering
I find people that quickly do fuzbuzz type problems to be worse on average. The only way you can validate your interview assumptions is to randomly higher people you would have passed on. You could compare how important you think X is vs. how predictive it was for on the job skills, but few people actually onboard enough people to get good data.
But being a good bayesian makes you do exactly this. The process of describing priors makes it obvious you need to do a sensitivity analysis to check how much the prior is influencing the conclusions...
Yep, we chose CRAN for the MVP, since it's the main R package host. But adding other sources is the plan, and Bioconductor is at the top of that list for R.
In the simplified essay, PG explicitly states that some causes of economic inequality are bad:

> But economic inequality per se is not bad. It has multiple causes. Many are bad, but some are good.

He is not "conveniently" ignoring that point.
Really? Thomas Asaro told us they were all in jail.
If there's no work - it's not a blockchain. Distributed ledgers are a completely parrallel movement that was taken up by those who wanted to leverage the marketing momentum of blockchain, for their own database projects. Which is fine, but shouldn't get confused with blockchain innovations.
I don't see the word exclusively. If you had a chat application you could protect the user content by sending along a DRMed ping.
I think this is a common problem when people working in fields that have somewhat accurate mathematical models look at fields that don't. They often don't realize how hard it is to create an accurate mathematical model for many situations, and assume that the other fields don't have them because the individuals who work in said fields aren't as good at math.

Which is why every so often you'll get things like a physicist spending a couple months studying economics in their free time and deciding that they can now unlock the secret to economics which has eluded economists.

This xkcd comic sums it up well:

https://xkcd.com/793/
I see it like you. The switch to OpenJDK was needed so that the Platform could be on par with other Java8 Improvements.
Also GPL Code means that you aren't forced to use the vendors versions. Google could fork it easily if Oracle does dumb things.

The move to OpenJDK was needed and the article is clearly wrong about the winner.
Especially the loser sections. Heck i've never seen proprietary changes to Dalvik / Harmony based on Android. And there definitely weren't.
Most optimizations are kernel optimizations and other stuff and when I look how "fast" vendors will publish the kernel after an update...

> The entire middle part of the Android stack will be subject to proprietary Oracle control

That statement is so wrong. Especially in the GPL sense.
Implication is not commutative.
Did we break it? I can't upload pictures anymore.
I wanted to add: The self-extractor had no interface -- it was all in the windows command prompt. A message in the prompt said something about "Media compressor" and below it was the percentage extracted.
We were aware of it for probably an year before anyone bothered to spend 10 minutes looking at coldfusion source. That's all the time it took.
Certainly.

You can use either sqlite or core data (though core data isn't really a database).

In my own current project I started with core data but am now converting to sqlite.

hth.
No reason. No employee at a company ever received royalty for the code they write for the company.
I think the problem is that there are relationships that are very difficult to show cleanly using other chart types.

Relationships between quantities with different units are hard to show otherwise, without significant cognitive overhead (a new unit ), or two charts which causes inevitable back and forth examination.

You mention elsewhere that they are commonly misinterpreted or misleading. Care to show some examples? I can't think of any off the top of my head.

These particular charts are poorly done because their isn't enough information about which axis refers to which plot line, but are otherwise clear in intent.
Read his bio more carefully - he doesn't have a PhD, he was a PhD student. He does have an MS in neuroscience though[0].

0: http://techcrunch.com/2013/04/03/founder-stories-lumositys-m...
So many bouncing buttons. Can't concentrate.
If $15 per year is too high, just round it down to zero and analyze the business from there. On the other hand, if it's a niche product that has monetary value the price should probably be several hundred a year or more.

Good luck.
Nobody went to jail, I'm the only person being prosecuted. I won't go to jail.
http://nownownow.com/now

Heh. I had to check.
>The problem there is that the DC subways are some of the worst in the nation now, thanks to years of mismanagement and neglect.

The Metro has faced years of neglect, but it is still a functional system that moves hundreds of thousands of people daily. Despite all of the investment in roads, traffic is still a terrible mess from Gainesville and Fredericksburg to the District line.

> They've had fatal accidents, and they're ridiculously slow because they single-track the trains so much.

In the same year the DC Metro killed one person, 26 people died on DC's roads. Virginia and Maryland have their own traffic fatality reports.

The single tracking is mostly a weekend issue. It's terrible, and makes the system useless on weekends half the time, but the commute is generally good. They have a railcar shortage that is currently hurting reliability partly caused by the Japanase tsunami delaying new equipment, but once that's solved the numbers will increase once again. Weekends will remain terrible until someone competent takes the reigns.
Sometimes I've noticed I just don't "get" the problem being posed. Either it's because of ESL or well I just don't focus very well sometimes. It takes me a bit to figure out what's being asked and at that point it's usually very easy for me to go think about the solution and assumptions and such. But it does happen.
you might like google+, where you can follow collections in which a user posts only posts about one theme.
Unfortunately the author's website can't say the same - how are pop up's still acceptable?
And as a potential user I'm only half-insulted.

But seriously, what purpose would it serve over a promise in TOS? A normal user will trust both (except the button would be bullshitting them). A privacy-obsessed one will trust neither.
Yeah... our issues mostly arose from the fact that at the time, they were advertising 1Gbps node interconnect - which actually turned out to be 1Gbps HOST interconnect, with the nodes actually throttled down to 50Mbps. We use memcached extensively, and this was absolutely crippling for performance. It didn't help that they furiously denied that they were throttling until we demonstrated it beyond all doubt.

They did obligingly increase these caps when we begged them to do so, but at that point the writing was on the wall, and we kept on bumping into other weird and wonderful limitations and issues, such as the fact that someone running an intense job on the same host could bring our VPS's to an absolute crawl.

It really is a shame, as we desperately wanted to make it work, as we liked Chris's hands on approach (very much like ours), but ultimately our confidence in them was so eroded by the point that things started going genuinely wrong on their end that we had no choice but to leave.

As I said, we kept random small single-server stuff (wordpress sites mostly) there, as if you're not dealing with their networking, performance is generally OK - but the network limitations were an absolute clincher for us, and it was at one point literally every day that we'd find that one of their switches had broken, or we couldn't ARP IP's for no apparent reason, etc. etc.
Dual n-back, coffee, LSD. All things people swear make you smarter.

Coffee has proven to make brain work better. But it's only temporary.

LSD...well, I've never tried it, but people swear by it. Not sure if scientists would be allowed to try it on test cases.
I would like to see how this sort of thing could benefit people with traumatic brain injuries as it would be a great service to people suffering from this sort of malady but also probably easier to measure the effects on this group compared to a bunch of average individuals.
Without strict aliasing?

Generally, I think strict aliasing is a fine thing. It would have been nicer to have "restrict" be the default and "alias" being an optional specifier, but likely there was no way to do this without breaking too much existing code. Warnings are often nice, but I don't recall having any issues with compilers optimizing based on assumptions of lack of aliasing.

especially of templated code like the STL in C++

I'm an opinionated C programmer, but have no opinion of how C++ should handle things. I'm only considering the impact on C. If the STL requires an unfriendly C++ compiler, I'm OK with that, but this doesn't affect my thinking about C compilers.

However, the only—or at least the easiest—way the compiler can tell that this is the case is by observing that, for example, a null pointer would have to be dereferenced to get to that dead code.

Or, for example, that a signed integer addition would have to overflow. Or a full-width shift. Or a variety of other things that have a might make sense in both the programmers mental model and on the processor on which the compiled program will be run.

Therefore the compiler is doing you a favor by eliminating that obviously dead code.

Do you really believe that the compiler is doing you a favor by silently removing a check for signed integer overflow that you explicitly included? If so, we have found (at least one of) the point(s) of our disagreement!

If on the other hand you feel that removing security related error checking is an unfortunate negative consequence of a necessary optimization, perhaps we can find a way to mitigate the consequences?
it's what gave Twitter it's identity and allowed me to discover valuable information quickly. sticking a read more button to expand a tweet is just lazy and bad UX but worse, alters the fundamental usefulness of Twitter for me. it basically breaks the reading experience while introducing a host of issues and unnecessary friction. I'll surely alter my usage as well. I post way less now because of all of this AB testing and lack of product leadership.
Twitter is considering to allow message longest that 140, but I don't think that the problem is the character limit for the kind of interaction of twitter users. There are other problems not so big but that make the user experience not fluent for a simple app like Twitter.

Writing posts with more that 140 can potentially get many FB users, nevertheless TW should take care of the its current users. I notice many incoherences of the web app, for instance the top menu, on left where pop/up and navigation are mixed.

Second, the mobile app is very wired I receive notifications about message or followers that appears on my notification tabs randomly.

In conclusion, I love TW and I'm not a FB user, but I'm honest my twitter timeline is a bunch of Ads and I follow Twitter just because I love the concept of it.
Not to be snarky but you missed the most relevant part:

LastPass uses public-private key cryptography with RSA-2048 to allow users to share the key to their vault with trusted parties, without ever passing that information in an unencrypted format to LastPass. When Emergency Access is activated, each user has a pair of cryptographic keys – a public key to allow others to encrypt data for the user, and a private key that allows the user to decrypt the data that others have encrypted for them.

The key used to encrypt and decrypt your vault data is encrypted with the Emergency Access contact’s public key, and can be decrypted only with their corresponding private key. When setting up Emergency Access, you are using the recipient’s public key, encrypting your vault key with that public key, and then LastPass stores that RSA-2048 encrypted data until it’s released after the waiting period you specify. Only the recipient can decrypt the data, so no one else can decrypt it without access to the private key of the recipient you’re sharing it with, which is encrypted with their master password key. This process is completely automated, with no action required by the end user, and ensures that the data is inaccessible by LastPass or outside parties.

Basically, it sounds like LastPass has each client generate a keypair, store the private key in the vault, and give the public key to LastPass for distribution. I'm no security expert but it seems secure to me, at least as far as LastPass is considered secure.
None of this is surprising. I'm not sure what the author was expecting? Or if they're simply clarifying the scenario for others as a warning.

> "You would be paying that 70ms cost four different times."

Right, and either you're willing to pay that cost OR temporary inconsistency is acceptable to you. BDR doesn't warp the speed of light.

Also: If bank accounts are involved, inconsistency is not acceptable. Someone will bankrupt you. That's not BDR's fault.
From someone with years of experience with javascript, how is this "plain 'ol javascript"?

<ul>
{ heroes.map(hero =>
<li key={hero.id}>{hero.name}</li>
)}
</ul>
Ahh yes, "Here you go, since you can't afford a car, you should ride this nice shiny bus! Picks up you blocks from home, drops you off blocks from work, and guaranteed to take at least a long as a car commute, but probably much longer!"

Buses make good feeders to trains, but aren't so good for main routes. If you want people to use transit, it needs to be usable.

BRT is a good compromise.

I've done a cross-town bus commute and that was a good commute, the bus was crowded, but tolerable for 15 - 20 minutes. But then I moved and tried a longer distance bus commute from the suburbs to work, but didn't stick with it as it took 45 minutes longer than driving (30 minutes by car, 75 minutes by bus), and dropped me off a 15 minute walk from work. I could bike in about the same amount of time as taking the bus. A road accident meant that the bus could take even longer since it had to sit in the same traffic.

My current commute is much farther by miles, but shorter by time because I now live where I can take a train. Limited stop express trains are great. Full grade separation would be even better (to reduce delays due to accidents), but taking the train is faster than driving so I wouldn't even consider taking the car.
At this point I'm starting to wonder whether this isn't a competitor putting their investors money to work. It's otherwise utterly bizzare that someone would be so obsessive in damaging Linode. I really hope they make the details of the investigation public...
Indeed: https://github.com/50pop/nownownow.com
He never actually got a PhD:

> Prior to founding Lumosity, Michael was a neuroscience PhD student at Stanford University.

> Michael graduated from Princeton University with an A.B. in Psychology.
> display a warning if both Y-axes are the same units because there is little reason to do so

OK - let's see a line chart showing the correlation between average daily lunch cost and annual salary :)
The Secret to Ribs Is Already in the Kitchen: The Oven (2010)
Pied Piper?