skysight-inc/HackerNews huggingface dataset:
First and foremost, it monitors the real world, not the version control system. It sees things as they are, not as they're supposed to be. It detects manual, unversioned changes. It detects changes from automation, or from intrusion. It detects things that can't be versioned, like reboots or cert expirations.

Second, it is minimally invasive. You don't have to change your process in order to use it.

Third, it shows relationships between systems. An application isn't just source code. It's compiled binaries, OS patches, user security, databases, firewalls, message queues, apis, and more. Here's a common failure pattern - System A changes, System B breaks. System A might actually be perfectly fine and correct, and B as well, but the relationship between A and B is broken. Change the database schema, and the app can no longer read it. Change the dns, and the UI can no longer find the API. For any decently complex application, the potential sources of failure are in the thousands, and potential interactions effectively infinite. Now scale this up to the enterprise, to organizations so large that your app can be broken by departments you didn't know existed...
Thanks, that's very nice :)
I think it's only a matter of time until back-doors are (re)added. At some point, Russia, or India, or China, or Europe, or America will come up with some legislation that says "backdoor or GTFO" and a few vendors will decide to adhere, and others will be forced to follow so they don't miss out and that'll be that.
Total Recovery Pro 9 Serial Keygen Plus Crack Free Download
StatusPage (YC W13) is hiring rails engineers in Denver
Cover letter should be short: one or two sentences. One sentence is better than two.

Just briefly explain why this job interests you and give a hint of why you is a potential match.
Probably not, because most house locks are really crappy, so they're easily picked. Except they're almost never picked, because it's easier to just kick the door in.

I'm really not sure getting the bitting on a bunch of house keys would be of any use to burglars.
Build your brand; become a The Guy. It's less obsessive.

In other words, truly master something, then write about it well, to where you have a reputation. That's far more than darn near anyone does and you don't have those long nights while your baby is in a potentially fatal fever.
Upon return from a non-blocking I/O call the request is either failed or succeeded. Upon return from an async I/O call the request might additionally be in progress thus the fiber is required to wait for its completion. This case has little practical difference from a thread pool. Except with a thread pool it is the worker thread that notifies the fiber scheduler on I/O completion. With async I/O it is the kernel that notifies the application and then the application (from a signal handler or from an auxiliary thread) should propagate the notification to the fiber scheduler.
Fast multi-threaded logging for Python
Uh...it's obviously less bad.
What is Engineering?
https://news.ycombinator.com/item?id=10909528 earlier today, 20+ comments
Drupal and Wikipedia both celebrating 15 years today; jQuery 10 years earlier this week... All three projects that have affected my life in a very positive way, and have made the web a better place.

Thanks, Dries, Jimmy, and John!
I don't know. I didn't do the background check.
Thank you! This leans more towards the client side than the server side. It's certainly in the hackish and glitchy direction, and has no guarantees for success.

Qubes looks really interesting. I'd love to give it a try some time. I've just grown rather attached to my FreeBSD setup and this seemed like one of the ways I might be able to improve security on it.
>In the same way we don't pick people off the street and harvest their organs, so long as there are 2+ people on the donor pool who could use them.

Well ideally we should do that. If it really saved more people. It could be done entirely voluntarily, through a lottery. And it would be rational for everyone to sign up, since you are more likely to need an organ at some point in your life, then to lose the lottery.

The rest of your comment is just a misunderstanding of statistics. Out of decades of hundreds of phase 1 trials, very very few people have died. The risk is known. We also have invented many new drugs that have had many benefits and saved many lives, which can also be measured.
>However, by not standardizing, we lock out all sorts of non-mainstream clients form accessing content. Now that Flash is going to disappear entirely, that means no access to all sorts of content on Linux, unless it's standardized.

That is simply not true. Flash was on the way out with or with out EME, Chrome and IE was already doing it. With out EME they still would have moved forward with their implementations of Widevine and PlayReady respectively.

