skysight-inc/HackerNews huggingface dataset:
As someone who actively researches biometric authentication, when I hear/read someone saying that biometrics are "usernames" and not "passwords", I automatically think they fundamentally misunderstand what a biometric is.

A biometric is both a 'username' and a 'password' - for instance, when you access your computer/device/whatnot you type in your username and your password to identify to the system that you are requesting access (on mobile the account is implied). When using a biometric, the system will have a stored template (similar to a password) that it associates to the system user account, and in ideal situations you (the user) do not need to do anything other than be present to access the system resources. It's a difference between identification and verification. Do you go to your friends each time they ask you something and say "are you so and so?", or have you already identified who they are? Based on the video it seems that MS is starting to understand this difference. Check out the video at ~2:35. He sits down at the login screen, and it just opens the desktop. For consumer applications this is really the goal of any biometric system.

Now spoofing and biometric template data being stolen are still real problems. Unfortunately, spoofing is not a very hot topic in the biometric field (usually conferences only have a relatively small percentage of papers on the subject), but given more consumer applications I'm hoping more funding will start to head that way. Concerning biometric template data, no you can't change it in it's most raw format, your fingerprint is static..that's what so great about it. However, there are methods such as key-binding where the template is itself encrypted with a private key. This however leads to more passwords... In any case, it's unfortunately up to companies like MS to start paving the way to successful implementations - if the data breaches we hear about almost monthly (Uber, Target, etc) are any indication, your password is just as at risk as your fingerprint.
Missing Genius.com
I wonder if it makes sense to recycle some of the dead company concepts. Seems to me that some of them were simply "too early" ...
please go and apply. if you need inspiration check http://fundersandfounders.com/too-late-to-start-life-crisis/
Straight Outta College: 9 tips to win at startup life
I can arrange that, and give you your first cleaning for free. Drop me a note at doug (at) thehappyhome.co
Deep brain stimulation is being used in humans.

http://en.wikipedia.org/wiki/Deep_brain_stimulation

It's even being used to treat behavioral disorders.
That's a magnitude bigger than I thought it should. Guess it's time to move on!

J/K, is it possible to share what kind of hardware is HN running on?
Ask HN: What's the best way to build a paid subscription blog?
Anyone have insight into how Jessica Lessin built The Information on top of Braintree? It works very nicely!
How many unique users post per day? That is a more interesting stat to me.

