skysight-inc/HackerNews huggingface dataset:
I have not and do not defend anyone for their actions, whatever they are, consensual or not. I am responding to a flawed statistical model. You're free to judge whomever you want, though, including people who respond to flawed statistical models. You're also free to essentially accuse me of defending quasi-rapists just because I find a statistical model flawed. It's a free country, after all.

"Can't consent" is different than "lack of consent", which is different than "consenting", etc. Consent is a highly varied and complex subject. There's explicit consent, implicit consent, informed consent, implied consent, non-consent, consent agreement violation, consensual non-consent, re-established consent, etc etc. Legally speaking (Note that I am not a lawyer) in America, there's very few laws that determine what is consensual or not. Usually it has to be determined by a jury when it goes to trial. It's because of this that, legally speaking, having alcohol does not alone remove the ability to consent in all cases.

Non-legally-speaking, I think you missed my original point. Nowhere in my commentary, nor in the study, does it say that anyone was actually intoxicated past the point of being able to consent. It merely says that within the legal framework someone could have been held liable for non-consensual sex. All this requires is that the person was intoxicated (about .08 BAC, or 1 beer, in the US).

If you feel like condemning people for this, so be it. All i'm saying is a study that generalizes based on guidelines like this is flawed, amongst other things.
Google's share of search in the EU is above 90%.
I simply can't get Ubuntu 14.04 to hibernate and resume reliably. 1 out of 10 times it's dead on resume. The culprit seems to be fglrx (as usual), but no decent solution other than to give up on AMD and go back to Nvidia (not gonna happen).

We've come a long way since the first Slackware, but Linux on the desktop is still a hot mess, particularly in terms of WM. I sincerely wish we had less options, and some of the "it just works" from Macs.
Consumer DSLRs “dead in 5 years”
SOFT, Not SOLID: Beyond Traditional Hardware Engineering [video]
The theoretical method of strengthening doesn't matter. And it's not vs. current law; current law is already stronger.

The important thing is that lengthening is not appropriate.
Cool idea! Would be helpful to see their top languages as well.
Mark Zuckerberg – Why I wear the same T-shirt every day
We desperately wanted to get this in before release, but it didn't make it :(

I think there's algorithm work being done on the matching for this as well. After christmas perhaps :)
> Spicy food was historically used to mask food that had gone off (e.g. meat in hot climates).

Spicing food has a preservative effect, which is probably a more important factor in the spread of the practice than masking food that has already gone off.
Debugging is a bit of a challenge with promises.

Indeed, and that is why I am personally not really that bullish on promises, at least not how they are currently implemented. When you're debugging you want access to the implicit state-machine that the promise statement constructed, but at least in JS such state is hidden away in the `then()` function.

