skysight-inc/HackerNews huggingface dataset:
An important note: as much sulfuric pollution as all the cars in the world. Which is bad enough, but -- for instance -- cars are (probably) still winning on CO2 emissions.

For those who don't follow the link, the 16 ships in question burn the sludge that's left over after refining all the cleaner burning bits out of petroleum. So it's not so much a "quantity of fuel burned" problem as it is that they're burning the worst possible thing you can burn, as far as this sort of pollution goes.
I love how there's no way to stick out from the crowd, you could be selfish or selfless when ever you want and no one will be able to recognize you as soon as you blend in with the other cursors. Only you know how you behaved.

I decided to be one of the dancing cursors pointing to the right exit on the early stage, it was so fun to watch the difference in throughput when someone was dancing vs not. Almost everyone went straight for the dancer if there was one and just went 1 by 1 otherwise.
You could cite sources on "probably NSA-backdoored" P-256, but they'd all boil down to "you can with some effort devise a scenario in which it would have been possible for NSA to influence the curve selection". You'd be in a very similar rhetorical position to the "controlled demolition" conspiracy theorists.

We should, of course, demand rigid curves, and very few of the mainstream curves are rigid. But there's a difference between that and the assertion that P-256 is "probably backdoored"; for one thing, the latter assertion encourages people to adopt RSA, which is more fraught than ECC.

That RSA vs. ECC issue is even worse in browsers, which I think makes your sentiment even less useful. In ground-up implementations, you can get some comfort from OAEP/PSS for RSA. No such help in TLS, where RSA still uses (terribly broken) PKCS1v15.
> The problem (to me) is the criminalization of porn and prostitution in the US.

Porn is illegal in the US?
Subtítulos.app is same but for mac desktop.
Very nice game, I just wasted a bit of my time trying to get through the levels :) which is always a good indication if you ask me.

On another note: 1) can you provide 1/2 links to the JS cursor API behind the game? 2) Do you plan to open source it?

Keep up the nice work
I made oroboros for working with large collections of app and server configuration that need to be shared across many systems.

Previously I had been using an automation tool to template my configuration variables and found myself frustrated that I couldn't access their processed values outside of the tool.

Oroboros exposes all configuration as JSON over HTTP by recursively templating & assembling configuration files under some directory. This makes it simple to track & release changes through version control.

This project solves a particular need of mine, hopefully someone else find will find useful it as well.

Happy Hacking,

Thomas
Very smart crypto implementors are already working on this codebase, aren't they?
It's great, the second time I played it I started drawing arrows at incorrect exits at the one level where you have to pick the correct one or be sent back. When I started there were about 10 people in the level and everything went quite smoothly since there was the occasional person pointing an arrow at the correct exit. By the time I was done there were at least 50 cursors in the room and it became completely chaotic. People started crossing out my arrows, and others joined me in my effort of drawing false arrows.
Riak[0] could also potentially be a good fit for your use case. Unlike Redis, Riak is distributed. I've heard of several companies in the POS space using it.

0 - http://basho.com/riak/
If you want a VPS with unmetered network you should consider http://scale.ninja
I have had this experience. In my case the bill was altered to $0 before I'd even got to the point in the conversation where I intended to ask for some relief. It most certainly doesn't cost them that much, and it's within their interests to keep customers coming back for repeat payments than soured by being forced to pay an exorbitant fee for something which was obviously not their fault.
That's some weird native advertising(?): http://i.imgur.com/qapXCSe.png