Netflix would have still switch to it, and Chrome on Linux would have still played Netflix.

EME did not result in "Content coming to Linux" and there is no guarantee it will continue.

It will be up to the individual CDM makers, in this case google, if they want to continue to include the binary blob on Linux. No different than Flash. If google chooses tomorrow to remove widevine from Chrome on Linux, there goes your Netflix and any future "HTML5 EME" enabled websites

Further many other "HTML5" Browsers can not play this content because the binary blob required is not there... making it non-interoperable with any true FOSS gnu/linux operating system. Firefox has to pay Adobe for a CDM Plugin under pressure from their less than idealist users...

"HTML5" as a standard should mean anyone implementing the spec is able to see all content built on the spec. Sadly with the inclusion of EME sites like Netflix can claim to be "HTML5" compliant while still preventing every FOSS HTML5 browser from viewing any content.

That is not a WIN for Standardization, or a WIN for interoperablity
Right on. Makes sense for YC and Sam to say "you need to grow fast" because they're investors, and understandably want return.

But for an entrepreneur, Sam's rationale is not yours. How much $$ do you need to make a happy living per year? Put that number down. The number of opportunities to achieve that goal is much much higher than unicorn opportunities.

TAKE NO INVESTMENT, and pursue that opportunity. Once you make that number/year, you will just think about working less, rather than making more money. And you'll be happier than most unicorn-founder who need to grow X% more next quarter because of their investors.

Yes: easy to say. But it is is much easier to do than building Facebook or Uber. A bit sad for Sam and YC, but much better for you.

Have been doing that for a while. It's working. No big press articles, no fame, but I am spending weeks skiing with family right now instead of growing faster. And making really good money.

Like many SMB founders, it's a throwaway account, not wanting to give away too much... Just a bit tired of reading of the "growth bible" as being the only way to be an entrepreneur.
He now knows 4 things not to do!
We're gonna finally catch all the bad guys.
Huh. I should read it again.
It's definitely a sequencing issue.

Glad you mention the "make something people want" motto :). I've recently realized that it's actually wrong. Well, backwards.

A more instructive formulation is: "find something people want and make it." Better to acknowledge the value of the search (and confidence in the finding) before encouraging the making.

I have seen many founders struggle to understand when the time to grow is. Pressure to raise deepens the struggle. On the topic of growth vs retention, of the hundreds of founders I have met or read about, I have been most inspired by the actions of Ooshma Garg (of Gobble). The quality of her service is second to none. She's the only founder I've ever met that has completely shut down her product because it wasn't good enough, only to reboot it to better quality, retention, sales, and growth than ever before.

In my experience (flawed and narrow as it is), the best way to course correct is to issue a recall. Treat bad advice like bad goods. Post the criteria where those affected will recognize themselves and make needed reparations.

As a community, we need to better celebrate founders that are doing it right. Not mock those of us still figuring it out.

If YC wants to get the word out about prioritizing product market fit above growth, it should elevate Ooshma's perspective, along with other founders that have made similar gut-wrenching decisions to invest heavily in retention while sacrificing weekly growth targets.

Overall I'm glad you wrote and posted the essay. And I appreciate any humility you may have felt while drafting it.
I've never heard of CLONE_NEWUSER before, it looks interesting. I don't think it's in FreeBSD.

My concern is that you can clearly browse and save files, so there is something that has access. Maybe it's much more secure than I thought, but I tend to be really skeptical towards programs of such length being perfectly secure.
That assumes that the manager doesn't insist that bugs of age get closed simply because long-open bugs make for ugly metrics.
CLONE_NEWUSER doesn't actually change what your user is outside of that container/namespace. You get to map exactly one outside user to exactly one inside user. On systems where unprivileged users are permitted to call it, you can map your host user account to exactly one account inside the namespace, of which root is basically the only useful choice. Any interactions between the namespace and the rest of the system continue to treat you as your original UID.

