skysight-inc/HackerNews huggingface dataset:
I think access to data is key. One of the hardest challenges is dealing -- in an empirical manner -- with paper documents, or anything that doesn't come in a spreadsheet...which, until relatively recently, was the norm of information distribution.

But I think we (as a society) are just beginning to make use of data, in terms of analysis and general computational thinking. To go back to the domain of journalism...Aron Pilhofer, who heads the interactive news team at the New York Times, said that in "one day...we can teach you the skills that if mastered would allow you to do 80 percent of all the computer-assisted reporting that has ever been done" (http://knight.stanford.edu/life-fellow/2012/times-editor-say...)...I think this is still the case.

As an example, you don't have to go back much further than last year's Public Service Pulitzer...probably my favorite winner in modern times: http://www.pulitzer.org/citation/2013-Public-Service

The reporters took a sensational story (off-duty cops being caught on YouTube egregiously breaking the speed limit) and opted to do an empirical analysis. But of course, what they were trying to find -- cops who broke the law by speeding -- was inherently non-existent, in terms of public records (because it is the cops who determine whether the law is broken). So instead, the reporters requested toll booth records, which recorded the passing through of each cop car. Taking distance divided by time, they were able to prove so convincingly how egregious the abuse was that Florida police stations pretty much rolled over and immediately repented.

Besides whatever database they used to hold the data, the analysis here is literally elementary level. This is not to say that the reporters' had it easy (they still had to do all the footwork, interviews, confrontations, and fact-checking, among other things), but it just goes to show you how many important stories are out there, in every jurisdiction, that only need someone who cares enough to do some counting and arithmetic. I kind of love the Public Service awards because of how they recognize these relatively non-sexy, but incredibly important stories done by determined and clever journalists.
This kind of abuse is also available in Python!

In [3]:
class TheObjectThatIsEqualToAnything(object):
def __eq__(self, other):
return True

In [4]:
x = TheObjectThatIsEqualToAnything()

In [6]:
x == 3 and x == 5
Out [6]:
True
No we don't. Even though we keep finding ways (so far) to make new sources affordable, the cost still goes up.
I would think that it was traced via bitcoin, not pgp.
Mind Over Milkshake: How Your Thoughts Fool Your Stomach
My understanding is that, in some ways, it gives them an advantage since many countries in the EU and elsewhere have mandatory data retention laws. The US does not.

They also go out of their way to accept anonymous payment sources, something most VPN providers don't bother with.
Actually, I'm starting to want to read this book, if only to see how far down the rabbit hole goes. Depending on what I find, I may want to demolish it. I don't care if the authors are gods, this glimpse of their work does not look good.
I love how this integrates with Photosynth. It can also use videos to create a panorama and appears to have lots of useful options.

MS Research projects pages are a real treasure trove of useful (and generally free) tools.
haha! what does that even mean - that's just typical religious mumbo jumbo. It's by relying in "HIM" that we have the blind spot. If "He" is so capable wouldn't he have thought of a better way to connect the optic nerve, like evolution did in other species? I know I can't win an argument using logic with a zealot, but seriously, let's stop with the "trust in him" claptrap.
When it happens to a high-profile figure, people grapple with the issues in the public sphere. It raises awareness.
Why would you envy vim users?

Larry Tesler would cry if he knew of this strange vim-obsession that has been creeping up all over the interwebz.

I use Emacs and IntelliJ, both modeless editors, and I've never understood the obsession with vim, but I'll be happy if someone could enlighten me.
@srean - can you provide a link to the PDP support for coroutines? I would like to read more.
Matt, my biggest problem with CloudFlare by a country mile is the ambulance chasing you guys do in your marketing and your penchant for inserting yourself in the story when you're not even involved. Here, you've done it quite obviously: you got predisclosure and you took the marketing opportunity at the expense of security on the public Internet. You were wrong. But you were the worst kind of wrong: you were wrong in a hurry to get your name in front of everybody first. If you had waited, you wouldn't have been wrong, and we would have been able to answer the question regarding keys without the disinformation.

It really pissed me off because I developed the ability to get keys long before you even wrote the post. I commented about it here several days before you wrote the post[1]. After your blog post, I was accused of fabricating the entire story because you said keys were unobtainable. I cannot, legally, release code without opening myself up to legal ramifications for reasons I won't get into here. Then, after your post, people I've known for a long time accused me of making the entire thing up for a "shot at glory." Meanwhile, I had to explain that your blog post was not definitive to multiple people who were reassured by the false security.

I brought your company's marketing strategy up with you before on HN. Remember when your company jumped on nytimes.com getting owned at the registrar[0]? And you wrote a hurried postmortem of events (I'm assuming, from the typos) without even consulting the affected vendor, then went so far as to speculate on what happened at the affected vendor, and made sure your "postmortem" got on top of HN first?

