skysight-inc/HackerNews huggingface dataset:
Yes, and the theories which seem to be nonsense according to most physicists I've read.

If you stick to the pure experimental aspects of "we put a microwave in a can and obtained these anomalous results" and ignore everything else, there's something interesting there that bears investigation.
Doh! Was wondering what the /s meant ><
In layman terms, "Extraordinary claims require extraordinary proof."
Anatomy of a Go Web Application
You don't often go from "nothing" to "proof it works" in a single iteration of a new technology.
Just a reminder that a marketing practise may aggressive and unwelcomed by some users while also being statistically successfully on some other users and bringing significant revenues.
>I still think it's wrong of mainstream science immediately reject Cold Fusion/LENR or even Em Drive research.

You have to focus on something - there are only so many grant and R&D dollars to go around
Indeed, if you look at the history of science, even modern examples such as the discovery of H. Pylori, it's a messy process. However, don't be confused by survivor bias: almost all extraordinary results turn out to be experimental error.
DoorDash loses money on almost every meal it serves.

Uh oh.

We're headed for a big crash in "just in time services that lose money". Remember Webvan and Kosmo. The business model of all these guys, including Uber, is "achieve monopoly, crank up prices". Probably not going to happen.

The experience of Austin, where Uber and Lyft pulled out over the driver fingerprinting issue, is instructive. Within a month, six competitors were up and running. The barriers to entry in this area are low. Even if someone does get market dominance, they can't raise prices much.

Uber is particularly vulnerable because their latest capital infusion of $1.5Bn is high-interest debt, not equity. That's an axe hanging over the head of a money-losing company.
> Anyone else got some docker war stories?

Yep. Wrote a blog post about that :D

https://thehftguy.com/2016/11/01/docker-in-production-an-his...

What systems/OS/docker version are you running?
These are all well-known things in simplicial geometry [1] which is used everywhere in computational topology and discrete differential geometry. It turns out all of these operations can be done efficiently by considering a matrix over F_2 and considering its several forms. These manipulations lead to a natural (computable!) discretization of differential/topological methods because they're fully constructive and have beautiful theorems. I'd highly recommend looking into it if you're interested.

There may even be a nice way of taking elements from the algebra and extending these definitions to fit this idea of '∂' or closure or interior, etc; but I have little intuition for what the algebra might look like and whether it would admit nice expressions of this (personally, I was more motivated by the possible connection to computability theory and languages). Once I have some time, I may sit down and toy around with the idea.

-----

[1] https://en.wikipedia.org/wiki/Simplicial_complex
Agreed. However, rather than ignoring the experiment, I think it would be better to encourage scientists to understand why.

“Whatever Nature has in store for mankind, unpleasant as it may be, men must accept, for ignorance is never better than knowledge.”
― Enrico Fermi
async/await in C# is pretty nasty and usually overused and overhyped for nothing but downside. It screws debugging, it screws call stacks, it dictates you to write bad code and it's just plain complicated. It infects your code up and down the stack and every new method MS now releases seems to be .SomethingAsync().

I likened it today to having a garden hose in a Victorian sewer but then declaring the sewer is the bottle neck, async/await to the rescue!

Most people use it in totally inappropriate scenarios, for no good reason but adding a load of complexity to your code and debugging.

But your sewer is now even bigger! Look at how you can throw that hose around!

I was working on a code base where the old developers had started going async/await for 'performance reasons'. Cue me ripping it all out, actually fixing the performance problems and downsizing the client from a P1 to a S1 in azure with 3x the load and vastly better page load speeds.

It's almost always a premature optimisation. My opinion is don't ever use it unless you actually know what the specific bottleneck is that async/await will fix and you actually need it.