A good compromise (which I'm currently exploring in JS) is to make the state-machine navigable from the root, giving you the ability to examine it and mutate it explicitly during a debug session.
Same experience here with a MacBook Pro circa 2012. Often seems slow to re-establish network connection after sleep. I've seen this on a variety of networks. Really just an annoyance, but better management of this on my Mac would be nice.
Bitcoin guide
Contrast Fox/Gretawire's response (deleting her tweet) to Newsweek's (interviewing the parody account's authors).
It would be hilarious if Google then scraped your list of removed search listings.
I use a very low-power pair of reading glasses, though I don't need them. I have an optometrist friend (retired) who recommended it to reduce eyestrain.

I also use "20 cubed", a chrome app, to remind me to do eye breaks every 20 minutes. My optometrist friend also recommended eye breaks, nearly the same thing that 20 cubed recommends.
Could you link the "why is my go program 138GB!" article?
Year of Prominent Deals in Finance
This lines up with my experience with the two languages as well. Usually I could get Rust to be virtually just as fast as C or C++ while Go would be roughly twice as slow. However I still prefer Go due to the quick compilation times and ease of development.
> I spent several years in the Big Freaking Enterprise Java Web Applications salt mines [...]

I had to re-read your comment twice as I thought that there exists an OTS ERP for salt production.

PS. The company I work for actually grows salt.
Lob.com works very well
Oh great, now the chem trail nuts are really going to think they're right.
I'd be careful about introducing more caching to the ClojureScript build process - I've been getting some really strange errors occasionally, the kind that leave garbled errors in the js that the source maps can't decypher, that disappear after a full clean & rebuild.

I just released a site based on Clojure + Clojurescript, with the front end written in Reagent, and it was a pretty good experience overall. The above was my main issue with the setup.

I've written more about the experience here (it seems there's not much interest in the site here, but at least the writeup should be interesting to those reading this post):

https://news.ycombinator.com/item?id=8791129

(Edit: it has since got a few upvotes, only to be killed by I guess the voting ring detection. C'est la vie.)
> The next time anything will enter the public domain in the US is January 1, 2019.

Right, because Congress surely won't extend terms again before that.
Which is only meaningful if the vetting is for the sort of skills one actually uses day to day.
commodity DRAM is, well, a commodity.

You're essentially saying that producing DRAM that doesn't work like memory should, regardless of access pattern, is excusable because it's "commodity"?
:s/most/some
I did forget the network once, but no go. Also thought pw for wifi points would be accessible through the network prefs. I'll check keychain next time.
I have a question about bitcoin in general - how do transactions on the network get verified? Does it mostly happen through miners? If so, what happens when mining reaches the point where it becomes economically worthless to everyone except a few electricity thieves? Will there just be a massive backlog of unprocessed transactions?

Unless I'm wrong somehow, I could see this becoming especially problematic as bitcoin becomes more popular and the daily transaction volume grows. How does the bitcoin foundation/community plan to tackle this issue?
For me it would be much more valuable if the programmer knew that a tree wouldn't be needed at all if expressions were represented in reverse Polish notation.

However, in the last 30 years, I needed to process expressions at work and by myself exactly zero times.
Did you throw AMD APUs into the project, or does their lack of x86_64 per-core performance kill the advantage of the shared memory pool.
For those that are interested, this was done as a 2 day hackathon project here at work :)

You can read more here: https://medium.com/@Macropod/conceiving-building-and-launchi...
Probably more interesting is Rust vs. C++. Rust is actually beating C++ on several benchmarks, by a comfortable margin.

Go is a modern scripting language, stripped of the features that make scripting languages impossible to multithread and intrinsically slow, statically typed, and with things built on top of the multithreading. (The Perl/Python/PHP/etc series of languages is very heavy weight, huge VMs, dynamic everything, and while if you started from day one to write one of them to be threaded you could probably do it, bodging it on after the fact was virtually impossible. IMHO "dynamic everything" turned out to be a great deal more dynamic than was really necessary. But it was a worthy experiment!) Rust is a C++ replacement. Go is very fast relative to its real competition, but it is certainly not a C++ replacement. It also seems to me that Go is likely to converge on being easier to develop; I don't think Rust is going to get all of this quite for free. Both will sit on an interesting part of the bang-for-the-buck curve that is currently not well-occupied. That is, it is occupied, but it is not well occupied.
the newest DRAM parts being produced have this problem solved

How new exactly? The newest tested in the paper is from July 2014 and that still has the problem.
Yup. Asking poker, bridge, santase, chess, etc. rules at interview is tricky.
First scientific report shows police body-worn-cameras can reduce use-of-force
It's unfortunate ewindisch's post has elicited such a response. He clearly spent time trying to communicate clearly the situation at Docker and some of the security issues surrounding it. I could be wrong but it doesn't seem that you've spent a commensurate amount of time and through in your reply.

It's certainly your right to be snarky and negative. Perhaps that's how you've learned to address others whom you're offended by. But instead of insulting ewindisch by using 'marketing' as an epithet, can I encourage you to address the content of the post instead?

Clearly, by using the term 'marketing' you mean to imply that the content of ewindisch's post lacks the kind of content you deem relevant to sufficiently addressing this issue. Why don't you challenge ewindisch on this? That would be more constructive than saying that he's NOT the lead security engineer.
I was trying to avoid sounding pompous, while calling out someone else for being pompous...

It's a delicate situation!
Graph traversal is quite relevant to DOM manipulation. More generally, these sorts of "classical" problems come up more than one would assume at first glance.

I believe that understanding the theoretical backing is very important for making correct software design choices, at least at the positions I have held. Moreover, this base knowledge is a proxy for general awareness of complexity analysis and architectural trade-offs (why do we pick this structure over that?). I agree that we needn't consider single-source shortest paths every day when programming, but for companies that want to be sure they are making good hiring choices, this seems reasonable to me. Graphs, for example, come up so often in practice, which is why I refer to them as fundamental. It's not like we're talking about red-black trees here. Again, it's a proxy for one part of what makes a great programmer.
Thanks for leaving your Gist up there describing the process, Jed. I do some work in VMs, but still found it very useful.
Link is four oh four, but I assume you're talking about a string comparison timing attack? Those don't really work over a network on modern hardware. Most string comparison functions actually compare words (8 bytes), and string comparison increases faster over the years than network latency. For more info see the Time Trial paper by Daniel Mayer and Joel Sandin ( https://www.blackhat.com/docs/us-14/materials/us-14-Mayer-Ti... / http://matasano.com/research/TimeTrial.pdf / https://github.com/dmayer/time_trial )
The article reports that they found skeletons and coins. Why is it hard to believe that human remains and coins were found under a city where millions of people have lived and died? I think these findings are highly credible.
What's the tech stack look like? I have some node.js code laying around that finds users top languages based on GitHub's own API.
We took "Soylent" out of the title, even though it's a legit reference to the movie, because the word "Soylent" has a different local binding here, and its presence in the title would likely trigger an off-topic discussion.
Pure callbacks aren't universally useless. For instance, the qsort() API can use pure synchronous callbacks effectively: http://linux.die.net/man/3/qsort

The article doesn't advocate always requiring pure callbacks. It's just offered as one possible way to make it easy to reason about the correctness of using an callback API.
Or presumably this is the same as a 'trivial solution' in physics (normally zero)? Makes the equations work, but generally represents nothing happening.
Shameless plug, the company I (just started) working at connects producers with consumers. We handle the logistics of getting the fantastic products from our producers to you.

If you are in the sf bay, nola, la, or nyc, check it out at http://goodeggs.com

Here is the SF egg section (we deliver to sf, east bay, and the peninsula)

https://www.goodeggs.com/sfbay/dairy/eggs
Transaction Fees: http://bitcoinfees.com/

> The fees go to the miners to incentivise them to keep mining, which in turn keeps the Bitcoin network secure. They already get a reward of 25 XBT for each block they mine, but this reward halves every 4 years. The plan is that as the block reward diminishes over the time, it will be replaced by transaction fees.
Direct browser addressbar searches do make it much easier to use a site's own search. Certainly for Wikipedia my keyword search of 'w <query>' is used daily to find things.
The backend is Rails (https://github.com/macropodhq/gitr-backend), and the frontend is React and Fluxxor (https://github.com/macropodhq/gitr-client).

I'd love to take a look at that code, if you have it online somewhere - it'd be awesome to show that kind of information and use it to rank suggestions!
> 3 & 4. Aren't these solved by requiring ssl, which should be in place anyway for user-based interactions?

Not really. There's no way for the app to know whether the particular QR code it just scanned came via a browser session protected by TLS, using a particular CA chain, connected from a particular IP, at a particular time, or with a particular session id. Even if all that information were encoded in to the QR dataset by the server, and digitally signed, it still need to be verified and counter-signed by the browser before being displayed for scanning. All you're really doing is QR encoding a certificate chain at that point... but in order to do that your browser needs to be cryptographically paired with the app.

What you have right now is TLS CA-certified confidence going in to the browser and "the user thinks this QR code is cool" level confidence going in to the app. The user is a poor substitute for a certificate chain.

> Also, would you clarify what you mean by xsrf bypassing tls

Sorry. I meant XSS. If you can inject script in to a TLS protected SQRL page it's game over (you just replace the QR code with one from http://192.168.1.5/MrEvilProxyOnTheSameLAN/dynamically_gener...) then the IP enforcement, as currently proposed, will pass assuming everyone on that LAN has the same external IP. IP bonding is just a lousy way to emulate a decent session layer.... which is ultimately what HTTP needs to nail this down once and for all.
hehe or "Deadlocks considered harmful."
Back when BPG was announced, I mentioned here that the real headline was the idea of distributing a new image codec without requiring a browser change, and without requiring the format to be solidified.

So, it should be possible to emscripten (that's basically how BPG works - it's an H.265 still-frame codec compiled to Javascript) with Daala, and distribute Daala still-images even though it's work-in-progress. The best bit is when Daala improves, you just re-generate your images and distribute a new Javascript decoder.

Anyone up for this? Even if it's not as good as BPG (it's very slightly worse it seems), at least it's royalty-free.
I believe it's http://utcc.utoronto.ca/~cks/space/blog/programming/GoBigVir...

Permalink to the relevant section of the Go source, with descriptive comments: https://github.com/golang/go/blob/04cf881fbea55d5bca584c78b1...
Don't get it. Unless the wifi hardware fails to initialize i have never found Android to be a slow connector. Are we so stuffed with stimulants these days that we can't handle those seconds?
S3plz – A polite, minimal interface for sending Python objects to/from Amazon S3
> A good compromise (which I'm currently exploring in JS) is to make the state-machine navigable from the root, giving you the ability to examine it and mutate it explicitly during a debug session.

You might also want to check out the JS library q, which has support for stack traces that span async jumps if a promise errors out https://github.com/kriskowal/q#long-stack-traces
If I was using a Mac and a poorly supported closed source third-party device driver was causing problems, I would be more apt to blame the driver's creator than Apple. I also would not assume that my issues meant OS X was a "hot mess".
Just to add to that, India, perhaps learned from the 1970 famine (see the wiki on Green Revolution). There are more variety of rice today in India, than anyone can count. And people have appreciation for that. I often eat 0.45cm long rice, which is as fat as a worm, as well as 3-4cm long rice, that is cooked not as a delicacy but as a base of other delicacies :)

Mangoes are another widely diversified food item. We even have a mildly popular Mango Festival Tradition in different suburbs at the edge of Urban Centers.
Storing multiple copies is a cost but 720 is less than half of 1080, and every smaller resolution combined is also less than half of 1080.

The real pain is when you have to have redundant formats each at high quality.
Knowing that some eggs come out bloody and birds die is one thing. Handling those bloody eggs and dead birds every weekend is an entirely different thing. I moved on from that job and after a while just knowing was not as "traumatic" and eggs/chicken was no longer repulsive to me.
I find it kind of ridiculous that making a self-signed cert is still that hard.
Almost every other country except the US does not refrigerate eggs.

I've personally kept US eggs unrefrigerated for 2 months with no problems - none of them were spoiled.

Refrigeration is mainly for freshness (i.e. yolk firmness). It's not necessary to prevent spoiling.
> I think you should note in captions that each of your code samples came from Domenic's blog, to be polite.

I actually mention this in a footnote, but I will do what you have suggested to be clearer still.

> it should be trivial to land on a syntax that is as easy or easier to read than the JavaScript implementation. I think your final implementation hides a bit too much.

Can you elaborate how this syntax might look?
Yeah problems with mutexes are ultimately the fault of the programmer.

The point that the article is trying to make is that because callback APIs don't expose their correctness requirements and because their correctness requirements are externally defined, they encourage programming error like this.
These are some Reddit-level retorts. You're not doing yourself any favours.
Right, this is only about the freshness of the yolk. It has nothing to do with keeping the eggs from spoiling - they will not.
This is clearly not the place to ask this question about mining. This is a thread about a software development on a whole different side of Bitcoin. If you are genuinely curious about the theme of your question, and not just interested in derailing threads, you are very welcome to educate yourself at bitcointalk, the main Bitcoin forum. There have been thousands -if not millions- of man hours in thinking, development, research and debate about the topics you enquire about. Head there and find the answers, and if still in doubt don't be afraid to ask (on an appropriate thread).
I don't know, I feel like understanding Darwin and Evolution is pretty important whatever the discussion you are in. It seems like 11 people agree with me as well.
Indeed, I'm very pompous since I'm quite proud of what a modern linux install can do.

Sorry if I don't partake in this unwarranted Mac adoration.

Instead, I explain how to do the same on linux, and actual results when it's possible to do better (with among other things i915.fastboot=1)

$ systemd-analyze

Startup finished in 781ms (kernel) + 648ms (userspace) = 1.430s

Add ~1s to the above to start X with SNA if you prefer a graphic mode - and that's on a 2006-era laptop, a 8-years old machine, so color me unimpressed. http://en.wikipedia.org/wiki/ThinkPad_X_Series#X60_Tablet
More like: if all bed bugs are attracted to the trap, then no more bed bugs.
Except that this is not a callback issue. It's an issue of circular dependencies - callbacks are merely the chosen dependency injection vehicle for this particular item.

The message pumping example the author gives has the exact same issue. The core here is that two items (database & logger) are mutually dependant. That will always be an issue. It doesn't matter if your promises are circularly dependant, your context objects, your callbacks, or your globals.

Static analysis won't help - fully resolving circular dependencies is equivalent to solving the halting problem, IIRC.

And so the only way to prevent those dependencies is to constrain the design in a way that prevents circular dependencies. That's where the ad-hoc rules mentioned in the article stem from. They artificially restrain the problem space to prevent (classes of) circular dependencies.
Hi Jed, I was wondering what your VM box looks like? Any cool tools you would recommend?
Libraries like bluebird will give you pretty stack traces that track the sequence of then calls, almost as if it was a single sequential execution. This helps with debugging.

Alternatively you can use the yield-spawn method of getting rid of then() altogether. Then you get code that looks sequential as well, and the browser gives you nice stack traces.

This doesn't help with modifying values during debugging as you mentioned, but it does solve the problem of seeing the "caller" stack frames.
Just to add as feedback to that: I much prefer the Jpeg render of 2 things in particular in that sample image. First, the brownish stone on the lower-right corner. As we as the car tracks. Regarding the car-tracks, the rough look in the Jpeg render looks more natural to me. The stone is though only slightly better in the jpeg. For the rest of it, Daala wins! I specially like the thin, tall leave-less tree on the left.
Seems he is working for Intel on CoreOS, and CoreOS is pretty much built on systemd...
Before it was a marketing term, "Hacker" meant someone who tried to understand things at a deep level, and pushed that understanding into new techniques, uses, and better performance.

I assume thats why it was submitted.
I'd heard that the actual reliable sensors that can see through rain and such are like $50k+ so are not affordable in private cars, but a service that uses it all the time could. I wouldn't want to fall asleep with today's consumer-grade hardware, but you're right that even an autopilot that has to be supervised still has most of the safety benefits.
Yes, the core issue in the database logger example is that it's a circular dependency.

The point of the article is that callback-based APIs like this obscure the actual problems (like circular dependencies).

You're right that constrained designs prevents issues like these but callback-based APIs aren't inherently constrained. They allow anything to happen, which is why they conversely encourage errors like these (and are subject to pitfalls).
Yeah look, I get all the criticism. Point is, can this mutherfucker hover and land ass-down? That's all we want to see.
Of course, the callback doesn't need to be pure. It just need to be side-effects free with respect to the caller.
Combining SMTP and HTTP tar pits to proactively reduce spam (2006) [pdf]