The following is bad stats, more gut: I would discard 50-75% uniques as random inbounds or non-repeating (habitual) users, bots, people who have switched wifi links, etc. That's going to be a lot closer to reality. Even then, at say 1.5M monthly uniques, divided by 30 = 0.15M/3 = 0.05M = 50,000 daily uniques. I am hugely skeptical there's that many daily human readers and would tend to believe the community aspect would fail at that scale. Besides, we often recognize one another posting. I'd have guessed 10-20% of that, give or take, ie. maybe 5,000-10,000 dailyish humans, max.
Drosera Capensis
The difference is that the code may try to execute x = "Hello", and then call free(y) (in case the condition is messed up). So the code will try to free() the pointer to a string literal (because they share the same memory location in the union).
What area do you live in?
Yes, and the next step would be kinect-like 3D scanning and "video magnification" for pulse detection ( http://people.csail.mit.edu/mrub/vidmag/ ), but these too could be compromised with some effort.

That's why these should be used only as a replacement for usernames and not for passwords.
Background: I have been developing in Go for ~5 years, and Rust for probably less than 2 months.

- Both Go and Rust use bounds checking on arrays/slices (which means out-of-bounds accesses are not allowed).

- Go is garbage collected, so memory leaks cannot occur.

- Rust encourages an ownership/lifetime model, so memory leaks cannot occur.

- Go can still have data races between multiple concurrent threads. To catch them, you must use the race detector _at run time_. Note however that Go encourages communicating information over channels, and if idiomatic code is being written the chance of data races is next to none.

- Rust cannot have data races in most cases, as it's ownership/lifetime model allows for catching them _at compile-time_.

- Both of these assumptions are based on no external C or unsafe code being in the picture.

TL;DR: Very similar.

EDIT: I used the wrong terminology -- sorry. Instead of _memory leak_ I should have said _dangling pointers_ (memory leaks can occur in _any_ language, Go/Rust/Java/JS/etc).
This is quite interesting. I lived in Okinawa for several years and remember how loathe they were to associate themselves with the Japanese Mainland "Honshu" - even calling themselves "Okinawan" and not Japanese with adamant fervor. A lot of that relates to World War II era atrocities committed on the island, but, regardless, I think Okinawans see themselves as largely very different from the mainland Japanese even though they are citizens of the same country. That would be yet another distinction that I think this article sort of missed as it only referenced differences between far north and the rest of Japan.

Having lived in both mainland and Okinawa, the cultures are rather starkly different as well - Okinawa with a pretty typical, more laid back island culture and mainland with a bustling, busy one. In this regard, Japan isn't as homogeneous - both culturally and genetically - as the article would have you believe if the covered area were to include Japan's southernmost islands.
It was hardly the only job, especially considering Google's store didn't have the review process until just now.

That cut pays for the payments infrastructure, bandwidth to deliver the app files, etc. that you don't have to provide.
Name.com's nameservers had a huge outage that lasted about an hour a few months back now.

That's not the bad part.

The nameservers didn't just go down, they were misconfigured and were serving the incorrect records for all of our ~140 domains. They were resolving to some totally unrelated address we'd never seen before. And not with a 0 TTL.

Before emailing to ask about an issue they already knew about, I looked for their service status dashboard... They don't have one. I checked their Twitter and other social media... No mention of the issue.

To date they haven't released any information on what happened that I'm aware of. When I contacted them directly and asked them what had happened and asked if there was to be a post-mortem released, their response was simply that it was a "configuration error" and they couldn't give me any details about what had happened or what they're doing to mitigate it, but I had their word that it would never happen again.

As a registrar they've been decent (lots of issues trying to get some registrant info updated on our .CA domains...).

I would absolutely recommend someone more transparent for nameserver hosting however.
Yes,

but sorry, no one spunks out millions of dollars to get a happy accident. There are months of wranglings, negotiations, covenants drawn up, targets created.

Granted Virb might have been collateral, but thats the point of my question. Why, was it lack of interest, did it cost to much to develop?
Machine Zone (YC W08)

Source: http://blogs.wsj.com/digits/2014/07/16/newest-hit-game-maker...
So presumably a (default) broadcast Probe Request would not disclose saved network names but somehow this doesn't appear to be true? Hence my question?
Neither, because policy has largely been written to favor those who already live on or own a given patch of dirt. Most of SF is neither millionaires nor being displaced.
>happens to get into a block

Yea, that's the rub there, lol
I guess it's not just us nerds in our bubble who dislike it.
Safari bug saves Web page URLs in Private mode
I don't understand Bengali at all. I'm trying to understand your second sentence though. When you say "no one writes that way", do you mean nobody hits the keys for letter, followed by vowel-silencing diacritic, followed by another vowel? Or do you mean the glyph that results from that combination of keystrokes doesn't match how a Bengali speaker would write it on paper?

If it's the latter, isn't that an issue for the text input system to deal with? Unicode does not need to represent how users input text, it merely needs to represent the content of the text. For example, in OS X, if I press option-e for U+0301 COMBINING ACUTE ACCENT, and then type "e", the resulting text is not U+0301 U+0065. It's actually U+00E9 (LATIN SMALL LETTER E WITH ACUTE), which can be decomposed into U+0065 U+0301. And in both forms (NFC and NFD), the unicode codepoint sequence does not match the order that I pressed the keys on the keyboard.

So given that, shouldn't this issue be solved for Bengali at the text input level? If it makes sense to have a dedicated keystroke for some ligature, that can be done. Or if it makes sense to have a single keystroke that adds both the vowel-silencing diacritic + vowel ending, that can be done as well.

---

If the previous assumption was wrong and the issue here is that the rendered text doesn't match how the user would have written it on paper, then that's a different issue. But (again, without knowing anything about Bengali so I'm running on a lot of assumptions here) is that still Unicode's fault? Or is it the fault of the font in question for not having a ligature defined that produces the correct glyph for that sequence of codepoints?
Imagine a world where the British always write the lowercase letter g as a single-story glyph (http://en.m.wikipedia.org/wiki/G#Typographic_variants). The colonies start writing it identically, but after a while, they start writing it as a double-story g.

After a century or so, nobody in he colonies writes the single-story variant, and all Brits always do.

The unicode consortium studies the case and concludes that there is only a single g with variations in the way it is written. Because of that, it creates a single code point for the lowercase 'g' character.

Now, suppose a web page stores the text 'goto' in Unicode as the code points for 'g', 'o', 't', and 'o'. To write the code that renders that string, you will find you need to know whether the text is written in British English or in colonial English.
While I disagree I've seen people object to the for/yield on monads because "it doesn't really seem like a for loop". YMMV
Nothing 'prevents' information leakage other than writing perfect code 100% of the time.

If the argument is that you can write a program in Rust that tells someone something they shouldn't know… is that… what's even the argument here? Is that even a question?

But in that case, comparing against Heartbleed is pointless. Why not ask about SQL injection attacks? Or directory traversal attacks? Or OS privilege escalation attacks? Or listening on a port that isn't correctly firewalled? Rust won't prevent any of those either, because none of them have anything to do with the language being used.

Arguing that it's possible to write code that does the wrong thing is so pointless that I can't understand why this article was written other than as some kind of half-assed hatchet job.
This is ridiculous. "Survival of the fittest" is not about who is physically stronger but who is fitter for their environment. And since most human's environment is a human city, monetary wealth is basically higher fitness. I wish these articles stopped spreading the LIE and MISCONCEPTION of what "survival of the fittest" means.
I agree with your point in general. However, in this particular case, what you wrote isn't equivalent.

The explicit use of flatMap(Option.apply) in the first example is to deal with the case of address existing, but being a null string. Your code doesn't handle that.
For the first few thousand years of writing, you could write whatever you wanted. For example, you could make up a new alphabet if you wanted to. Or come up with symbols, like = or $ or @, which represented some concept previously expressed with words.

Moveable type, and then typewriters, meant that we had to decide upfront which characters could be used. That is, you could use any symbol you wanted, but you might have to cut it yourself, cast it in metal, etc.

Now, with the infinitely more flexible digital technology, we have achieved the ultimate level of rigidity: using a new character would mean petitioning a committee somewhere.
Contact me if you do! Check my profile. Would love to see the result.
I think the median age reflects the types of companies in the batch. I think in general, younger entrepreneurs take on Consumer, maybe marketplace, and perhaps some dev tools and hardware.

The remaining categories will likely have older, more experienced people
Ironically enough, trying to open this blog's main page crashes my Safari (on an older iPad) every single time. I guess that cute little 200ms header animation is too accidentally quadratic for my 'outdated' hardware...
They killed that brand ages ago. Now they're going to stop mentioning its name.
Well, assuming you run the JIT on its own code it could be considered conscious to a tiny degree. It can analyze it's code, but only at a very low level, with no understanding of how it works. Also it can change its own code, but only to improve speed, not to change its functionality.

But, you are right that it is possible to write quite simple self modifying programs that would be conscious with this definition. However, having consciousness without intelligence can't be very useful.
Nothing prevents you from licensing your code BSD while using GPL-licensed software. You can use what ever library or software out there which is GPL and if you always use BSD or MIT license, you can share your code that you wrote with whoever and for whatever purpose. People who receive it can then use your code for what ever, and only need to follow the GPL if that also use the code which you have not written.
Nah, he's just being Eric Schmidt. The guy is an utter douchebag who should of been fired years ago.
I don't get your point, what are you trying to say?

> What Tedbleed, as your article calls it, demonstrates is a bug similar to Heartbleed

Similar but very different in the severity.

> but I would suggest that thinking that memory safety ends all security issues is a not good plan.

Nobody said that.

> The key is Unless you venture into the (explicitly demarcated) unsafe portion of Rust, you will not see memory exposure vulnerabilities like Heartbleed: the language does not prevent this.

Sure, if you want to break it, you'll probably can, but you'll have all kinds of warnings before and the few lines where you actually do that, can be proofread the most times.

There's nothing preventing you from writing common bugs the generate vulnerability either, but that's simply not possible.

> Perhaps your post will stimulate Ted to go further with his example and write an erroneous complete TLS stack in Rust, showing how it too can do Heartbleed. Perhaps you agree that this can be done.

Well, Rust may have a memory leak at some point in the future, no software is perfect, but that is one language, that will be review constantly, that is mainly memory safe, the other is one language that is not memory safe where thousands of developers are constantly writing code, inserting lots of heartbleed/memory kind of bugs.

> Among the scariest mass vulnerabilities relating to total information disclosure, the Padding Oracle Attack, the BEAST attack, the compression flaw CRIME, none have to do with memory safety of languages. Rust there would not have helped one whit.

That's not the point of the article, ted tries to say that hearbleed would be possible, author contradicts this as it shows how the vulnerability would be of different severity.
Softimage & naiad would beg to differ.

Plus Max isn't fairing to well either...
Also do you find different job postings work better for different networks? Github vs SO vs Glassdoor.

Which networks have you found most effective for finding good engineers?
Designated initializers are one of a few indispensable features that make "C++ is a better C" a complete non-starter for me.
Build Newsletter: Open Source, IoT, and Devops/Agile Transformation–March 2015
> Now the Japanese people are understandably concerned about maintaining their traditions in the face of massive Western cultural influences.

I lived in Japan for some time and this sentence is a gross generalization. Some right-wingers in Japan are attempting to maintain their traditions, but the rest of the population either couldn't care less, or has fully embraced western culture. You don't have to look hard (or at all, really) to see the evidence. Speaking English is (and has been) considered "cool" and you can find popular music artists dropping the occasional English words in songs, in their mangas, anime or in their dramas. A walk around any city with over 20k people and you can see western influence quite literally everywhere. Nobody is rushing to tear it down or even denounce it.

There are a few extreme right-wing nationalists who might, but they're the fringe. They're smaller in size than America's Tea Party and should not be taken seriously.

> Thus, when Japan sent troops to Korea and annexed it in 1910, Japanese military leaders celebrated the annexation as the restoration of the legitimate arrangement of antiquity.

No, this is incorrect. At the very least, it's extremely misleading. China and Japan were fighting and both countries attempted to snatch up Korea as part of the first Sino war. It had nothing to do with their "restoration of legitimate arrangement of antiquity". That may have been their reasoning long after but it's not something any historians worth his salt would say was the reason for China and Japan's interest in Korea. See here: http://en.wikipedia.org/wiki/First_Sino-Japanese_War#Conflic...

This paper is actually probably one of the best papers I've read on the reasons behind Japan's imperialism during that time: http://wgordon.web.wesleyan.edu/papers/imperialism.htm

It goes over all of the possible reasons. The most likely of which, is that they were straight up emulating the West.
Show HN: DIY – JavaScript that compiles to a Makefile
"Survival of the fittest" needs to stop being parroted, full stop. It is not an accurate way to describe evolution and reproduction.

"Death of the unfit" (or failure of the unfit to reproduce as an identity for "unfit") is a much more accurate way to phrase it.
Not sure, but it might be helpful to look at the most recent YC RFS: https://www.ycombinator.com/rfs/

E.g., something that is vertical specific may be more "Enterprise" than B2B
I've played around with both languages and to my limited knowledge Go just seems like a more modern C language with a GC and easy multithreading.

Rust on the other hand is a completely different animal to anything I've used before. It has one of the most annoying compilers but that is for a reason, if your code compiles then it's memory safe (with a few exceptions, like 'unsafe' block)
Ted's original point about Heartbleed not being a violation of memory safety is bogus, because there is a configuration of OpenSSL (achievable with flags passed to ./config) where extended-sized Payload values cause the OpenSSL server to segfault with an out of bounds read. It takes a special kind of bravery to look at that kind of crash and say that it is not the result of a violation of memory safety.
I'm not sure how to best characterize it in the very beginning (and I wasn't there) but in the 3.5 years I've been here it has largely been smaller services -- even down to things like the app's nav is its own service. More recently I think we've really embraced microservices (the number of deployables has grown ~2x in the last year).

Personally I think after 5 (and definitely 10) engineers working on a single app I would look at whether you can break it down into independent services.
I would distinguish them as enterprise requires a top down sales approach, while B2B can be either, but more often is a bottom up approach.
The poster did not sum values. They used the loop to call into printf. I'm guessing they didn't also use those particular compiler options... What you have here sounds like a lot of tuning that does not apply equally for all scenarios.
It looks like Dataminr has had a different experience than Meerkat when building businesses off access to others' APIs.

I also think this is interesting in that an ecosystem company, Dataminr, has raised just as much money as the company that created the ecosystem (Twitter). Of course, this is a bit of stretch in that Dataminr is more than just interpreting tweets.
Chist ovarian TRATAMENTE NATURISTE
If you mean how many logged-in usernames, something like 40k and 100k.
If GitHub continues on this track of making content available directly in the browser, the use cases are endless as a service. When someone, and someone will, makes git accessible to the general public, features like these will propel GitHub into the general consumer space.
The headline is total clickbait. The abstract of the paper says:

"In contrast to demographic reconstructions based on mtDNA, we infer a second strong bottleneck in Y-chromosome lineages dating to the last 10 ky. We hypothesize that this bottleneck is caused by cultural changes affecting variance of reproductive success among males."

"caused by cultural changes affecting variance of reproductive success among males" is a reasonable hypothesis, since the bottleneck affected males more than females. But who pulled "wealth and power" out of their rear end? That's just one possible cultural change. And why would you lead with one possible version of a hypothesis rather than the actual data and results (which are interesting in their own right)?

There are lots of possible ways that cultural changes could have caused a male-specific pattern of reproductive variance. Maybe settling down into agricultural societies changed how (and how much) men fought and died in conflict. There are lots of possibilities; "wealth and power" is a total guess. But that's the part that makes it into the headline.
​Stable backups with the help of public services
Actually it's more like encouraging people to eat healthy by making it take 5x as long to buy anything at McDonald's.
Good point I was sloppy in my reading.

def getAddress(name: String): Option[String] = {
for {
elem <- database.get(name)
nullableAddress <- elem.data.get("address")
address <- Option(nullableAddress)
} yield address
}

def getAddress(name: String): Option[String] = {
for {
elem <- database.get(name)
address <- elem.data.get("address").flatMap(Option.apply)
} yield address
}

are both still better though.

Also it seems like a bit of a strawman to use such a pathological example (null values stored in a map are frowned upon even in Java-land) to motivate the entire styleguide section about monadic chaining. They say it's contrived but still -.-
Oh how fun it is to performance tune my data analyses
I hope you don't find analogies like that. It doesn't make sense to compare athletes to programming languages; that analogy makes no sense at all.

Also +1 to what @Padding says.
I've lost count of the number of times I asked someone what browser they used and was told "Yahoo."
I love StackOverflow careers. They are expensive, but draw a quality crowd.
Marking your code as unsafe lets you do a bunch of, well, unsafe things. So yeah, if you wanted to you could probably reproduce heartbleed in OpenSSL.
You kind of sound like a dick, are you sure that's not why he wants to leave?