skysight-inc/HackerNews huggingface dataset:
We should be happy: For all its warts (horrible, horrible spelling) English is an order of manitude saner than German and a few other European languages. Imagine if you had to keep track of which (for all intents and purposes more or less randomly assigned) genders any thing had. Imagine if a/an had 12- 44 different forms instead of two and was dependent on the position, movement, a randomly assigned "gender" as well as ownership of the object in question. This is what German and a few other languages are like. Utterly stupid but it would sound ridiculous if we dropped it now. Just saying.

(Source: native speaker of one of those.)
If he's serious about that stuff, he should look at a minivan.

Or here's a wildcard. It's similar to the Aztek, the GMC Envoy XUV. The Aztek gets about 94 cubic ft of cargo room, the XUV is 95.5. You won't find one new, but so long as you get the V8 4wd model it will last a long, long time with many replaceable parts.
Ask HN: How many hours did you spend on investor pitch?
That was my thought as well. Given all communication is considered compromised, I can't think of a simple way to do this that isn't a face to face.
If for no other reason than the press attention the project received. Likewise, Amazon isn't likely to actually deliver packages via drone, but it didn't stop 60 Minutes from devoting a show based on the concept. A writer coined a term "Conspicuous R&D" to describe efforts like this. Auto companies have been doing it for years in the guise of "Concept Cars." From a pure engineering perspective it's not an optimal solution, but it gained a ton more attention than if it was merely a sort of small quadcopter.

I wouldn't be surprised to see this company eventually move towards non-wearable drones, but this little R&D project doubled nicely as a marketing campaign.
That's a compliment to Amazon.
The Idiot's Guide for Migrating from Heroku to Amazon Web Services Opsworks
> I run fixed release distros on production servers/devices. It's important to be able to install a new package on a machine and not have a hundred dependencies need upgrade, break or conflict.

Isn't that an argument for rolling release? I don't see how this would support using fixed release distros.
I agree with you regarding all of the above, except for the DMA bit. That has to do with crappy drivers causing crashes. Without direct DMA you'd have horrendous performance issues. It is not a transistor count issue.

These days pluggable devices (SATA, USB) don't get DMA access. Only physical cards do (PCIe, etc.) -- again because of performance issues.
It's difficult to get the real-time processing and performance you want for a quadrotor control loop with Linux. You usually want to write firmware or use an Real-Time OS.
Wasn't popcorn time just a "tool" ?
The tool is not infringing on copyrights until the user actually runs the application.
Your coworker should look into a minivan with fold-flat seats. I rent them when I needed to move equipment. They have great cargo carrying ability with the flat floor, plenty of anchor points, and not having to worry about where to stash the seats is really convenient.
A 1988 Mercedes That Has Been to 172 Countries (2013)
I'm sure this was made in jest, but this is probably a real concern with folks at the NSA. With stuff like this becoming consumerized and easy to use, how long do you think it's going to be before some jerk decides it'd be a good idea to strap a bomb to one and fly it into a building?
Good luck keeping any clones from popping up in the future, especially in a decentralized repository.
Coincidentally, I've just been reading about Esperanto. It seems slightly nutty in today's climate of English dominance. But when you needed to learn several natural languages to communicate internationally, it made far more sense to pine for a simple, neutral common tongue.
> If you're going to wait a few months to update, you are much better off on an actual non-rolling release distro than Arch.

I think that's a good point and that makes sense. And I agree with that from my experience. However, I generally think that one should not wait months to do updates.
I don't want to threadjack, but you don't have an email in your profile.

If you (or anyone else reading) ever want to talk about what "this will be a problem soon" might look like in the future drop me a line: dave@pagerduty.com
They also say We may, but have no obligation to, remove Content and Accounts containing Content that we determine in our sole discretion are unlawful, offensive, threatening, libelous, defamatory, pornographic, obscene or otherwise objectionable or violates any party's intellectual property or these Terms of Service.