The original implementation of CLONE_NEWUSER did actually convert users to vectors, or at least namespace-user tuples, which would have allowed unprivileged users to use the kernel UID mechanism for actual privilege separation. But that was dropped, I believe mostly because it was too much churn to the rest of the kernel and thus too risky. The current approach means that code that just thinks about root-namespace users continues to do the right thing.

The primary thing Chromium's sandbox seems to gets out of CLONE_NEWUSER is the ability to call chroot without shipping a setuid binary.
Doesn't running on AWS make this decidedly and automatically not open-source infrastructure?

[edit]—typos
I definitely would, and would particularly use it as a way to spend a lot more time preparing myself to enter a PhD program.
> Another concern: what if they get hacked? Does everyone then have to change their locks?

Presumably they don't store your address with the key. It would be like losing a hotel keycard.
Ask HN: What book changed your life in 2015?
I find profits to be way more fulfilling than growth/sales. Growth does not increase my happiness. Pressure from third-party investors does not. Money in my pocket, free time, decision freedom does.
>Of course, now the big question: if we have a neural net big enough, and it works, can we simulate a human brain?

There are many possible neural networks. Most of them are not human brains.
Neither of them have marketplaces for custom made goods (for the most part at least compared to etsy) and both are in competition with each other to expand their marketplaces to as far as they can go.

Seems like it would be a good fit to me. I'm not sure how it ultimately gets integrated it (maybe it doesn't?).
I was also wondering about that. With El Capitan there was the big 'root' change. I guess they probably didn't break setuid, so this might still work.

I'm not sure about xraru working or not. If vncviewer runs on OS X, maybe? It might actually be a convenient way to run X programs in general.

Although if I add in any logic for auto-scaling, it'll likely break on OS X. But it'd be even more important because of the crazy retina resolutions.

xhyve, by the way, is an awesome hypervisor for OS X. It's pretty light. Not raru-light, but as light as you can get for proper hardware virtualization.
Brand, and cultural relevance?
Yes, and what percent of these killing are justified and/or in self defense? I'd wager the bulk. They have an inherently dangerous profession. Notice, I'm not saying it's ZERO either, but the risk is much lower than, say, black shootings.
CLONE_NEWUSER / user namespaces is Linux-specific, yes. (Though see my other comment.)

I believe the Chromium sandbox mostly applies to things like renderers, where you can just hand it a buffer and a bunch of inputs and it'll effectively contain things like HTML parser bugs or libpng buffer overflows. I'm not totally sure if browsing itself is sandboxed.
I'd think you'd get a better result from simulated annealing over GA here.
It could well be that the employees did that after management made decisions that they feel gutted the value of the company anyway.
Are there other instances of this happening in the secondary markets?
On a case by case basis you might have a point, but over time we have tons of statistics on how many drug trials fail and hurt people, vs succeed and save people. It would be relatively easy to calculate the risk/benefit objectively.

That's also an ideal use case for prediction markets, if you want to get really good predictions.

Also, I've heard this argument used before in other contexts. Do people really believe that because you can't make perfect predictions, you should default to inaction? That's just silly. You do the best with what you know and believe.

And if you really believe your predictions are wrong, then you can just adjust them accordingly and make them correct. If you don't believe that, then you obviously wouldn't find that argument convincing in the first place.
He mentioned researchers have tried simulating a life-form known to have a small number of neurons, like a thousand, and they can't get it to work yet"

302 to be precise - https://en.wikipedia.org/wiki/OpenWorm
Lead developer quits Bitcoin saying it 'has failed'
Yes. http://cafehayek.com/2011/05/bennis-v-michigan-and-the-awful... is also good.
casuals amirite
FDA outlines cybersecurity recommendations for medical device manufacturers
yeah, I agree, but I think a lot of us work in similar situations, where bug tracking exists, but there's such inundation of bugs that we can lose track of some.