Did BMW pay the "devotee" to do this interview?
I thought it was going to be about data structures for circuit design.
Collect emails in something like aweber. If they give you their email it is ok to email them. You have an unsubscribe link at the bottom of emails, so if they don't want them they can just click that.
With respect to regex-dna, there is still substantial room for improvement in the Rust library. It's currently using a full NFA simulation (albeit specialized to native Rust code with the `regex!` macro), while the competing C++ library (RE2) has been tricked out by Russ Cox with a parallel DFA implementation. :-)
Could I give a mention to Threefish as well? It's in the same vein as ChaCha20, but it's a block cipher, based on modern ideas, is more capable than AES, and naive implementations are resistant to power/timing attacks by default. Yet, I rarely hear much talk about it. Half of the time I see it discussed, it's along the lines of "Hey, AES is looking really old, should I use Threefish in my new application/library?" to which people respond "AES is proven and still secure, so just keep using that." Personally, I find Threefish to be a beautiful algorithm; simple and effective just like ChaCha20.

Seems to me we've hit this local minima with various crypto algorithms. SHA2, AES, et. al are still considered secure, and almost no one has the guts to "risk" something new while the old stuff still works. Whereas before, we knew SHA1, DES, etc. were failing, so people were happy to jump to new algorithms as soon as they hit the market.

(Side note: I chose to use Threefish-512 in my hardware password manager project. It gets used in the disk and database encryption, so its built in tweaking is a godsend.)
Yes and no. Primary rays cache, but secondary trash. That's why CPUs are still king for that type of rendering.
Like digital audio software? Or equipment/hardware? Wave synthesis functions, synthesizer filters, what kind of technology interests you?
Minor suggestion: on the newsletter page, hitting enter/return should submit the form. It didn't on my browser for some reason (Chrome 36.0.1985.143 on Linux). I had to click the button.
Whisper CEO answers privacy revelations: 'We're not infallible'
> Yep, this is true. The only thing I concluded from this page is "I am an old time Debian admin, I don't want to learn another way to configure my system that is not a bunch of shell scripts, so I am gonna bitch about this decision and create a fork".

Yet the oddly amusing part is how systemd isn't difficult to learn. The only valid complaint against systemd IMO is its departure from Unix philosophy, but for some parts of the nix ecosystem, I can't help but think that boat sailed long ago.

I was hugely resistant to systemd when Arch first switched, but I learned to appreciate it (the simplicity of unit files won me over). This came about a year and a half into my journey with Arch Linux when I was still learning that the easiest way to use the distribution isn't to fret over change but to embrace it. Otherwise you'll be implementing fragile workarounds that break every time you update.

Though, journalctl still annoys me.

Sure, I can understand some of the hate directed to systemd simply on the merit that it does* do things differently--but it's hard to believe that the vitriol and insults from the anti-systemd camp are likely to help anyone's cause.

Personally, I like it, it works, I've not encountered the stability issues or other bits of weirdness some folks seem to insist regularly occurs (maybe it's distro-specific), but I'm also OK with being a statistical outlier. Or perhaps the anti-systemd crowd is disproportionately noisy.
> Due to an off-by-one error, this code fails to properly reconstruct the example text

What's your example? It seems to work fine to me on
"{all is well}{ell that en}{hat end}{t ends well}"
systemd doesn't care what it is starting, so you can hand it a shell script just as easily as anything else.

See item #4 on http://0pointer.de/blog/projects/the-biggest-myths.html
I believe it was for Jim Gray instead. http://archive.wired.com/techbiz/people/magazine/15-08/ff_ji...
My understanding of the issues with P-256 is that it's very easy for mistakes in the ECC implementation around certain points to leak information whereas with other curves it is not. Not quite "backdoored" but certainly not optimal in terms of security.

Edit: based on http://cr.yp.to/talks/2013.05.31/slides-dan+tanja-20130531-4...
Equipment and hardware specifically samplers and synths. Thanks for the reply!
Candidly and concisely: I think the arguments about the importance of differences between sexes and races are so dumb that the only way anyone could want to introduce them into a discussion is if they are in some way broken.
GM failed to perform an adequate hazard analysis. Faultiness is inherent in any vehicle driven for a number of years, and as we've seen a single fault can disable many safety-critical features like ABS or Power Steering.