Which is a long winded "If we don't want to host something we won't."
Calling people out as #worseisworse is almost certainly going to be ineffective - attacking people just makes them defensive and argumentative. Instead, can we find useful principles to steer us away from the two bogeymen (hack-it-till-it-works vs useless-ivory-tower-wankery)? Some ideas:

The real world exists. Successful solutions usually come from actually understanding the problem and all it's constraints. Solutions that are dismissed as overly academic tend to fall afoul of solving just the immediate problem and ignoring eg compatibility, switching costs, accessibility to beginners. Similarly, the linux community spent a long time burying it's head in the sane w.r.t. usability and appearance. Sure, people shouldn't care how pretty your UI is. But they do and you can't change that by burying your head in the sand.

Everything has a cost. The benefits of your new solution and the switching cost have to outweigh the pain of the old solution by a large margin. The original 'worse is better' was really an observation that simple solutions that do half the job are often cheaper than a hugely complicated solution that can do everything. If you spend every day coming up with better ways to make widgets, it's easy to believe that everyone wants to have as much widget-customising power as possible and is willing to invest time in learning to get that power. If you actually talk to your users you might find that only having three kinds of widget isn't annoying enough to make them spend time learning something better.
That was a deliberate choice in initially establishing the character. He was such a shlub that he dove an Aztek.
Can you just install JDK8 and select 1.7?
I see and I used to agree although I usually didn't care to do that myself. Lately I find a lot of the downvoting that has been going on has been so stupid that the stupid "why the downvotes?" question has seemed relevant.
That's a huge and critical difference. Open source down to the hardware is the only way you can be sure that what you're getting is actually Tor and not Tor + secret backdoor. (Though I suppose you still have to trust the hardware manufacturer, but the buck does have to stop somewhere.)
I don't think what you provided are counterpoints, they're facts in support of the point.

Censorship in the name of preventing "foreign interference" is no less censorship.
Would add another dimension to car vs. smoke alarms. [1]

Smoke alarms are loud and typically near you (think about the one that goes off in the kitchen because of burning pizza in the oven). So you have to react or you are paralyzed. You fan it almost immediately. You have to.

Car alarm typically you can't do anything (unless it's your car) and the noise, while annoying, is not as close or as loud as a smoke alarm.

[1] Edit: Distance from and the decibels of the alarm and what you can do about the alarm. Of course there are also building alarms (follow procedure) and alarms in your own house "get the noise to stop!"
What do the android ids look like? I'm assuming it's just a number, but I don't know how big. The page you linked to says the key is md5(android_id + "seems legit..."). It seems to me like this could potentially be brute forced to find the android_id using a captured encrypted image.
> I have never heard of Illumos which also implies I've never heard anything bad about it.

It's the open fork of OpenSolaris after the Oracle takeover of Sun. Many ex-Sun engineers work at companies that use/contribute to Illumos.
> Having the team feel direct pain is a great motivator for building robust applications

But the OP is a dedicated reliability engineer, they don't build the actual applications and couldn't given the size of the company. Essentially you're being punished for other team's generated issues.

You getting punished when your own stuff breaks is more a small business issue, not something corporations have.
It's worth mentioning both that Debian Testing is not called 'stable' because, in their own words, there are occasional significant breakages. It's also worth mentioning that right now, Debian Testing is being prepped for a freeze to become Debian Stable in less than a month, and it's absolutely chaotic as everyone is applying patches all over the place to get them in before the freeze.

After the freeze there'll be two months to sort out critical bugs like the ones in the article, but this possibly wasn't the best time to do a big upgrade of an edge-case system. Well, unless you want to find and report bugs :)
The first one that got a tiny bit of seed money? under 10.
semi-optimal setup; ip_hash might give you issues if you have to server a lot of mobile-clients (at least here in europe), because of central proxies used by mobile-providers. this one might help if you need stickyness: https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng/o...