I guess I have sympathy for the PayPal team in this case. They're working on an extremely large product, with a huge user-base. I would imagine it would be very easy for bugs like this to fall through the cracks even with a "process" in place
When a voter can't go into a phone store / Apple store and buy a shiny new thing: Boom, recall election.

Presumably assemblyman Titone knows this, and is expecting the bill to do nothing other than provide the usual security theatre. That, or he is dumb as a post. Could go either way :-)

I expect to see congressional level legislation like this very soon. That'll be significantly more interesting.
Sure thing.

Using the bitcoin client directly: the addmultisigaddress command. https://en.bitcoin.it/wiki/Multisignature

Using bitaddress.org, an "Open Source JavaScript Client-Side Bitcoin Wallet Generator". Makes use of Shamir's. https://bitaddress.org (save the page locally and run it while disconnected)

Using Shamir's directly. Split one private key into multiple points. https://bitcointalk.org/index.php?topic=393159.0

There is one nice thing about bitcoin multisig as opposed to running ssss on a private key. With multisig, you can generate three keypairs on three computers, then combine their public keys into a (say) 2-of-3 multisig. I'm pretty sure that using ssss would require the full-authority key to exist on a single computer at creation time, and it would be split afterwards, which is less secure.
Well I think we have to go with the author's interpretation. :) Thanks!
Unfortunately, we've seen a lot of situations where the "majority," at least of those who speak up, are (for example) opposed to heavily restrictive codes of conduct proposed by outside groups, yet the code is forced through anyway by project leaders. Majority rule seems to be valid only when the majority votes the "right" way.
There's also the issue, in ruby, that CoW doesn't really work due to the fact that the GC dirties all pages.
> I probably understand these concepts without knowing their official names.

It's been my observation that reading articles/posts written by Haskell programmers is a great way to be spend a fair amount of time being confused over things that you already understand, usually for this reason. In that sense, at the least, they're usually educational.

It's my suspicion that the most common path to becoming a Haskell programmer is to read too many of these sorts of things, to start using the terminology in your own writing and speech, then to find that no-one but Haskell programmers understand you anymore, leaving you no choice.
The Physics of Why the E-Cat’s Cold Fusion Claims Collapse (2011)
I am also cautious about learning new technologies and very carefully select what I actually learn.

Using proven techniques and tools makes experienced people more productive even if their raw mental abilities decline with age.

Learning and testing new technologies is expensive and most of the time leads nowhere.
Why is it scroll down to zoom in? The standard behavior is to scroll up to zoom in.
It is funny how "giving away a book" has changed meaning since then.

Today, "giving away 1 book" is easily understood as potentially indefinite copies of a single work, but the headline here refers to 123 million, physical copies of a much smaller amount of works.
In defence of the hamburger menu
Great article, took an neural network course while I was doing my graduate study long time ago and it might be time to resume that subject. the NN training then took a long time to be impractical for real use and now it should be much faster.
You are assuming a lot. I know how to write purely functional template code using the virtual DOM in JavaScript, or something like SXML in Scheme. You can do this without using a terrible mashup of XML and JavaScript.

> JSX is far more pleasant to read and write than the native function call syntax

No, it isn't. XML is both hard to read and write. It's for machines, not humans. Besides that, mixing two languages with two very different syntactic structures together is a recipe for disaster. And besides that, you now need an additional compilation step because it's not plain JavaScript. What works much better is something like Mithril's templating API, which is concise and pure JavaScript.
Show HN: Docker image with overlay networking
From looking around an Android device via ssh a long time ago (still in the "wow, linux on my phone" phase), I remember that all apps that are installed also have their own user installed. Access to various resources was then done via the groups that user is in. But of course then there is no real "main" user and multi-user wise it is back to Win95 level. I assume that has not changed much.

And back when the first commercial games for linux came out, I did not want to trust binary-only executables and added a user plus a script so I could run anything via passwordless sudo and then did and still do the same for my web-browsing. Since these have their own ~, the data is persistent, but for something you totally do not trust raru looks nice.