async/await in javascript is actually useful.
Wow. I remember scanning this writeup when it first became public, but looking back over it, I'm certainly struck by the author(s) seeming desire to educate their audience...
Top 6 Apps for Android Antivirus and Security
(So many typos above. "html4lib" should be "html5lib". "Seralizer" should be "serializer". "Previously-send" should be "previously-sent". Sorry.)
Lean UXmas 2016
Morpheus was close to the truth but misunderstood (wouldn't be the last time, right?).

The machines were harnessing the unused parts of the human brain to create a gigantic supercomputer, but one that was capable of intuitive leaps, blah, blah, blah, lost interest....double backflip scissor kick to the face. Whoa did you see that?
All watched over by machines of loving grace...
I didn't suggest ignoring the experiment. I'm just setting a baseline for how important this result is.
It was short for the explanation in the following paragraphs (OK I should have added "without unwanted storage side effects" which was the whole point though). WHich I still haven't seen resolved in a memorable/non-gross way (I do assume extempore's hack works). Even Martin's private[this] idea from that thread was apparently never implemented, I just tried it also.

I'm a Scala fan by the way, and this is a solvable problem (the private[this] solution would be fine I think). But it's currently a landmine IMO and an unfortunate because it's such an unforced error.
GNOME loves to cook
It's correct that these blobs are loaded way before GRUB or a Linux kernel gets booted. To be precise they are part of the firmware image; UEFI refers to a boot protocol specification. So for example with coreboot, you can select one of many "payloads". Payloads include UEFI boot, MBR boot, etc. So it's probably best to distinguish between the boot protocol and the firmware package as a whole.

The ME firmware is loaded by the CPU itself before anything begins executing; there's a header in the firmware image stored on the CPU to let the CPU find it. These are cryptographically signed, so all projects like Coreboot can do is incorporate the binaries provided by Intel.

The MRC/FSP blobs are executed by the x86 firmware, they're x86 code which runs very early. Theoretically projects like Coreboot could replace these blobs with their own code, but it would require reverse engineering these blobs to figure out what they're doing. The fact that this would be a major effort is a testiment to the complexity of the initialization routines implemented in these blobs.

The order is basically something along the lines of:

1. CPU loads ME firmware, verifies signature, starts it running on the ME coprocessor.

2. First x86 opcode is executed; this is part of the 3rd party firmware (Coreboot, AMI, etc.)

3. The 3rd party firmware will probably start by executing the Intel MRC/FSP blob. (Possibly this blob even expects to be the reset vector now, wouldn't surprise me; I'm not an expert on this.)

4. The memory controllers/chipset/etc. are now setup. The 3rd party firmware can do what it likes at this point.

5. Typically, firmware will implement a standard boot protocol like MBR boot or UEFI boot. Coreboot executes a payload at this stage.

I should add that microcode is another (signed, encrypted) blob. Modern x86 CPUs are so buggy out of the factory that they're often unable to even boot an OS unless a microcode upgrade is applied, so 3rd party firmware often performs a microcode upgrade before booting. Historically I don't believe it was uncommon for the OS kernel to perform a microcode upgrade, if configured to do so because a newer microcode was available than was incorporated in the firmware; Linux has functionality to do this. However I seem to recall that late (kernel boot or later) microcode application is being phased out; recent x86 CPUs want microcode updates to be completed very early, before kernel boot.
This sounds more like like it treats the symptoms than the cause, as I thought that the cause of a disorder like this originates from the gut and it's bacteria..
Don't confuse OpenID and OpenID Connect.

They are very different things.
OK...but Google and my bank still use OTP over SMS to two-factor authenticate me. So clearly there's room for discussion and evangelism here. NIST can say that pigs fly, but until I see it in the wild I'm going to take it with a grain of salt.
Found 2 minor bugs between the builder and the downloaded version:

Body Styles break with multiple paragraphs - http://imgur.com/YOjjGkB

Emoji break when you change them - http://imgur.com/FE8VUgH
Maybe I'm naive, but it seems incredibly impressive that the 6502 only has that many transistors!
How to Install PXE Server on Ubuntu 16.04
Clicking through these out-of-order, I happened upon this one: https://www.youtube.com/watch?v=SWR5Z4HWxbM