instead of "if ($host !~ ^(api.yourdomain.com)$ )" you should use a "server_name api.yourdomain.com;" - directive for your proxy_config and a catch_all - server{} block that consist only of "return 444;" to avoid that "if"-processing on any request.

oh, and you might want to use "ssl_session_cache shared:SSL:1440m;" for better performance (adjust the timeframe accordingly, i've seen values from 10 minutes up to 48hours like google)

> SSL certs tend to be rather confusing ... no not, really, but i leave it up to you to figure out what a key is and what a cert :D
> The problem is that can't act on symptoms, only research them and then act on the causes.

Have a look at the example at the top of page 5.
It seems like this would be a great case for doing a machine learning approach. Something good at anomaly detection like single class support vector machines, perhaps.

I wonder how well that would translate for a client services person, though. "Why do we think this client is off?" "Because black box."
"American products were inferior to German-Austrian-Swizzerland ones"

Got some examples? Cars are a given, but I couldn't think of any others where the difference was that pronounced.
Severe Hand RSI Pain and Recovery
I run Debian sid, and I upgrade almost every day, with a few exceptions (like "during or immediately prior to travel"). Doing so lets me catch issues before others hit them, file bug reports, obtain the latest fixes and improvements, and participate in the community that shapes future architectural decisions for the distribution.
I've read a few papers on this in the past, after having originally seen the video. The ongoing research is indeed nuanced and complex, and as with a lot of ongoing scientific research, there's disagreements among scientists.

Different papers use different methods to estimate predation risk in various locations, for instance. Some base it on actual predation incidents, some on landscape factors (which may model risk perception as opposed to actual risk).

There's also discussion about the way active predators such as wolves impact an area, which is different from lie-in-wait predators. And there's an idea that a constant background threat comes to be ignored, as opposed to a sort of pulsing threat, where there are surges of predation.

Also worth noting that various studies take place in different areas of the park, and in different seasons. Not to mention there's three main varieties of trees under discussion (aspens, cottonwoods, willows), which have all seen different recovery rates in different areas.

It's not a simple question, and from what I've seen in my sort of casual reading on the topic, it's not at all settled.
Not when you have a few hundred servers. Then, you want consistency. Consistency between servers, between datacenters and between pre-production and production environments.

Now, you can get there with your own repos and a rolling distro. Or you can accept a test/upgrade cycle for a fixed release distro every half year or every year. I personally think the latter is less error prone.
Chrysler T&C minivan. As a bonus, it's almost as ugly as an Aztek.
Amusingly, the "Azteky" cars you list were also failures of market demographics (and have all since been discontinued).

Of them the best seller, the Element, enjoyed mild success only because it missed its target market entirely. Instead of the "young urban males" it was targeted at, it was instead popular with older people who wanted an economical vehicle with easy cargo access, and dog owners, who wanted a n interior that was easy to clean.
Happy to know people are working on substitutes. The perfect replacement for me would be a combination of Forrst and meetup. What I mean by that is that it should be some place where I can showcase my skills and get involved with like-minded individuals in the same or adjacent professions. As someone already mentioned linkedin is really just a recruiter database and the social aspects are completely forced.
That's Bob Lutz writing. I was just re-reading his book, "Car Guys vs. Bean Counters". It's fascinating to read how he thinks about cars. He writes that there is no part of the car market where an existing product can't do the job. So it's all about going for customer desirability, and looking for the "buy trigger".

Cell phones and tablets are just about to that point, at least until somebody has a new big idea. They're all little slabs with a touchscreen and some cameras.
> every few months, you have to update EVERYTHING all at once

The non-rolling OSes I use - RHEL, OS X - have longer than "every few months" release schedules.
Re: this will be a problem soon? Metrics trending. Look for changes in your metrics to spot potential problems and plan for the future. This is done quite often for example in QA to look for issues between releases, and can be done both macro and micro in terms of continuous delivery services' metrics.
And it was the perfect choice, precisely for what it said about his character at the beginning of the show. Walter White, the put-upon high school chemistry teacher living in quiet desperation, driving around in a car generally perceived to be a big, swinging two-ton white flag to the world.
I found the car an over-faceted monstrosity but since that time several uglier cars have been introduced - e.g. Nissan Cube - that didn't seem to suffer the same level of rejection. So timing is probably everything.
How is that harder then keeping track of the billion didn't vowel sounds and 4 ways to represent it? Or the lack of any sort of rule, as every single one of them has exceptions. Or the fact that depending on where you live depends on how you spell and say words which mean the exact same thing. Or the whole Your vs You're or its vs it's. Or the way it spells words which make absolutely no sense. Or the fact that half our words are German and the other half are French.

I know 3 languages, German and French are both easier then English. And English is my mother tongue.
Also worth mentioning is that large amounts of the linux kernel can be either 'built-in' or built 'as modules'- I think most distros prefer modules where possible.

Run shell command 'lsmod' to see all the modules you currently have loaded, and check out the .ko files under '/lib/modules' to see the modules provided.
There were crossovers and small sport utilities for many years before the Aztek, so it certainly wasn't a timing problem. Look at the Toyota RAV4 (came out in '94), Honda CR-V ('95), Isuzu VehiCROSS ('97), and even original Jeep Cherokee ('84!). The Aztek was just a terrible looking vehicle for the mid-2000's, had a completely lackluster engine and drivetrain, and ended up being built on a mini-van platform instead of an SUV platform to reduce costs. There is truly nothing redeeming about the car.
Here's another good writeup on effective alerting, by a former Google Staff Engineer: http://blog.scalyr.com/2014/08/99-99-uptime-9-5-schedule/
I'm a medical doctor and this is such a big problem.

I applaud your efforts and encourage you to keep on working, I hope that you get employed by a pharmaceutical company in the near future :D Or else.....disrupt the pharmaceutical industry ;) Good luck :)! If you need any further insight, would be more than happy to help you out :)!
Beautiful website. I love the simplistic yet colorful design. I'm looking forward to using your service.