This of course requires root access, automatic /home/me/home2 (or /home/me_home2) generation with optional persistence and isolation might be a next step. But I have no idea what the current state of more fine-grained control via cgroups etc. is. It is probably more complex than the true and trusted method of just adding another user.

But what I still miss (and never really looked at) is an ACL or so system to make the game or webuser completely transparent/subordinate to my main user, meaning I can read, write and take ownership of any files of these sub-users but they have to obey standard permissions wrt. my files.
Very interesting. I wonder if something similar could happen today...digital or our paper, books have so much to compete with for peoples' attention.

I think we as a society could really use it.
I am still amazed that BaRT employees got away with striking. Many of them make $90k a year base!

Oh and this pathetic low-life still has a badge and a gun. https://www.washingtonpost.com/posteverything/wp/2014/08/19/...
Case in point. Social Security is OASDI - old age, survivors, and disability insurance. It's not a guaranteed income for the general population, it's meant to provide support to those incapable of working due to age or disability.
I've been using this for chrome: https://chrome.google.com/webstore/detail/hacker-news-collap...
And of course, criminals will certainly only purchase/steal device compliant with the law, because, you know, they want to obey the law.

And they won't install any apps or use any other means to hide their illegal goods/communications.

Just like the ones with violent felonies/intending to commit violent felonies will only lawfully acquire guns to commit violent felonies.

Can someone explain please what I'm not seeing? I give you our politicians are sometimes not the smartest, but it doesn't take even an average IQ to see the logical failure here. That being the case, these elected officials must know that this won't solve the problem.

So what is their ulterior motive in spending so much time chasing after a law that will do very little to stop real crime? Just so they can look like they're doing 'something?'
"This is not entirely true, as there are spiking neuron nets and neuromorphic chips (like IBM's TrueNorth) that emulate what we have so far understood about how neurons operate."

How is this related to the neural networks we are discussing? (deep ANNs?) As far as I know, the ANN topic in machine learning, apart from its origins, is completely unrelated to the simulation of biological neural network models: https://en.wikipedia.org/wiki/Nervous_system_network_models

They are often confused because of the name and because ANNs did begin as extremely simplified models of biological neural networks, but the machine learning concept that is setting all the records in vision / speech recognition serves no purpose as a model of a biological neural network.
While I like -fsanitize=address, the project I spend most of my time on may have tens of thousands of lightweight threads, which makes it a non-starter. Valgrind works fine on it (Albeit at a significant performance impact).
As much as NYC people want it to happen, they don't have the universities or the concentration of talent that Boston does. The numbers prove reality http://www.entrepreneur.com/article/228709
Bitbucket or just host it on your remote and ssh in
Philadelphia: Thinking differently about data
OP here. I'm a pretty big CNC enthusiast and part nesting is a problem I face regularly. The software that does this is all pretty expensive and I couldn't find an open source implementation, so I decided to write it myself.

Try it out and let me know if you have any feedback
Add Your Own Egg
Anyone else read this article as an advertisement of Gokul Rajaram to other companies?
> perks allow [hiring] more cheaply than wage increases

That sounds like the kind of thing some bored economist must have done some kind study on at some point. I'm too lazy to look for it, so maybe someone else can volunteer. I'll just say that sounds very likely to be true.
I first encountered Jimbo back in the 80's when he ran the Moderated Discussion of Objectivist Philosophy (MDOP), an Objectivist mailing list that featured brilliant philosophical discussions among the stars of the Objectivist community. Jimbo's contributions were consistently excellent as well. [Anyone know if there's an archive anywhere?]

It was quite a surprise when he turned up years later in an entirely different context as a founder of Wikipedia - though I'm not surprised he did something big. His charisma showed in his MDOP contributions and he always seemed destined for something big. Congrats Jimbo, and all the other people who have made Wikipedia, for this amazing asset to humanity.
Dope Books