It's definitely different from the others on the list, and I quite enjoyed it :)
You can add Uthapam & Kothu Paratha to the list.
Je teste un salon d'aéroport
Or even better: google accounts with the Google Authenticator on your phone, then require a Duo push auth. ML with some hard rules for when to require a second or third factor, like "always" when it's an admin account.
"Everyone, shockingly, wants convenience. And as a result, it's our job to find the ways to fulfill that." - said every consumer internet company ever.

Demand does not beget a sensical business model.
Reflects my limited experience with them as well. We ordered, and waited, and waited, and waited. Eventually I called them and was told someone had messed up the order and the restaurant needs at least another hour to deliver. I gave up.

I love the idea of quickly ordering lunch for our employees on the app - DoorDash just needs to ensure they meet expectations. Just do what Dominos does already. If they do that well - I'd love a reminder at 11 am with our favorites listed where we can check out in 3 taps. And they need to really ensure Uber quality execution.

Given the current state, I feel like they're missing out on a massive opportunity by not fixing genuine customer issues.
Sure. Just put something on your resume that gives a recruiter some confidence in your capability with respect to those data structures and algorithms. A computer science degree is only one way of doing that.
I'd be keen to see a comparison of transistors counts between modern and older processors with caches removed (I could be wrong, but I thought built-in caches made up the majority of transistor counts nowadays). That is, how much more complex is a single cache-less core now vs then? Not as much as the overall transistor count would indicate, I suspect.
Clonezilla: Disk Imaging and Cloning
Mark Papermaster[0] should formulate that law.

[0] https://en.wikipedia.org/wiki/Mark_Papermaster
And those dollars should be spread around to different ideas not just to research that which we assume to be true.
You're comparing a single-core to a quad-core. Moreover, the Skylake is an SoC that contains stuff other than the CPU cores.
I seem to remember that the 68000 does something similar, using a 16-bit ALU to implement an ISA with 32-bit registers; part of the performance gain upgrading to the 68020 was shaving off the extra cycle from a bunch of instructions thanks to an actual 32-bit ALU.
It only says "including" SMS OTP. If the study is based on Google internal use, it probably also includes Google's OTP app.
I have the intuition that the plans of the developers of the future version of JS are that you will always have to transpille the code.

https://youtu.be/3pKNRgResq0

On the other hand, I think that the time of CoffeeScript has passed. It made some sense before Babel but now, IMHO, it is only for Ruby developers who don't like the syntax of JavaScript.
You forgot "including"
Also let's not forget the Lugano report, an independent attempt at reproduction of Rossi's E-cat claims. It produced more heat that was put in, and the isotopes got formed.

http://www.elforsk.se/Global/Omv%C3%A4rld_system/filer/Lugan...

And later reproduced by the Russians, with similar results:

https://drive.google.com/file/d/0Bz7lTfqkED9Wdm1NeEtxMFJLTmM...

https://geektimes.ru/post/243787/
We already know for a fact that quantum mechanics is an incomplete theory. It fails to accurately describe gravity. A fundamental force of nature. Therefore we should expect that it fails to explain other phenomena as well.
A popup which shows this dark pattern. Try it again in a private/incognito tab since it'll only do it the first time. Or don't bother: it's not exactly super exciting.
JWT = Json Web Token. That's not an authentication protocol at all. It's about using authentication tokens and JSON, which everyone's been already doing for years.

SAML = Security & Authentication Mega cLusterfuck. It does get the job done, but it is the hell of a beast to understand and use.
If all the factors are on the same box, it's just one factor.
The security of these is actually somewhat DUE TO the low adoption rates. If all of my consumer services have SMS 2FA, attackers will currently just move on to the next account in their list. It's similar to the spam game: it doesn't have to be perfect, just enough to make it not economically viable to spend the time required to crack it. Once everyone has SMS 2FA, I'll move on to push or U2F and be ahead for another decade or so. It's just important that people are given an option, so lazy / don't know any better consumers can do the easy thing and get their accounts stolen, while people who actually care / know enough to know they should care can stay somewhat safer. The unbalance is unfortunate, but until we figure out a way to ACTUALLY secure things which companies will get onboard with (related: the US uses chip cards now...but still only requires a signature facepalm) staying one or two steps ahead of the general population makes you pretty safe against everything except targeted attacks.
Can AI Finally Help Humans Choose the Right Gift?
That might be my favorite Ted Chiang story overall. Unfortunately Hollywood couldn't touch it with a ten foot pole, so I'm not expecting a movie out of it any time soon. His biblical fiction is quite good as well, and I could see them getting movie adaptations.
You mean the same make that has multiple abstractions built on top of it (cmake, scons, autotools, etc...)?