The potential impacts of the failure modes of the key switch are quite severe, although in normal use the likelihood of any one is low. Because of the severity, some risk mitigation should have been in order regardless of whether the component "works fine" or not.
I'm for this move, choice is _always_ good, be it systemd or anything else.
> So I'm pretty sure my definition is closer to the original than yours.

It is most certainly not. You're free to study this fascinating topic further, or not -- but you're simply wrong about this. When feminists (who coined the term) say sex, they are very particular to contrast it, and its biological meaning, from gender, which is sex's social construction. So when it says "sex doesn't matter" it means "biology doesn't matter".

> the underlying concepts are the important point.

With that I can agree. And the big problem is that of slavery, or the Matrix, or whatever other analogy you want to pick to describe the extant social structure regardless of intent, and not the misogynic acts performed by individuals. The issue of freezing eggs obviously falls under the category of sexism (or not -- you can argue the claim, but not the careful categorization) -- not misogyny.
I don't know if you've played Shadow of Mordor, but even as an occasional game developer like yourself I was able to forget about the technology running the Nemesis System at times and treat the Orc Chiefs as though they had intelligence and history. You can easily imagine how that system works when you take a step back, but if something even at that stage can trick us I have high hopes for the next few years of AI / NPC programming in the next few years.

On a related topic, a lot of money has gone into graphics programming in the last few years as studios developed their own engines in anticipation of the now-current generation of consoles. I am hopeful that with virtual reality on the horizon we'll see improvements in AI and Physics, among other tech necessary to create a convincing virtual world.
Although not directly related to your use-case, I wanted to mention that we received a pull request [1] implementing a test of the Iron framework. Expect to see this in Round 10 of our framework benchmarks project.

[1] https://github.com/TechEmpower/FrameworkBenchmarks/pull/1101
To 'skip' the narrow passages:
google "Move mouse with cursor keys" ;}
programmatically: CGWarpMouseCursorPosition on mac
To them, the computer is a tool, not an environment, and to use it is to press buttons to get some tangible result you want from it, and the buttons you have are not buttons you are going to know how to change.

Your general point is correct, but the analogy you're using is incorrect.

It's not tool/environment, but rather, it's tool/appliance.

The fundamental cultural shift going on between many anti-systemd and pro-systemd people is that the former want the computer to be a tool, something that with proper discipline and skill can yield great things, whereas the latter want it to be an appliance - something that you fire and forget, and is meant to be inflexible and that "just works".

The problems, as always, are that tools have learning curves and often need to be composed into more complex configurations to yield more powerful results. Whereas appliances, although they "just work", they work only for predictable and formulaic configurations that the appliance explicitly expects, and proceed to break down and reveal their opaque innards when used for more esoteric or unusual situations.

In summary, the anti-systemd side wants to do things with their computer, and the pro-systemd side wants their computer to do things for them.

This is why there will never be a consensus. It's also why systemd opponents will often resort to stupidity like defending the messy hairball of SysV initscripts, while proponents will just casually look at unit file configuration being outwardly simpler and not think of the bigger picture.
It's true that P-256 is more susceptible to implementation flaws than other curves, because P-256 wasn't designed to be misuse-resistant, unlike recent curves where that was a design goal.

It's unlikely that any credible new protocol is going to adopt a NIST curve. They exist only for legacy support now. BULLRUN killed them.

Fortunately, in this case I think hysteria actually served a good purpose. I do not think highly of crypto standards, and these ones in particular were dragging the industry down.
Parallel rendering of an HTML page means an improvement of one renderer to 2 or more renderers. Writing a web server means possibly handling thousands to millions of concurrent requests, which isn't really doable with Rusts 1:1 threading model.

But the reality of concurrency and hardware is that all we have at the end of the day are threads anyway. So in Rust you could have a thread running an event-loop that serves your web sockets. People are building these sorts of abstractions for Rust but they are a work in progress as far as I know. MIO[0] is one such example.

Rust is a programming language for systems programming and "server side programming" is just a subset of systems programming.

