skysight-inc/HackerNews huggingface dataset:
There are very many add ons and extensions and things available for HN.

There's bound to be a thread filtering add on for whatever browser you're using.
Comcast’s “Six Strikes” Email With Infringement Details Surfaces
Encourage -- allow and enable -- kids to participate in the real world around them, whether that's farming, or computer work, or whatever else.

Shoving kids into artificial situations does everyone a disservice.

P.S. Keep them safe, by all means -- reasonably safe, not to the point of disabling learning. But don't keep them ignorant, or perhaps worse, mis-informed.
> This response indicates lack of experience to me.
I could say the same in return. I've worked in a few data centres and they've all put redundancy at the forefront of their design. (even to the point of having multiple physical fibre paths for fail over).

> No systems are immune to failure. No matter how much redundancy you have

You have that backwards. No systems are immune to failure, which is why you have redundancy.

> chances are you have interdependencies you did not anticipate, and sooner or later run into failure scenarios that violate your expectations.

If the dependencies haven't been anticipated then someone isn't doing their job right. There's a reason why incident response / disaster recovery / business continuity plans are written. It should be someone's job to think up every "what if" scenario ranging from each and every bit of kit dying, all your staff winning the lottery and walking out the next day and even terrorist attacks. I've even had to account for what would happen if nukes were dropped on the city where our main data center was housed (though the answer to that was a simple one: nobody would care that our site went offline). It might sound clichéd, but people get paid to expect the unexpected and work out how to maintain business continuity.

> It's very well possible that Cloudflare messed up here, but to claim so categorically that "human error is unacceptable" is a bit of a joke. We build systems to withstand the risks we know about, and guess at some we don't.

This was their infrastructure failing. If you own and maintain the infrastructure then you have no excuse not to work out what might happen if each and every part of that infrastructure failed. (trust me, I have had to do this in my last two jobs - despite your accusations of my "lack of experience" ;) ).

> But the number of possible failure scenarios we don't understand properly is pretty much infinite.

You're confusing cause and effect. The number of different causes for failure is infinite. But the effect is finite. For example: a server could crash for any number of reasons (hardware, software, user error, and all the different ways within those categories), but the end result is the same; the server has crashed. Thus what you do is plan for situations when different services fail (staff do not turn up for work, your domain name services stop responding, etc) and plan some kind of redundancy around that, thus giving a little more breathing time for engineers to fix the issue and with the minimum possible disruption to your users. As Cloudflare had to resort to Twitter to update their users, they completely failed every possible aspect of such planning. And given the high profile sites that depend on Cloudflare, they have no excuses.

If this happened in any of the other companies I worked for, I'd genuinely be fearful for my job as a crash of that magnitude would me that I hadn't done my job properly.
The flip side is, farmers in developed western countries have the option of selling their land to agribusiness and sending their children off to do something less godawful.

Economists tell us the "developing countries" will never actually develop until rich countries stop subsidizing their agriculture. Those folks in developing countries are stuck.
I'm sure there's a lot of information that could paint a more complete picture, but here's a start.

According to NASA[1], a shuttle launch cost $450 million on average. Their contract with SpaceX covers 12 launches for $1.6 billion[2], or roughly $133 million per launch. SpaceX also received $75 million from NASA to develop a crewed version of the Dragon capsule.

I'm sure NASA has made other payments to SpaceX over the years, but even if those payments totaled a couple billion it's still cheaper than 12 Shuttle launches just to supply the ISS.

According to Wikipedia[3], the Falcon 9 rocket itself costs half as much as an Atlas V.

[1] http://www.nasa.gov/centers/kennedy/about/information/shuttl...

[2] http://www.space.com/13012-nasa-unveils-private-space-taxi-c...

[3] http://en.wikipedia.org/wiki/Comparison_of_orbital_launch_sy...
You are probably referring to the way the word is used in a computer programming context. I was talking about this:

"A preemptive war is a war that is commenced in an attempt to repel or defeat a perceived offensive or invasion, or to gain a strategic advantage in an impending (allegedly unavoidable) war before that threat materializes."
The paperback is just a printout of the online (living?) version that esr still maintains.
A lot of big routers run (or have the option to run) on DC power, too, which makes it harder. Much of the remote power control gear out there is AC
Yeah, I've seen a lot of great options for OOB access:
1) At carrier hotels, wifi (heh)
2) Cellular modems (ideal for branch offices; a lot of datacenters have bad cell coverage inside the racks/cabinets/floor though)
3) Cross-connect (in places with free/cheap cross connects) to someone you don't use for transit. Can be mutual
4) Some facilities give you an OOB network, although this often has issues (if you buy transit from them, it's possible your outage is due to something going wrong with them, and it might take out your OOB access)

I'm looking at the Verizon Private-IP thing (an outsourced private network over Verizon's cell infrastructure) for OOB management of lots of CPE; the cost per device per month is low, and then you pay for bandwidth across all of them. Makes initial provisioning easier, plus ongoing monitoring/maintenance.
True, but getting everyone on signed/encrypted email is a much more massive undertaking than just sending an https link.

To your point, as long as straight SMTP is involved, there will always be a gaping hole. But, sending https links is a very cheap way to prevent making the hole even bigger.

Anyway, all of this underscores the fact that virtually nothing that Evernote did was secure. But, most companies probably wouldn't have done much better.
> You don't get interrupt handlers, for one thing