Snark aside, just because a product exists doesn't mean it's perfect, it doesn't mean that it can't be improved on.

Gulp is significantly easier to work with than make for many usecases, and tools like webpack aren't really comparable to make.
Well, if it's experimental error, then we learn a bit more about how to properly and carefully conduct experiments. If it's not experimental error, though...

Unfortunately, you have to look into it carefully to find out whether it's experimental error or something more interesting.

And, to return to Everhusk's first post: Experimental error can result in an "anomaly". The experiment is not returning the results we expect. That's an anomaly. An anomaly doesn't have to be new physics.
But you cannot get to extraordinary proof of you immediately reject the idea.
OTPs must be phished and then used very rapidly. The ROI for a successful phishing is much lower: a database of old OTPs is much less useful. (I'm sure you could use that to break the secret, but it's definitely not storing the secret.)
My favorite cluster algorithm comparison:

http://nbviewer.jupyter.org/github/scikit-learn-contrib/hdbs...
Somebody posted a great educational video narrated by William Shatner in the late 1970s: https://www.youtube.com/watch?v=VJmero_L7g0 (14 mins).

Shatner plays it pretty straight here, and he does a great job of making the subject mattter interesting to audiences of the day. What's interesting about the video now is that every time he promises us "Thousands of transistors on the head of a pin," you can remind yourself that what we actually got was billions of transistors.

It's humbling from a software engineering perspective to contemplate how poorly we're taking advantage of the semiconductor industry's Promethean gift. My computer still looks a lot like the Apple IIs and TRS-80s did in that video, and the same is true for my workflow.
Buy skihlz shoes for kids year-round
Just so you know, you can also use Google Authenticator if you really dislike SMS. Make sure to back up those emergency keys though, and read about encrypting your iTunes backups so it'll actually back up the GA settings.
Show HN: Run a local AWS Lambda server for development and testing, transparently
Why do these companies always phrase it as "our next step" or "what we're doing next"? As far as the outside world is concerned, Pebble is dead. There is no "next step". Maybe those same people will go on to work with Fitbit to make similar products, but they are abandoning their existing product.

I hate spin for the sake of public relations.
I don't really think that Bluetooth is an industry-wide practical prank that's gotten totally out of control (you weren't let in on the joke, and I wasn't either), but I do think that it's nearly indistinguishable from one.
Cool project. Virtual machines and assembly are always fun.

Not sure if the C compiler is quite ready for the headline, though. I was trying to get the test.c program to run on the vm, but after compiling and assembling, the vm just hangs. Is that expected?
I did read the article, and if you have to say "no offense", then it's because you're giving offense. The bit you quoted is literally what I quoted, just with more (irrelevant) words quoted at the beginning, so I don't know why you're even accusing me of misquoting anything.

The real problem here is the fact that the title of this post was edited multiple times, and now bears very little resemblance to what my comment was responding to. The original title alleged that Google said FIDO U2F Security Keys were better than OTP, without any mention of the fact that the article was only comparing it to SMS-based OTP and therefore the headline was inaccurate because OTP does not mean SMS-based OTP, and I expect (well, I hope) that most commenters here don't even use SMS OTP but instead use TOTP with an app.