> An e-mail obtained by Matther [sic] Key, an independant [sic] journalist, indicates that the hackers used a MelbourneIT domain reseller account as part of the attack. While we are only speculating at this point, it's possible that there was a vulnerability in Melbourne IT's reseller systems that allowed a privilege escalation.

You replied here on HN with "no good deed goes unpunished" after I expressed my displeasure with your company's behavior in that scenario, and you didn't really address my points. You basically pointed to the CTO of NYT's praise of your company as evidence enough that you did the right thing. You took advantage of the marketing opportunity (which is fine, I don't fault you) at the expense of allowing the affected vendor to even draft a postmortem or contact customers in a timely fashion (I fault you for that).

We get it. You want to position CloudFlare as a superhero company, capable of fixing the Internet problems that the rest of us cannot handle. However, your marketing strategy has alienated me from ever using your services, and I am not alone in that opinion. Please, rethink that strategy. Focus on the product instead of fixing what you perceive to be a broken Internet that only you can fix. That's the obvious tone I get from your marketing and choices of venue.

[0]: http://blog.cloudflare.com/details-behind-todays-internet-ha...

[1]: https://news.ycombinator.com/item?id=7551915
The full timeline doesn't make big tech companies look particularly great. Heartbleed was a bug that came in with a questionable implementation of a questionable feature. It sailed through standards bodies and OpenSSL itself. A sensible explanation is that these are underfunded, understaffed efforts.

But next, the feature went live on the servers of more or less everyone, including Google and Yahoo and Amazon. People who employ and, presumably, well-compensate many experts in security and SSL implementations. Still, the code marched on, unnoticed, undisabled, deployed. How did that happen?
I wonder how one should proceed (if not working for any of this big tech companies) when one discover as critical bug as heartbleed?
> It happens routinely.

I think that still leaves open the question of how likely it is, or perhaps the question is better phrased as whether it is due to chance or not.

It is extremely unlikely to be due to chance in this case. It was out for years, but discovered independently within days of each other.

One possibility is that it was discovered independently many times, but we only find out about it after someone actually goes public. At that point, those finding it earlier either never wanted to mention publicly that they found it (or they already would have), or even if they want to, they would be admitting to finding it earlier but not disclosing, so they'd look bad.

That leaves others finding it slightly after the group that goes public - soon enough that it wasn't public yet, so they have evidence that they actually did find it independently. That would lead to exactly the result we see here, in fact. But this does imply that there were, very likely, multiple other groups that found this earlier but never went public.

The only other option is that it wasn't random, but some event led to both discoveries. Perhaps a hint was around, a new method of finding vulnerabilities, or anything at all that could nudge people's minds in that direction. That option is much less worrying, but very hard to prove.
The main benefit is it's an easy to update, minimal OS. And docker's already set up for you and updated regularly.

Our cloud-config implementation is designed so that you can use the same config to set up a new machine to match an existing one, and have it automatically join the cluster. Start with 3 machines and scale up as you need.

Learning systemd is one bump you'll have to get over, but all of the major distros will be using it, so they're is no better time to try it out.
It would be much easier to trace him via the blockchain than break PGP.

Bitcoin is pseduoanonymous, it is possible to track coins.
They sure do. You can also go to reportaproblem.apple.com to request a refund, for the record.
you can make decent flat bread with flour and water
I think if you reread my comment closely, you'll see that it describes a scenario that is spookily similar to Heartbleed: same impact, same latent bug (presumably in the code for many years, maybe even longer than TLS heartbeats), and co-discovery not in a matter of days but hours.

Sorry, there's probably nothing interesting happening here, except for coincidence.
He was arrested by admitting to the crime. Anyone could have done that accidentally, here is the source: http://www.cryptocoinsnews.com/news/charlie-shrem-did-nothin...
Fortunately, this case is much more about Charlie Shrem and his penchant for violating laws than Bitcoin itself. I think this guy - who now refers to himself as "Charlie van Bitcoin" - just doesn't get it. There are laws out there, and he doesn't seem to want to follow them. Here's an example:

He is out on bail on this case right now. As someone out on bail for a federal felony, he is prohibited from using or possessing deadly weapons (knives, guns etc.). There are people in his position that have found themselves in trouble over kitchen knives. Yet Charlie publicly posted yesterday that he is the proud new owner of a World War II Nazi Dagger.

https://bitcointalk.org/index.php?topic=566300.msg6202174#ms...

