skysight-inc/HackerNews huggingface dataset:
nginx does have the minimum necessary support to handle shared session ticket keys. It would be nice if it did more for you out-of-the-box, but I'm more interested in practical solutions that work today.

You can specify ssl_session_ticket_key multiple times, and the subsequent declarations are used for decryption only.

It does take some elbow grease to implement the tooling around this, and it's unlikely that many people have bothered, but they should.

1. Generate new key on a master host (store only on tmpfs partition for extra points)
2. Somehow get it on all of the relevant hosts securely, such as by using lsyncd
3. Add new key to end of list of ssl_session_ticket directives
4. Reload all nginxes that answer a particular address
5. Move new key to top of list
6. Reload all nginxes that answer a particular address

(after I wrote this, I noticed it was pretty similar to Twitter's idea. I guess great minds think alike.)
These kids are HILARIOUS CUTEST sibling rivalry withtalent. MUST SEE
>> it didn't help that the language itself didn't, at the time at least, make it obvious how to do such things.

Why should a language "make it obvious" what are clearly implementation details?

Hashing passwords is not the job, or the concern, of any language I've used.
The Best Day to Close a Sale (Infographic)
It's not about being more or less free. You should ask the question "freedom for whom?"

People who use Copyleft licenses want the users of the software to have freedom. People who use permissive licenses want the developers of the software to have freedom.
OS X updates have been virtually flawless for me in the past. Yosemite is the first one with big problems:

- No longer able to connect to any 5GHz wifi routers.

- Wifi drops suddenly and won't reconnect automatically even though the network is present.

- Very slow wifi generally.

- Unable to restore from sleep, machine reboots.

- External display doesn't come up during login after sleep, need to open MacBook and login there.

- Random hangs/kernel panics. (Could be explained by faulty RAM, but starting to happen just after Yosemite upgrade? Doubt it.)

- Laggy UI.

The last point is the worst. "Reduce transparency" does nothing for me. WindowServer is occasionally using 20-30% when the system is doing almost no redrawing. Safari is sluggish, and often hangs for several seconds — especially on opening new blank tabs, loading a new site, trying to load an embedded YouTube video ("HTML5" mode) — before becoming responsive again. Overall, it feels like my machine (early 2013 MBP, quad-core 2.7GHz i7, 16GB, SSD) just rolled back two hardware generations.

Hopefully this update should fix the wifi issues. But the lagginess isn't mentioned in the release notes. Has anyone gotten any performance improvements by reinstalling the OS from scratch?
The catkin and bloom tools developed for ROS (robot operating system) go a long way toward mitigating this pain— they make it much, much easier to maintain a source workspace of multiple federated packages, build them all together with dependency resolution and a single command invocation, and switch between the released (deb) and source version of a particular package.

Unfortunately, there isn't a good page which explains this all for the benefit of someone who doesn't care about ROS or robotics specifically, or who doesn't care about how catkin compares to the legacy system it replaced. But this is a start: http://wiki.ros.org/catkin/conceptual_overview
Funny, I googled "programmer testifies..." and the first autocomplete was "...about rigging elections": https://www.youtube.com/watch?v=tjvtSquZkhs

Journalist Greg Palast also has evidence of electronic voter in Ohio in 2004. (Disclaimer: I have not delved deep on his claims, but the mere fact of their plausibility is deeply concerning.)

http://www.gregpalast.com/how-they-stole-ohio/
It's getting better. I, for one, am going to begin contributing to the core code :)
If it's any consolation, I think spider uses the most sane syntax out of any compiles-to-JS language I've played with so far. And that's coming from an arachnophobe :)

Maybe because I've written a decent amount of C++ I'm more acclimatized to the "::" syntax..
Strange how "campaign finance laws" always seem to come down to suppressing speech.

Sounds like there's also serious doubt this is in any way illegal, e.g. this comment by "Daniel Tokaji, a professor of Constitutional Law at Ohio State University":

"A lot of things you and I would consider coordination are not coordination under the law. I don't think sharing polling data is going to be enough to establish that the campaign was materially involved in decisions about content, target audience or timing."

Outlawing "coordination" is a very dangerous slippery slope to go down, as Wisconsin recently showed.
Out of curiosity did you fresh install or upgrade?

I'd upgraded since Leopard/Snow Leopard it had always just worked for me. Yosemite though had crashes and hanging - I decided a fresh install and it's been working great since.

Not the best news if you're used to upgrading but for me it worked wonders.
Yeah, except there is no proof that there is any exchange of goods taking place in the overwhelming majority of these.

Do you think teenage girls and boys are really going to start selling their nudes? Just on a shallow examination of this possibility, it seems exceedingly unlikely to ever be a problem on a scale larger than a handful of cases. The social aspects of trying to sell "nude" pictures of yourself would be utterly taboo. The only market would be for people that you don't know, yet then the risk increases dramatically. There are already 100s of sites where they can do exactly this (pretending to be 18), yet its not happening, at least on the scale that the fear represents.
The problem with the cost-cutting mindset is that it often allows for actions that seem really counter-intuitive. A friend of mine was spec'ing out some pumps for an off-shore platform, and they were rentals. Turned out renting was like thousands a day or some similarly absurd number. Company ended up renting like twice as many pumps, just in case they needed them for redundancy.

It literally made more sense to spend hundreds of thousands of dollars for pumps that sat around and did nothing just to make damned-sure a multi-million dollar rig never sat idle.

So, when we hear that there is too much complexity in, say, making sure nobody is drinking from wells within a mile of where the stuff is being injected, we look askance.

O&G is full of money and talented engineers, so I doubt that this is a problem we can't overcome.
For those on food stamps: http://thepiratebay.se/torrent/11017423/Waking_Up__A_Guide_t...
It's deserved. Gotta give it to them though, pretty bold move considering.

http://www.wired.com/2014/10/the-snappening-is-not-your-faul...

http://www.foxnews.com/tech/2013/12/27/snapchat-ignored-secu...

http://gibsonsec.org/snapchat/index.html
> What's the deal ?

Mac OS and OS X always had good multi-monitor support. In 10.7+ Apple tried to push a "one app in fullscreen as in iOS" approach as new paradigm, negatively affecting the multi-monitor experience. It backfired and they adjusted in 10.9+.
Even if you've posted a skeptical comment, do you doubt that one day sending money in a chat app will be totally normal?

When it's there it could be the foundation of hundreds of new business models and applications, and the reason a few household names went the way of Myspace...
This is indeed a huge bummer, now that I've upgraded to yosemite I've got 1-2 full seconds of lag streaming audio to my blue tooth receiver.
We used it for the operating systems course I took as a reference OS while building a microkernel. It really is quite good, reading the code is far more helpful than reading a textbook.
It's always intriguing to me how critical the BSDs and BSD programmers are to the Linux ecosystem, even though their user base is fairly small.
> Clear benefit is supporting codecs which their users can encounter without forcing them to reencode to anything else.

That assumes their users actually ever encounter such music. I fully expect that significantly less than 1% of Apple customers ever encounter FLAC music, and those that do, do so infrequently and with other options made available as well. Personally, every time I've seen FLAC as an option, it's been one of a set of options (typically including MP3 and AAC, and often even including ALAC).

> Clearly for Apple "benefit" means screwing users and degrading interoperability.

Bullshit. Nobody is being screwed here. Anyone who gets FLAC music is choosing to do so, and it's pretty trivial to reencode. And there is absolutely no interoperability issue here. FLAC is not a codec chosen for portability reasons; very few people have any reason to be using lossless audio to begin with.

> False pretenses to hide real intentions - retaining lock in and reducing interoperability, which were always Apple's notable goals

Bullshit, bullshit, and more bullshit. Apple was at the forefront of pushing to remove DRM on music, and you're trying to accuse them of lock-in? Either you're horribly deluded, or you have your own anti-Apple agenda that you're trying to push here. Either way, you're pulling this argument from thin air and it is entirely incorrect.
Court Finally Throws Out Ultramercial’s Infamous Patent on Advertising
On hacker news we are only allowed binary decision making no matter how analog the situation, but obviously the optimum solution is to talk to / work with both, although I'm guessing they aren't going to literally work with each other at the same moment. Which is really too bad. I could totally see a GP, Specialist, and Patient relationship developing.
This also baffles me. I have a number of friends who use OS X for development and some just use one large monitor + spaces but the majority use multiple monitors. None of them experienced this issue but we were unable to figure out (we didn't spend a lot of time on it) what was different about my setup from theirs. Maybe it just never manifested for Apple employees? That sounds a little ridiculous but I don't know what else to think.
Arguably the short duration helps quite a bit... bad trips don't start instantly....they are more of a gradual building of anxiety that builds to a sort of panic attack.
Well, since it's ultimately based on the fact that we evolved with 10 fingers and 10 toes, it's not meant to be taken literally. In fact, some programmers are effectively worth infinitely more than the average. The average programmer isn't even a fraction of Ken Thompson, for instance.
No mention about fixes to the WindowServer using all available CPU either... When there's animation on the dock it happily uses ties up a core for as long as it can.
Have a look at this:

http://ianmiell.github.io/shutit/

which is a means of capturing this complexity for automation purposes.

https://github.com/ianmiell/shutit

I'm working on a "shutitdist" to compile "everything" from source:

https://github.com/ianmiell/shutitdist

ShutIt can (among many other things) produce depgraphs like this:

https://raw.githubusercontent.com/ianmiell/shutitdist/master...
Good grief, that's a statement. And bravo.

(However, what can they really do with that money? Operating systems aren't the sexiest of free software projects to work on, so I would be tempted to think that manpower is FreeBSDs biggest limiter.)
It is probably worth nothing that "female" is really a parenthetical. Source is simply using the appropriate Polish word (which is gendered). The translation could be read as implying that the person's gender has anything to do with the issues they've had, but source's wording doesn't really imply that. (They may have in fact wanted to imply that; but we can't determine that from the wording.)
Also https://news.ycombinator.com/item?id=8619284.
Or realize promising things like this is like a student council president promising everyday is pizza day and no school on Fridays.
Yeah, and you can't check file integrity (hash or crypto signature) first, or list the contents of the file before extracting.
Disappearing cash!
Combine this with one of those tiny self-compiling C compilers that were the subject of a few HN articles recently (e.g. https://news.ycombinator.com/item?id=8576068, https://news.ycombinator.com/item?id=8558822) and this could be one of the more interesting minimal self-hosting OSs someone could understand the entirety of in a relatively short amount of time. I like how it supports multiprocessing too, and the entire kernel is <100 pages in the source code PDF.

However, I wish they'd use something other than GAS for the Asm parts... a minimal self-assembling assembler (and a C-subset compiler written in it, to bootstrap the whole thing) would be nice.
>> Just as Windows is highly secure

That's a bold statement.

I don't presume to know more than you, but I don't hear that sentiment echoed very often.
I never found that to be an issue getting friends to sign up for Venmo. You don't need to enter any info to accept cash. It was getting them to realize this was cash and not some magic points (because they dont know what venmo is). Snapchat should kill it here because people already understand and trust (for the most part) Snapchat and this is just a new feature - not an entirely new service to learn.
I did an upgrade and I'm considering wiping and doing a fresh install when I get some time. This is my primary work machine (it's a personal laptop but all my work stuff is on it) and so I'm hesitant to take any chances or do anything that could mess with my work timelines on projects.
I'm an American someone who's been called a hipster who moved from NYC to Berlin.

I walk into Berghain whenever I want. Then again, I care about the community, took the time to learn German, and have established connections in my city of residence.

If you're obnoxious, you're going to be shunned anywhere you go. Your misconceptions aren't helping Berlin or NYC.
Is New York the New Model for Startup Cities?
A worthy report, but some valuable context is buried near the end of the article/TV news report.

“We are still comparing the testing of what was the injection water to what is the tested water that came out of these wells to find out if they were background levels or whether that’s the result of oil and gas operation, but so far it’s looking like it’s background,” said James Marshall from the California Department of Conservation.

So it seems as if no actual contamination of the aquifer has taken place so far - not an excuse, but far from the environmental disaster you might have imagined when you heard about 3 billion gallons of waste water.

When asked how this could happen in the first place, Marshall said that the long history of these wells makes it difficult to know exactly what the thinking was.
“When you’re talking about wells that were permitted in 1985 to 1992, we’ve tried to go back and talk to some of the permitting engineers,” said Marshall. “And it’s unfortunate but in some cases they (the permitting engineers) are deceased.”

Again not an excuse, but when you learn that these injection sites were permitted 20-30 years ago (at a time of lesser technological and environmental awareness, as well as of lower population and land usage intensity), then it's not so surprising that some bad decisions could have taken place. On the plus side, the fact that the injection wells have been in use for oil exploration for so long and contamination actually seems to be quite limited suggests that halting further injection and carefully monitoring the surrounding wells may be sufficient. In other words, an unjustifiable risk but one that seems to have been identified and halted prior to a serious failure.
You must understand that I live and breath in the terminal. If I'm working, my computer has at least one terminal window open.

When I'm in the middle of projects, there are several terminals, all on different 'machines' (ssh/chroot/and now docker) in different directories, and I need a file, be it source code or a binary or an rpm/deb/tgz/zip or just plain data to be where I am right now. I might use scp for this purpose, I might use rsync if the connection is flakey. Some times there's a shared file server and I can just use 'cp' instead.

Http is just yet another protocol where files come from, and when I use curl/wget I don't want the file in ~/Downloads along with all the other random crap, I want that it downloaded to where my terminal window is pointed, which may be a machine half-way around the world from me, or at the very least, in the right directory.

It doesn't make sense to download it to my machine, then upload it to where it needs to go either - just wget it directly, on the machine it needs to be on, in the directory where it needs to go.
> Music in ALAC? I never saw it being sold anywhere.

Because almost nobody has any reason to want lossless music. Anyone buying music in FLAC is deluding themselves if they think they can hear a difference between that and a properly encoded lossy codec like MP3 or AAC.

> Any time you want to reencode your music, you care about the lossless codec for the source, otherwise you'll degrade your quality.

True. But this is an issue for so few people as to be effectively zero. Extremely few people actually do this sort of thing, and I would wager that most of them aren't Apple customers to begin with.

If Apple had infinite engineering resources, then yes, it would be nice to solve every single problem for every person, everywhere. But Apple's engineering resources are not infinite, and it would be a flagrant waste of those resources to spend them on issues like this that impact effectively zero Apple users.
I like the original title better. It's interesting that you chose to un-Betteridge the headline for Hacker News. I'll take that as a compliment.
I am not sure what you mean. Are you sure what you mean?

OSX (and I think even earlier MacOS) have supported multiple monitors for quite a long time, historically better than most other OSs. Many of us use multiple monitors on OSX with no problems. One neat thing OSX/MacOS have always done with multiple monitors is allow you drag windows from one to the other as if they were one big workspace -- even having a window partially on one monitor and partially on another, with it working fine.

What has happened recently is that the combination of the OSX UI, multiple monitors, and new features to support a 'full screen' mode (which seems to some people like a sort of convergence with iOS) -- have been problematic. Apple has had trouble deciding what _should_ happen with multiple monitors in this situation, and has had trouble making it work reliably.

Until the most recent OSX release, you could only do 'full screen' mode on your 'main' monitor, the other monitors would all go dark. Which was pretty annoying for those who wanted to use this newish feature. But other than that, multiple monitors had no real problems.

In the most recent OSX, they've tried to do some things to take care of this, so you can use 'full screen' mode on all your monitors (one 'full screen' workspace on each monitor). (Sadly, these things also get rid of the ability to have a window half on one monitor and half on another).

The solution they tried appears to have some technical problems. Which yes, is frustrating for people with multiple monitors, who want to use the 'full screen' feature, with the new improvements (which you can turn off if you want, to back to only being able to use one monitor in full screen mode).

I think many people do have a sense that Apple QA isn't quite as good as it used to be. And they do seem to be having trouble getting the new-ish 'full screen mode' (which people seem to like) to work reasonably with multiple monitors. But I don't think it accurately represents the history to suggest that OSX has historically poorly supported multiple monitors. I am not familiar with what you are referring to when you say "prior to [Mavericks] there were all manner of basic usage problems," that has not been my experience and I have not previously heard of such experience.
The tenant will still pay, just in the form of increased rent. Costs pass through to prices. Landlords don't own property to lose money.
My top 5 are:

1. Advertise on Google (adwords)

2. Advertise on Bing (which is the same thing as advertising on Yahoo at this point)

3. Advertise on Facebook

4. Advertise on Twitter

5. Open an affiliate program (CJ, Shareasale, etc)

While that's happening: Run split tests and optimize every part of your conversion funnel. Up those conversion rates, lower those bounce rates and abandoned shopping cart rates. Every little bit helps.
What an awkward monetization scheme. Seriously, this is why you passed up x billion dollars? Should've taken the money and tried to actually help the world. Silicon Valley greed and delusion at it's finest.
Every time I spend some time in BSD land I'm pleasantly surprised with how well-designed, featureful, and well documented everything is.

For dedicated server systems that developers don't access, it's pretty much perfect. I kind of wish that the developer world had standardized on that rather than GNU/Linux, though perhaps if there was a wider pool of developers, the BSDs wouldn't be so clean and straightforward.
Eventually this will probably happen in one way or another - although make isn't going to be replaced - it'll remain there for compatibility.

Currently, in a guix package, you specify how the package is built - and there are some predefined configurations built into guix, such as the gnu-build-system. It's perfectly possible to write your own build script in guile alone, or you can call other build tools.

In case you missed it, GNU Make already has Guile support built in - so you can already use it to augment your build process without throwing away make.

The real advantage of having a build process as part of Guix will come when we can throw away horrible hacks like pkg-config - since the Guix model of exact dependencies offers far more accurate information that pkg-config can guess, we'd have more reliability with less effort, and probably big performance gains.
Right, that's the fundamental problem with free-market idealism. There is not an effective limit to the damage that can be done, but there are limits to liability. Many industries are capable of committing environmental destruction on large scales, but don't have any assets when the EPA comes around looking for restitution.
Care to expand your points on this? I'm not totally up with all BSD does / how it is used today.
If I recall, in Arkham Asylum, it was impossible to win the big boss fight, but there was no messaging about it - it just happened.
I've had similar experiences with recruiters, so I don't really understand all the hate. If you're not looking you can be direct and get rid of them quickly without being rude, and if you are looking you just need to be smart like any other business transaction and keep an eye out for time-wasters and scams. The more I work with them, the more I appreciate their services and the better I get at spotting the 'real' professionals.
I wonder if there is a way to add a penalty to comments off topic, not to affect a uses karma but just the comment ranking.
same here. hope they fix it soon
The Black Knight Satellite
>It's always intriguing to me how critical the BSDs and BSD programmers are to the Linux ecosystem, even though their user base is fairly small.

Edit: "critical to". My mistake.

Why? Do you think popularity reflects quality?

It is immediately evident to me that the popular BSDs (or at least FreeBSD and OpenBSD) are of vastly superior quality (both in terms of design and code) to Linux. I understand why people use Linux instead (it's generally for the same reasons corporate environments use Windows: legacy, large userbase, and familiarity), but it is definitely the case that by all my metrics, the BSD programmers have every right to be critical.