0 - https://github.com/carllerche/mio
The Mono C# programs also use llvm ;-)

A more accurate comparison? A different comparison would be against clang.

The benchmarks game might well be described as "a good starting point" http://algs4.cs.princeton.edu/faq/ but let's not confuse that with some kind of definitive final analysis.

(Edit: Say what you disagree with, don't just down vote.)
Green threads (M:N) do seem to be available as a library though: http://doc.rust-lang.org/green/
It just surprises me that mainstream brands haven't embraced advertising on porn sites. There is no reason why there couldn't be a Hulu style high end porn site with real ads from like Budweiser, Old Spice, Mountain Dew, Red Bull, Comedy Central. There might be backlash for the first company to advertise but after that I can't imagine people would care.
Any relational DB will work but I would look at Postgres before going with MySQL.
Can you actually pose an argument in favor of Threefish? I have suspicions as to why Threefish, Twofish, Blowfish, &c come up in discussions like these, but rarely in discussions between actual cryptographic engineers.
http://www.pornmd.com/ is a very interesting site.

For one, it scrapes all the top sites.

For another, you can see what people search for in which region. I.e. I am in Denmark and danish people apparently wants to see danish porn. I wasn't aware of that.

For a third, they have a live-search which is quite interesting. (and amusingly, read aloud by porn actors here: http://www.pornhub.com/view_video.php?viewkey=1025156889)

For a fourth, they also have a chrome extension, which if nothing else is curious as the adult industry has so far shied away from apps and such (I believe because of regulations).

Another interesting take is http://www.porniq.com
The site speaks for itself.
In which case we don't need to debate who's spreading FUD.

But people who want to take part in a debate should expect be held to account for the things they say, and in the case of systemd a lot of people are spreading a lot of misinformation. That's forgivable, I make stupid mistakes and misremember things all the time, but it's sure starting to seem like there's a very casual disregard for the truth and with it, any possibility of solid debate.

Not to mention the usual crowd of trolls who are just happy to have something that'll start an argument.
Bronco, Explorer, and F150 rollovers -fixed by adding stability and Tire pressure monitors

Toyota's gas pedal and floor mat recall - halfway similar to this issue in that it involved very poor affordance (drivers could not immediately tell what was wrong, they thought they were pressing the break, but the gas was pressed as well)

GM Streetcar conspiracy

Cars from the Big 3 used to literally fall apart in the 70's due to poor assembly. (Welcome Toyota)

Ford Pintos in the 1970s had badly under-designed gas tanks that ruptured and caused fires in rear-end collisions. Media put the death toll in the "hundreds", NHTSA had a death toll of 27.

The scandal of the Big 3 killing smaller car companies like the Tucker 48.

Incredibly stupid design decisions like planned obsolescence.

GMs policy of "build a bunch of cars and make people buy them" from the 1970's to the early 2000's - responsible for peoples poor opinion of GM and competitors that followed the same mantra (It even bit Toyota in the mid 2000's)
Are there actually many alternatives at this time? SHA-3, and more recently CAESAR, still received submissions based on AES. Grøstl (one of the SHA-3 submissions borrowing from AES) was a top 5 candidate. Constant time, side-channel free algorithms don't seem to be a big issue for many people yet.
I would suggest that the author learn the language of rationality... starting with an analysis of correlation & causation. http://lesswrong.com/lw/khd/confound_it_correlation_is_usual...
Show HN: Flexible HTML5 drag-and-drop mixin for React with full DOM control
Bear in mind "uniq" only removes adjacent duplicates. On my machine:

$ cut -c 1-3 /usr/share/dict/words | tr 'A-Z' 'a-z' | uniq | wc -l

5089

$ cut -c 1-3 /usr/share/dict/words | tr 'A-Z' 'a-z' | sort | uniq | wc -l

3434

p.s. How do you do newlines on HN?
Facebook hits DEA for a fake account
> Google gets 100% of my searches

I switched to DuckDuckGo for the last couple of months. Works fine for 95% of my searches. The other 5 percent is related to local (to my country in Europe) searches, where Google is absolutely giving better results.
I think it is actually the opposite to self deprecating. The tone is the equivalent of an "ipsum lorem". He just wants you to focus in the big picture.
I didn't say it's bad to have a smaller business. I said it's bad to have a smaller startup. Because by definition a startup is a company designed to grow. If a business isn't growing then it's not a startup. Between the two extremes of being a Google or a barbershop, it's closer to a barbershop.

It also isn't as weird that I wrote that comment considering I alarmingly find myself falling into Colin's shoes as a single founder. If there's a trap laying ahead that I could avoid, I'd rather know about it sooner than later. It's not to disparage Colin that I wrote the comment. It's to learn from him. I like Tarsnap and I'm a Tarsnap customer.

If there's a way forward that is unexplored terrain, I at least would like to learn more about it.

I wonder how far YC pondered over this question actually. What do you do with the cpercivas?

This gutsy, uncompromising quality is a trait of successful founders. I'm curious to see what will happen.
I don't think that most of the problems stem from the NSA, most of the problems stem from the fact that security is hard, and we don't culturally have a proper appreciation of this.

We love complexity, we love adding features and wrappers and creating libraries, and when it comes to security this complicates things very quickly. You end up with massive specifications, layers of dependencies, and lots of code. And in many cases a single bug in the code can compromise the entire system.

In security, complexity is very much the enemy and we don't apply that mentality forcefully enough.

The crypto world is evolving quickly, and new vulnerabilities appear. Backdoors appear, ciphers get compromised, this or that RNG is shown to be flawed, etc. And when something that your application uses gets broken, are you going to know? If you do know, are you going to be able to swap it out for something more secure, or is that going to cause a lot of pain and dev time?

Lots of applications are going to prefer the single patch hotfix to the system redesign. And this introduces more weaknesses, because often the hotfix only addresses the single attack, and not the core vulnerability that made the attack possible. Future attacks may be harder, but they haven't been made impossible. (But... it's good enough, right? It'd be like, way harder now to create an attack... right?)

Building properly secure applications is hard, because it requires you to be minimalist, modular, and it requires you to pay attention to the latest security problems and be aware of the types of problems you can introduce when you implement something. Security is incredibly nuanced and you have to be properly aware of all the nuances. A single weakness in your entire stack can affect your whole system if you haven't carefully configured your applications.

Crypto is broken because crypto is hard, and application builders will take the easy way out, often without realizing that they're taking the easy way out. Although the NSA has been shown to be an issue, most of the problems seem to come from our own ignorance when trying to build secure applications, and there's no silver bullet.

Creating reliably secure systems is only possible when working with simple systems. Right now, the Internet is built with a ton of complexity. Operating systems are built with a ton of complexity. There are many libraries with different implementations and they all interact together in ways that are difficult to track. (IE shellshock... who would have thought that Bash would be vulnerable?). We aren't going to have real security until we melt all of this complexity away, and until we train ourselves to view complexity as an enemy, and until we culturally appreciate how difficult and nuanced security is. And that's going to take a long time and a lot of effort.
Salt is worth money. If you have a bunch of salty leaves, you should be able to process them and get the salt out.
That makes two of us! Porn en masse shouldn't be, but it is.

As for Stripe's size, they are a tiny, tiny drop in the bucket compared to the world markets. Heck compared to a U.S based hedge fund they'd be tiny. I'm guessing they have very little leverage.
Just grokking K had that effect on me ... I can't even estimate how much farther that will go if I had a chance to work with Arthur.

And I keep thinking "ignorance is bliss" might have been right in this respect - perhaps I would have been better off had I not lost my appreciation for the (now obviously sad) state of software construction. (Engineering it is clearly not, by and large).

But I wouldn't go back. Would you?