Side notes:
Your social icon footer is broken. The Twitter icon has the "Twitter" text next to it. The others have "#" in the <a> as the link. In the bottom footer, I would suggest linking to your twitter account instead of saying the user name.
I don't know much about Debian. I may have slightly mischaracterized things because I don't understand. That's why I asked.

I am getting the impression that Debian Testing isn't really used in the sense of, "Be a nice volunteer and run this thing that has problems so we can fix them," which is what (to me) is implied by the name "testing." Rather, it seems to be "here is a (mostly) rolling release version of Debian, if that's what you want." In other words, it almost seems like "Debian Rolling" might be a more apt name, in a sense.

The thing is, as a user of Arch Linux (without a ton of other experience), I just don't have problems with a rolling release. For me, things don't break, and it just works. So it feels to me like Debian's whole release philosophy is based around the idea that things have to break all the time and be fixed carefully, and that just doesn't sync up with my experience. So I'm trying to figure out what is missing from my worldview.

Thanks for defending me. I think might be somebody (maybe multiple) who doesn't like me and just downvotes all my comments, but I don't have any hard evidence.
On Getting Wasted
So the whole thing was more like the neighbor's dog, Spot, crossing your lawn to pick up a frisbee? Interesting viewpoint.
Because too many men from continental Europe were slaughtered during WW1. In many ways Europe has not recovered until 1960.
What do you mean by large _concept_ application? If you mean large or famous projects in production, Yii 2.0 was just released so there aren't many.

For 1.1 there are some:

https://www.facebook-studio.com/,
http://2gis.ru/,
http://itop.fm/,
https://www.humhub.org/,
http://www.x2engine.com/,
http://zurmo.org/,
https://www.rebilly.com/,
http://buildwithcraft.com/
Remember that before WWII US of America was [...] with a lack of formal education.