He will eventually learn, but apparently he hasn't yet.
Given the breadth of information covered, I think you did a remarkable job on providing one of the better, succinct and balanced introductions on the Search Engine Optimization chapter (#23). If I could make one suggestion - your alternate text attribute markup for the images is non-descriptive at best.
I checked 3 compilers: icc 14, gcc 4.8, and clang 3.3. Clang is the only one which optimized the memset away.
The even bigger deal about methane hydrate is its release from the formations as climate warms (and it's a feedback loop) - https://en.wikipedia.org/wiki/Clathrate_gun_hypothesis
Yes, it is spookily similar, I agree 100% (I did read it carefully ;)

What I disagree with is that one event happening means that another event very similar to it is likely in a statistical sense.

Of course, it is an argument that supports that to some extent. But it is fairly weak support, when on the other hand statistics strongly imply the opposite.
Hi Tim, ToneDen looks really cool. I love the look of the live-frequency line.

I wish to incorporate aspects of the player on (http://spawnsong.com), will this work for non-soundcloud sources of music?

Do you have an e-mail that I can contact you at?
wow, I never knew you could get a vps for that cheap, thanks.
I'm sorry, but as a long-time sufferer, I feel compelled to disagree with this viewpoint wherever I see it, to represent people like me. I've been suicidal and depressed on and off for about 20 years. From in here, it doesn't seem anything like an illness at all. The flu is an illness. This is having lived through an absurd number of absurd events, emotionally draining and also traumatic in the long-term. It's having been abused. It's having exhausted yourself pouring all the energy you have into being your best, excelling, achieving, pleasing everyone, but having one dream after another expectation shattered, and having to learn a new framework for living with it. It's cumulative rejection. It's guilt over things you can never undo. It's finding no pleasure in life, only monotony, the grind, suffering, disappointment, and loneliness. It's wondering what's wrong with you that everyone you know got married, have kids, own homes, advance in their careers, buy nicer cars, but your life is still just like a single college student's.

It's not quite my brain, and it's not quite my mind. It's my life, which in a sense is my mind. Which may or may not be my brain. I think that current psychiatry is confused about which level of abstraction is the one to target - not too surprising, since it's circular, almost strange-loopy. Also, people, even most professionals, don't really know what to do or say when the problem really is your life.
Except ELS applies only to RHEL3/4 (which gets only 7 years of support otherwise) and also covers a limited amount of packages.
Coincidence seems very unlikely, but the other explanations you suggest do seem plausible. Hopefully it's one of those, because otherwise given it's unlikely, it means it was most likely discovered earlier multiple times but not disclosed.
I don't see how that's material to whether or not he was competing with his employer.
I think the idea is that everyone would get the info at the exact same instant. It also allows everyone to be "at their computer" ready to implement the fix.

It would mitigate the possibility of it leaking and getting exploited by someone.
I agree with you. It reminds me of an interview about Steve Jobs.
I don't have the link, but one of his executives was offered a BOD position in another company. Upon asking Jobs if he can take the board seat, Jobs told him he was barely making it at Apple as is...

I also don't buy the example of Musk and others, I think we have context as to how much better each of these companies would have run if they had put 110% of their efforts into just one.
My Childhood in an Apocalyptic Cult
Big tech companies, small ones, and OSS folks, all write bugs. How does it "not look particularly great" to do something that literally every person writing software does. Wait, not even to do it. To miss the error in an obscure change in a backwater part of OpenSSL that no one uses. It does not strike me as likely that these companies review every change to every possible piece of sensitive software. The volume of work would be far too large.
We don't know how much oil exists,but we do know it is finite.

The sun's energy will out last us all, millions of times over. Plants have it figured out. We should ask them.

Plus what happens when we are ready to leave Earth? Surely we'll need a way to feed off of the stars then anyway, so why not start now.
And here we all are reading this post during work hours. My god, the amount of productivity lost because of that simple question in chat!
The future of software is the aggregate of teenagers the world over messing around with Linux, Arduino, etc.

Without entry-level jobs they're just going to be distro-hoppers who never get a foot in to industry.
Here's the Reddit thread;

http://www.reddit.com/r/science/comments/22qhob/laboratorygr...
Don't be too envious, Sublime Text is a decent platform. Easy to install plugins on the fly from inside the editor, reloads settings on the fly, and you have a Vim (vintage) mode so you can enjoy the awesomeness that is Vim AND Sublime.
I would suggest there are many developers who have the potential to be 10x, but are constrained by their environment.

How many of you have suggested a course of action that is plain to you as a developer, but is shot down by non-technical management? Are you allowed to solve problems with new tools and languages or must you ensure compatibility with everything written at the company since 1970? Are you busy writing a great service, or are you expected to integrate with some clunky service that will limit your work in the future because using a third party is expected to be faster and cheaper?

I believe Jeff Dean in charge of healthcare.gov would have failed. Not because he's not great. It's just certain environments are not conducive to producing 10x results.
Parallax Beyond a Kiloparsec from the Hubble Space Telescope
I didn't mean the engines were on the whole way down. But if they aren't pointing in the right direction to begin with, you need to flip the entire 70m-long stage around somewhere in the atmosphere. Even at terminal velocity it's moving pretty fast, and I doubt it will survive going sideways at 100m/s through the air, never mind that you need some thrusters that can even develop enough force to flip it around.

That animation for the second stage reentry is an animation. Recovering the second stage will be extremely difficult and, if it is ever done successfully, I don't think it'll involve doing a 180 flip in the lower atmosphere.
Definitely! I can point you to how we are doing it on our player.

You can reach me at tim@toneden.io
Mixture of Webaudio API with D3 is awesome , liked the themes as well .. good work :)
What if the sky rained donuts!
I don't understand. Isn't this what Dropbox Sync API for?
A lot of this just looks to be lacking const correctness. If you declared most of the mutable types const (and the use cases for a non-const unique_ptr are few) you can avoid most of these issues.

I think it is a valid criticism of the language that not all non-primitive types aren't implicitly const, though. But you could never implement that without colossal backwards compatibility breakage. Which I guess is fine, since you could just keep a code base an std= behind until you fixed it.

> Use after move: obvious. Undefined behavior.

This I don't have an answer to though. I've always disliked how this isn't a compiler error.
This is another great point. When the normal salary is 120k at 30 years old, housing is usually way more expensive. (NYC, for example)
I already spend a lot of time talking to early stage startups (it's really important that we understand them well); this seemed like a good way to formalize that in a way that helps them too.

(That is, my hope is that this is good for Stripe, for YC, and for the startups.)

In general, I'm very leery of distracting time commitments, and I don't sit on any boards or anything like that. I think this is a (pretty rare) example of one that makes sense for all parties.
The "mistake" you are making is that you assume Tesla has "invented" an electric motor, so rugged that it can withstand that riggers of being inside a consumer vehicle on the open road with a novice operator, in various environmental conditions, that is a fraction of the cost of similarly powered electric motors that operate in static environments, such as a factory floor, with experienced operators and fixed maintenance schedules? Wow.. I have a bridge to sell you...
And that's saving the lemon for dessert!
Hey Mate, may I ask since when you started saving and if you don't mind disclosing how you got upto 450K ? I am database developer, 28 and have only accumulated 60K.
If you don't mind asking what strategy you use ? Thnx.
That's a myth, especially for salaried people.

Companies aren't going to lose a good hire over a reasonable term change. I've heard the "this is non-negotiable", but when you get up to walk away, it becomes negotiable, as long as what you're asking for is reasonable.
It may be PR, but if so, it's the best kind -- there's a lesson to reflect on here.

There are limits to automation (and, more generally, any reduction of knowledge/craft to process). As you depend more on robots (literal or figurative) to execute process, over time you're likely losing a body of knowledgable/craft-capable practitioners. You can automate worker function, but until we have AI, not their perspective and the potential expertise that comes with engaging with a task over time. And you concentrate the responsibility for improvement in a smaller number of hands.

That doesn't mean there aren't also yields to automation -- sometimes big ones. Just means there are limits too.

By way of comparison... it's great that many software developers are much more productive in Ruby or Python or whatever than they would be in C or assembly. But when the time comes where you have to make a key optimization, if you don't have a "god" around who can be productive at a lower level, you may be bound to a sub-optimal approach (you might not even know about the potential optimizations).
That just seems too anal retentive, though, doesn't it?
Not that this article isn't cool and valuable, but the fact that it had a scheduler at all puts it light years ahead of this in being-a-kernel.
> What I disagree with is that one event happening means that another event very similar to it is likely in a statistical sense.

Why? It makes perfect sense to me that, when one type of vulnerability is discovered, many more of same type will be discovered very soon thereafter. You have to consider that vulnerability discoveries don't happen in a vacuum. There's a near-infinite number of attack routes that one could investigate, but which one you're looking at now is a product of the environment you operate in.

For example, let's say you're investigating a web server. Then, some security researcher demonstrates a flaw in an image codec where even using "safe" memory copy functions in C leads to a vulnerability if tainted values are passed in for the size parameters. You think, "Hmm...I'm not decoding images, but web servers do copy memory. I should check to see if any memory copy operations are using tainted values." Bam! You discover Heartbleed...but do you honestly think you'd be the only researcher working on web servers that saw the image codec demo and made that connection? Unlikely.
I think he was selling btc for other very traceable and identity-linked forms of digital money (paypal, liberty reserve, western union, something like that). The issue was that he was operating as a money processor without following the mandatory guidelines that try to prevent laundering, etc. You can google the earlier arrest for more information on it, there are some juicy transcripts.