Thanks.
Apparently it uses CSS rotate() for the rendering. I'll have to remember that trick.
Explore North Korea for 2050 Euros
2050 Euros for 5 days (all included: hotel, meals, train, a personal "government" guide...). Departs from China...
I wish I did things this way. In college I formed a lot of uneducated opinions (why would you ever not have a completely normalized database? That's dumb) that only thanks to my extensive coop experience did I retrospectively see the value of.
Contrary to what everyone here seems to think, I've actually used (something like) RoR (Django, to be specific.) Although frameworks simplify the process quite a bit, there's still a lot of stuff that doesn't really need a "proper developer" to do, imho. Again, oversimplifying here, but tbh, aren't a lot of these applications basically "glorified spreadsheets"?

Anyway, I guess I got the title for the post wrong. The main point here is that:

1. CRUD is repetitive.

2. CRUD is boring.

3. Why don't we solve better, harder problems and leave CRUD to the non-programmers?
I’m not a programmer but have witnessed – and mediated - a lot of these arguments. Some are very esoteric while others are pretty practical. But some programmers forget that when you’re trying to implement a “large” project (relatively large user base and relatively long expected life), the programming language is just a tool. You can tinker forever with a technologically superior language – and enjoy the intellectual challenge – and never implement your project. Or you can settle for a less sophisticated language and implement your project in a reasonable amount of time, though not as elegantly as you might like.
Work Comes First
My proposal is ... perhaps reducing their ability to post replies for a period of time.

This kind of flame retardant has been built in since 2009:

We also have some new features to prevent flamewars. The most conspicuous is an exponential delay before reply links appear on deeply nested comments. We'd noticed these were rarely the most interesting comments on the site. We're hoping that instead of killing stupid arguments, it will be sufficient to apply gradually increasing drag to them.

http://ycombinator.com/newsnews.html
I've been programming for over ten years and the only situation under which I need a debugger is when I'm working with a language that allows segmentation faults.

Maybe debuggers are useful to you in other scenarios, but they are by no means necessary. You don't need to be inflammatory about it.
You'd be amazed how often "standard" network protocols behave subtly different between vendors. You have to exhaustively test interoperability for every single feature and config option if you want assurance that it isn't going to break in some bizarre way.
TL;DR: There is no reasoning or logic in this article, only a rationalisation that because a site works on a desktop browser on a 1900x1080 screen, it should work just as well on a 1024 x 768 screen, and if the site doesn't work the same it must be the browser at fault.
The tl/dr; version of your post could be summed up:

"Ban commenters who have a style different than what I like"

Since that's the case, I don't really see a reason to continue.

Or... the flip side is that you've discovered something meaningful but, in the attempt to "be nice", you've left out critical information that I apparently need to see your post as anything other than the tl/dr; version. Name names or cite examples and maybe I can 'see' what you're talking about.
In England:

A person can go to their GP to get treatment, and the GP will either treat (access to short form talking therapies and some medications), or refer on to a community team.

The community team provides access to heavier duty meds; long form talking therapies; ECT; hospitalisation; a variety of different clinicians, etc etc.

Note that treatment can be forced, and against the patient's wishes. Note also that there's the possibility of community treatment orders. These mean that a person living in the community (not in hospital or prison) could also be forced to take medication regularly.

All of this is free at the point of delivery. (With the exception of prescriptions, but there are so many exemptions they're free to most people.)

And let's not forget that people with mental illness are far more likely to be the victims of violent crime, not the perpetrator.
True that. I often think of how many services ask for the same info as "security questions". By definition, if there's a "standard" set of such questions, it's not secure.
Recording in a public place in generally legal, but recording a private conversation, like a business meeting, is more complex. The laws vary depending on state (in the U.S.), and some states require the consent of all participants. I'm not sure that I'd want to wear a device that would expose me to felony charges if I inadvertently recorded some sensitive conversation that I didn't have permission to record.

Also, private property owners (like store owners) can eject you for trying to record video on their premises. There are some places where recording devices will never be welcome, such as movie theaters, sporting events and workplaces that deal with confidential information (e.g., a doctor's or lawyer's office, or even a start-up company whose product wasn't yet announced).

And I'm pretty sure that even Google wouldn't be happy if all their employees wore these to work every day. Would your work colleagues or managers speak candidly with you if they knew that their every word might be getting recorded?
Well-known Google SRE motto: "hope is not a strategy".

See also R.Reagan: "trust, but verify"
Most kids don't actually read Milton or Bradbury in college when it's assigned. On the other hand, people who do want to read classics can do so while also being a software developer.

I'm all for enrichment, and I did enrich myself in college, but no more than I do on my own now that I'm in the real world.

(Edit: Also, I didn't learn how to really party until after college =)
This illustrates the problem rather well. The case where I ready my weapon in preparation for violence vs. when I use my weapon to stop an anticipated threat are both preemptive uses of the weapon.

The definition is unclear and one researcher may use one definition while another might use the other. Both cases are distinct, however. In one case, I am actually preemptively using the weapon and in the other, I am merely carrying it in anticipation of use.

Part of the article is a discussion of the fact that such definitions are muddied and lost as statistics are looked at.
I didn't follow everything in detail this time. What was with that problem they were talking about?
Marc Andreessen critiques Warren Buffet's letter to shareholders on Rap Genius
"But, the reality of the situation is that all of this gear is marked up well into the thousands of percent."

You seem to be confusing hardware with software. Juniper's gross margin was 64.25% for the quarter ending Dec. 31, 2012, and in that ballpark for previous quarters back to inception.
It probably means what you think: urine, blood, saliva, fecal matter... Whatever a scientist or doctor on the ground might need to analyze.
I see more problems with mobs of stupid comments attacking one person. Should that person let them alone? Probably, but explaining something to several people who are wrong is a good thing for each person receiving the reply and to a degree third party readers.

After reading some egregiously bad posts on here in a couple threads I'm thinking that a Chrome extension to collapse threads started by certain people, user's choice, is the best idea. That way if you and I think different people are the problem in a thread, we can each hide what we'd rather not see.
> I run a number of DNS servers myself. And yes, it was "fairly unforgivable" to mess that part up.

So then you basically agree with my point <_<

> But what I was addressing was the blanket claim that human error is unacceptable. Anyone who runs a setup much larger than a calculator will deal with human errors - whether actual operational errors or human inability to engineer for resilience against all possible but unlikely scenarios - on a regular basis.

You're twisting my words and taking them out of context. I was saying that human error is an unacceptable excuse for the entire stack of a company the size of Cloudflare going off line. And I was saying that because redundancy systems should act as a "safety net" so that administrators can make human errors. I've lost count of the number of dumb mistakes I've made over the years, but each time I've been able to switch to a back up system while I've worked towards undoing my cock up. And you said yourself that a complete DNS outage was unacceptable, so clearly you and I are more or less on the same page regarding this.
I agree Windows is an interesting target. Best thing is to target multiple platforms at the same time though. Many people might think this is a lot of work, but I don't think this is necessarily true.

I've recently began rewriting our framework to Mono / C# and so far it's been a good experience. From what I've read I should be able to have at least 50% shared code across platforms, but some type of apps can perform even better. Games written with MonoGame (open-source version of Microsoft's XNA framework) might be able to share over 90% of the code between iOS / Android / Windows Phone apps. Also the Ubuntu phone will be a possible target in the coming year.

So yeah, I agree Windows is an interesting target, but you don't want to miss out on the other markets. Mono is the best solution to have a performant app for most platforms while at the same time offering a native UI experience.
"or the rule itself was in error"

I thought that the rule was in error: I couldn't read the rule clearly on the screen, but it seemed, or I guessed, that the problem with the rule was that the "humans" omitted the decimal points and, thus, asked for blocking packets with lengths 1000 larger than intended. The Juniper software got sick, i.e., allocated too much memory, only because it was trying to swallow working with such absurdly large packet sizes. But, then, I couldn't clearly read the screen capture with the rule.
The capsule's thrusters had a blockage which prevented them from maneuvering and deploying the solar panels. They managed to clear the blockage just fine.
Alan Turing's reading list (with readable links)
So what do you want to do about the innocent people dying from drunk drivers?
If it's any consolation, I'm not taking about intervals, I'm talking (mostly) about people who are fooling themselves utterly. There are more than a few folks out there who never get above a good walking clip (and every bit of clothing in the kit is always sparkling like new with conspicuously-displayed brands).
That does look pretty gross, thanks for sharing. Any other ones stick out in your mind? I've been happy using Go against postgres, but haven't had a significant enough load to run into real problems yet.
SPDY's colon headers
C is a language I'd like to see make a reappearance in CS curricula. It's great that most programmers today don't have to deal with memory management and pointers, but I think a CS degree should leave the student with a basic grasp of the full stack of programming paradigms.

I think a nice approach would be to start off with a high-level, functional language like Haskell or Scheme, and then move down the ladder of abstraction in subsequent courses, culminating in a hardcore C (or maybe even assembly) course.
Great article. I think this is really the only way to help people learn real world skills. So many college grads have a lot of theory but no real world practice.

It also helps the people who take apprentices on, as teaching is learning.
What stuff are you thinking of specifically? The biggest web time waster to me is the culture of "every site must look unique". Tools like bootstrap mitigate that to an extent, but using them heavily makes your product look amateurish. On the other hand, your application looks and feels amateurish if you don't use Cocoa, or WPF, or Qt/Gtk natively.
Responsive design with Clay, the Haskell CSS preprocesor
Having a tiny bit of JS and having no JS at all is worlds apart. I edited the DOM in my inspector to try to add arrows and change percentages, but nothing happened after I injected new elements.

Had this been entirely in CSS, it would have automatically rendered immediately after modifying the DOM.
These are selected picks from a blogger. The original list was hosted on Mr. Alex Bellos' blog, which has since moved.

See the "new" section for the apparently complete list.
For functioning people with mental illnesses (well treated or not severe), it has gotten better. For non-functioning people, it has gotten worse, for them and for society. I have a loved one with functioning schizophrenia. She has great care and good support through her family (including one of the most loving big brothers I've had the pleasure to meet), her friends, her church and her school.

But I know if she has a true psychotic break, there is little to no support available beyond a 72 hour evaluation. Jail has become the defector storage place outside of the underside of bridges because there are far too few beds for people who need longer term care.

The state hospitals of the 50s were horrid places, but in dismantling them, we've done away with almost all long-term care for people who can't function due to mental illness. And that comes with a huge cost to society. There was a middle ground of "let's improve the care and treatment" that was completely ignored.

But, as a society, let's not talk about that. Let's talk about whether 11 bullets or 14 buckets are too many, even if a fire extinguisher can be shown to be a horrid weapon to somebody ill enough.
If a shuttle launch and a Dragon launch have the same utility, what you say is true, but the shuttle can carry a lot more cargo. For example, the Dragon is nowhere near large enough to carry a full space station module. I'm not sure that this renders what you said false, but there's a lot more to it than this.
People are praising the transparency of this report, but I am not sure I agree because of this point. when I read the report, I had to stop to think when I read the part about packet size to conclude that they had to be talking about an IPv6 packet using the hop-by-hop extension for fragmented packets. That is a special case, because you don't actually know the length of the packet until you receive the last fragment.

As a consequence, fragmented ipv6 packets are error for use in DoS attacks. This is not a "weird" occurrence, but rather an expected one, and since end points are not required to accept such huge packets, I am surprised Cloud flare want already doing all it could to advertise to upstream sources that IPv6 fragments longer than a much smaller than 90K should be dropped, at least if rooted to their DNS. I am also surprised that when their software came up with that kind of a response without first validating that it wouldn't cause the exact memory problem it did. Rules on v6 fragmented packets that can't match on a single fragment are inherently dangerous. It is only reasonable to have safe guards already in place for them.

I am also not sure this is really a bug in Juniper software. I imagine the memory problem only shows up with high traffic and in the midst of a DoS attack. That is kind of a given when you put a rule like that in that kind of a situation.