In any case, I did edit my comment to mention that the title has changed, so the fact that you're saying I'm wrong immediately after accusing me of not reading something is pretty hypocritical.
I think you may have not entirely understood where he was going with that. It's a metaphor for entropy. It's actually a much more poignant and beautiful topic than something as short-term and universally inconsequential as climate change on earth.
Apple just broke it's secrecy law
I have friends who went to HR, and my personal perception is that bootcamps are a bubble bound to fall on their faces. They have been aggressively expanding for as long as they have been around, and I don't think the market is keeping pace. 100-125 is the number they advertise, but we won't know when that number has fallen until the 12 month average has fallen significantly.
Almost every time I've implemented a graph algorithm professionally, it's been using matrix operations because they came with a GPU implementation and smashed the performance of a naive implementation.

But from a design and theory standpoint, I prefer to work independent of the representation as much as possible, and only switch in the matrix language as an implementation of a type in already working code. (Sometimes, this isnt quite possible and you need to, eg, reorder operations to make it efficient to calculate in your representation.)

So I would say that linear algebra is a big deal for implementations, if not as much of one theoretically. (Mostly cause my computer has really fast linear algebra chips/code, and not so much for random graph traversal.)
Someone on HN explained this very well recently: that food delivery is the perfect business for duping gullible investors, because you can book the entire cost of a meal as top-line revenue, even though it passes straight through you to the restaurant. So if someone orders $80 worth of food, that's $80 that you can show off on your Series B pitch deck even though your profit after delivery might be -$5. It's not even like the Uber theory of "we're spending to grow", it's "we're spending to make more money that isn't ours look like ours", with the losses expanding in lockstep. I agree that a major bust is incoming.

Edit: "gullible" may not be the right word. It's more like this is a clever hack to exploit how tech investors are complacent about huge losses, as long as revenues are growing too. That's not inherently a bad thing, sometimes this approach is a good way to build out a healthy business. But the food delivery outfits are carefully exploiting this and hoping they get pattern-matched to other business models where it's OK, even though their situation is not the same at all.
Preaching to the choir here, but I would like to voice my strong dissent towards this move.

Trump and his cabinet directly effect everything HN stands for: the planet, space exploration, online surveillance. These are not "off-topic" at all. In fact, I'd go as far to argue that even this week-long ban should not touch anything to do with climate change. Climate change is science, not politics, and what Trump does now (see: EPA pick) affects this like nothing else.

Please let this be an experiment and nothing more. I come to HN to have a discussion on a wide range of topics, including politics.

Thanks.
Yes, Skylake is superscalar, hyperthreaded, multicore, SIMD, OOO, speculative and a few other things too.

Yes, Skylake contains GPU stuff in its transistors and also in its documentation.
Yes. Its a bug with 'ret' - try test2.c
Detailed explanations of state of the art techniques. Huge archives of learning data. Massive amounts of cheaply available computing power. All of these are available to anyone on the internet. Anyone can get involved.

However, not everyone has equal skills, experience, and insight. And as you'd expect, the people with the best of all three are highly credentialed and are being paid highly for their valuable efforts by companies which an afford to do so.

The days of an untrained tinkerer in a back shed contributing to the state of the art are long gone.
This is cool because it's in Haskell, but there are a bunch of great formal theorem provers, coq (https://coq.inria.fr/) being one of the most famous ones.
GETMAIN, the malloc() equivalent in MVT-derived IBM OSes, does not always zero memory. IIRC, MVS didn't zero it at all, so you might get anything in there, thus the need for a call that guaranteed zeroed memory for it. (This is from my memory of assembly programming on MVT/MVS up to the 1990s; z/OS apparently[1] does it somewhat differently now, so that some allocations are definitely zeroed.)

[1] http://www-01.ibm.com/support/docview.wss?uid=isg1OA28314
Partial quoting an article to the go on to disagree with the core premise and good security will net you no sympathy from me.

But the burden is on you to update it make it clear what you're referring to. If you think that this is truly unfair then I apologize for only reading your post and the linked article and not the entire historical context.

But I think even without that, you went on to make a point counter the article using article text as if it was a valid counterpoint is wrong.
To be fair that assumes you have node and npm set up properly, including making them upgradable, making sure node_modules is in PATH, etc. I think it's easy to forget "obvious" knowledge like this that (for me at least) had to be figured out with some trial and error.