Source? American scientists were the only ones staffed on the Manhattan Project. Germans were focused on rocketry, and their work contributed heavily to the space program, but to say the US science was nonexistent seems a bit of a stretch.
They're probably exaggerating the state of language education in most of USA before those laws. However, one could also imagine the thought process of prospective teachers who lived then: "Well my Greek is pretty good, and with a couple of years' more study I could teach at the high school level. On the other hand, we might get in a war with Greece someday, so instead I'm going to teach math."
> For all its warts (horrible, horrible spelling) English is

English is not my native language but I love its spelling and I think it's ideal. I'm not referring to saxon words, though, but the majority that comes from Latin, Greek and French.

I'm also glad English has no Academy prescribing its usage; lack of genders is super nice; easy article rules another plus; if we could get rid of the preposition madness it would be perfect (i.e. in/on/at are not uniformly applied as inside/on-top-of/at-point-of).
Why I Love Startup School
We know of at least one Tor hidden service which was deanonymized because it leaked an IP address at some point. This protects against that flaw being likely to happen again. That is what the use case of this is. Of course it's not enough on its own. It protects against a specific attack in an easy-to-setup way.
Wishlist for CSS features from 1998
It's time to decentralize source repositories.
30 Organization and Productivity Gurus You Should Follow on Twitter
What's news is that this isn't how the DMCA is supposed to work. It's supposed to apply to copyrighted material. Not material which when downloaded and run will connect to a P2P network and attempt to download material, which has some probability of being infringing.

This case actually seems relatively flimsy; and as the DMCA notice admits, it hinges on a previous ruling that

“the distribution of a product can itself give rise to liability where evidence shows that the distributor intended and encouraged the product to be used to infringe”

Unfortunately there's no way this notice will be challenged in court, so we probably won't find out if it was legally valid or not.
Airplanes, aviation engines, jet engines, rockets
Tor traffic is monitored. Many high-bandwidth endpoints and relays are run by law enforcement, and Tor is configured to preferentially use high-bandwidth nodes. It is a given that, at minimum, all Tor metadata is logged; if not all content.

Additionally, the list of exit nodes is open and public, (https://www.torproject.org/projects/tordnsel.html.en) so any given server can tell if you're using Tor.

Comparing Tor to your neighbor's open wifi was an example of how poor Tor's anonymity is, rather than how good your neighbor's connection is.
> Attached as Exhibit A is a series of screenshots taken from within the applications of each Project that includes images of copyrighted works available through the Projects. The representative titles shown in Exhibit A consist of only some of the motion pictures and television programs that are owned or controlled by the MPAA Member Studios and that are being infringed via the Projects. Exhibit A is provided as a representative sample of the infringements being committed as a result of the operation of the Projects and to demonstrate the readily apparent nature of the massive infringement occurring via the Projects.

So by this logic...the source code for any web browser, torrent client, media player etc. etc. should be subject to these notices because they can be used to infringe copyright?

After all, through any of those applications, I can take a series of actions which could infringe copyright....

Maybe we can skirt by with the general purpose nature of the above tools...so what about tools used to facilitate penetration testing (which can also be used for computer crime) - should we get rid of that source code too?

I don't know the architecture of popcorn time, but if they published a generalized application which when given a configuration file (sources of infringing content etc.) would allow copyright infringement should we ban both? Or just the configuration file (which does not in itself infringe copyright)??

Making distinctions like this is dangerous, and allowing speech to be suppressed by corporate interests is a worrying trend.
Reminds me of a "joke" that my Uncle told me once:

An aircraft controller was sitting in a tower in Berlin-Tegel, and hears a request for landing by a Lufthansa pilot speaking German. The controller asks the pilot to please repeat the request in English. The pilot asks, "Why must a German pilot of a German aircraft landing in a German airport make a request in English?". A British Airways pilot, listening in on the conversation, interrupts: "Because you lost the war".