skysight-inc/HackerNews huggingface dataset:
No the onus is still on the user. How does the onus move to the channel provider?

I don't see a difference in this and 'Reset your password' links in emails that are common place. They are basically the same premise, without the password.
Python and Ruby aren't dominant against C#, Java, and C++. JavaScript is in its own category since you kind of have to use it.
The Desert Southwest Is Burping Methane Like Nobody’s Business
This reminds me of a similar theory put forward by Edward de Bono a while back. He suggested it might be lack of zinc in the diet, caused by eating unleavened bread. He proposed shipping out Marmite to help.

http://www.independent.co.uk/news/de-bonos-marmite-plan-for-...
Wandealust Weekly: The Best Las Vegas Travel Deals for 10/8 to 10/14
> Didn't 23andme start out by offering disease and ancestry information based on SNPs, but then stopped disease prognosis due to liability reasons

They just stopped because the FDA told them to; AIUI they don't have any liability concerns of their own.
My assumption is that a "login key" is essentially a large piece of data that would be prohibitively inconvenient to use outside of an email account, text, etc. Analogous to a large session cookie without an expiration date.

In contrast, a password is designed to be used from any login point.

In this regime, unless the optional password is used, there is no hashed password stored on Mozilla's servers. Only a copy of the hash of the "login key" is stored, so the attack surface is considerably shrunk if you are attacking Webmaker users.
As a fellow coeliac I have also had those experiences, no idea what caused them but they went away with the gluten free diet.

After being gluten free for 10 years now it's so easy to tell when I've eaten something that contains gluten.
No. Government isn't the answer to most problems and certainly not this. The market fixes this. If you don't like the terms, don't use the app. As soon as "legislation" gets involved, then suddenly app developers are now under the same type of regulation that covers medical devices, etc. That's a huge burden. Imagine the patent trolls -- they use patent legislation to attack developers (often small indy shops) that "potentially" have infringed on some patent, despite the fact that the developer didn't even know a patent existed and the technology involved is sufficiently ambiguous as to be case based more on the financial resources of the participants rather than the merits of the claim.

With this permissions legislation, an app that does legitimately request a permission might have increased lawsuit exposure because of someone's interpretation of what the permissible purpose of that permission might be. Even if the developer is "right" they still have to spend thousands of dollars they likely don't have to defend themselves. We have patent trolls -- what's next, permissions trolls?

The free market is the answer. However, education of the public is necessary for them to realize the tomfoolery in which some apps engage. However, all the education in the world is unlikely to help -- this "general public" we're talking about is the same crowd that plays Farmville and Candy Crush.

iOS is a bit more "safe" in the privacy regards because each app must explicitly request permission for a specific use and Apple is rather rigorous when you attempt to use a permission outside the scope of the app. I don't know anything about Android, but if it covertly enables a permission without the user's knowledge, then that's something Android should fix. But legislation? Hell no. I don't trust legislators to paint white stripes on the road correctly, let alone pass laws about technology about which they are demonstrably ignorant much of the time.
New Studies on Leukemia Therapies
> What is your workflow that this would be any more difficult? The first time you sign up for a service you almost always have to do this anyway for confirmation. If you then select the "Remember me" path, your primary computer is whitelisted and you don't have to do the round-trip.

This assumes one (or n) devices that belong to you. I typically have to log into multiple services using a large amount of computers for work. In my use case this would be tremendously annoying whereas two factor I can simply log in like normal and type in the code from my phone's app.

> If you have two factor auth set up for your email account then you're already pretty well protected and having each and every service use a different two-factor method provides diminishing returns in security.

I disagree; it prevents someone from getting into my email due to a vulnerability and then being able to get into every other service I'm connected to. Each service I use would, ideally, have two factor (though I obviously do not think two factor is perfect but it's better right now than most alternatives in my opinion).
I think the question is, can 100% of children be brought up to read and write and do basic math? If so (and it would be pretty controversial to argue otherwise -- who are these genetically unhelpable children? maybe there are a few, but less than 1%), then the goal of "No Child" is at least coherent, even if the implementation was so poor that it could never have improved public education so drastically.
True, however it should also be common sense. Too many people expect something for nothing. The entitlement mentality. When a company that makes their money on target advertising offers you a free email account, it doesn't take a rocket engineer to understand that there's likely some reason for that "free" account. But, I'm convinced that 65% of the general population is as dumb as a box of rocks. That's the only thing that can explain why the Jersey Shore and the Kardashians made so much money.
As far as I can tell, the biggest threat to water in my state are the elected politicians. Certain municipalities are dumping raw sewage into the water. They claim it is due to not enough money to build proper plants, but they keep redirecting the money for other uses. There are now 2 specific taxes to address this, and still the cronies end up with all the money.
Preventing readmissions and reducing LOS with predictive analytics
Arguably, that's a problem with "junk apps" as much as "junk data".
The login key is in the article in the example screenshot[1]: 'hopping-smiles'.

[1]: http://notebook.ideapublic.org/wp-content/uploads/sites/5/20...
Unfortunately (and I say this as a member of the organization), I feel like the AOPA is fighting - or at least dragging its feet - on the issue, since transition to any other fuel is likely to add some kind of expense or inconvenience.
What Does 200B Stars Really Mean?
I forgot to mention that the main lisp implementations (SBCL) are fast. Compared to languages like these it's a done deal.

Good point about long term maintenance. Ruby and Python aren't that great either, people say static typing is the way to go. Lisps are weird because they allow to hot swap most of the things which makes changing a system easy, but at the same time it leads to spaghetti images.
There’s already an evil version of Tetris called Bastet (“bastard Tetris”).
Researchers replicate Alzheimer’s brain cells in a petri dish
Not a bad idea but the chief drawbacks I see:

1. Needs a very long-lived session to be convenient. Elsewhere they note their's is a whole year.[1] That's a long time to go without reauthenticating a client!

2. Authentication is or should be a much more common event than recovering a lost password, and now that's totally dependent on your email provider. One concern is latency.. a minute can feel like an hour while waiting to log in to your account to do something urgent. But also worrisome is provider downtime, spam filters, etc. all can block you from accessing your accounts.

Of course the way they "deal" with #2 is by just trying to avoid authenticating you very often (#1), which is not a generally-applicably awesome security practice. Might be ok in some cases but I wouldn't classify that as an overall "better" way to sign in.

I think a better way to solve this is at the browser/OS level with built-in password generation and management. And that's actually a third drawback to this approach.. it's incompatible with password managers.

[1] https://chrisdecairos.ca/one-time-passwords-pt-2/
The run time seems to be outdated... Hasn't the JVM been updated and optimized since 2000?
I think you're missing the point - at least how I'm reading it - the idea is the user friendliness, not that the techniques themselves are novel.

You're absolutely correct that PCR and DNA/RNA amplification tech is nothing new and is (relatively) very simple - to the point where I did it in high school biology (AP) 6 years ago and then a number of times in undergrad labs.

However I am not aware of anything that makes it this easy for a nurse/doctor to do in the hospital - as they put it "without the need of a specialized technician or expensive lab machinery."

There isn't enough information provided to know how useful it will be though. I can see some potentially interesting use cases where a nurse being able to take a blood sample and run a plate with results in an hour could save a lot of time and money. At the same time, it really comes down to the "patented biochemistry" and what specific markers are on the plates.

> On top of that, doesn't anyone else think this is a bad idea to try to test everyone for low incidence diseases? miRNA and sRNAs are OK markers for disease, not great and certainly not definitive. You're guaranteeing that most of your positives are false positives.

That is highly dependant on the disease in question, no?
Glenn Greenwald  TED: Why privacy matters video
It could be worst for apps that are not junk (need the permissions for useful features).
Agreed. To me the explanations as to how this kind of forfeiture work just feel like absurd doublespeak to try and claim that the Fourth and Fifth somehow don't apply.
No. http://www.thatdanny.com/2008/11/20/one-fewer-or-one-less-a-...
I'd be really interested in knowing how it compares against lazy.js: http://danieltao.com/lazy.js/
> And it tastes so so sweet...

You mean wall candy?
http://www.penny-arcade.com/comic/1999/10/18
I'm currently rewriting my Mac application. Its prototype was written in Qt, but I'm now dropping Qt for several reasons:

1. I demoed my application to my friends and they all complained that it didn't behave exactly like a native Mac application.

2. Qt5 has a lot of UI bugs on Mac OS X.

3. The LGPL license of Qt may not compatible with Mac App Store [1].

4. I could buy the commercial license of Qt, but it's $215/month for Mac OS X. I don't know if my app is going to sell at all, so I can't afford that kind of burden.

[1] http://blog.qt.digia.com/blog/2014/10/01/benefits-of-the-ind...
More technical details here from the post:

https://chrisdecairos.ca/one-time-passwords-pt-2/

I'm not totally clear about what the different between a "login key" (short-lived, pronounceable) and whatever is contained in these semi-permanent login email links (~1 year, presumably non-pronounceable).
The effort involved to get the right coloured trousers, shirt, tie, and jacket far outweighed the fares I should have paid..
If only I had specified the exact subset of users that would benefit most from reading my recommendation, then that might have allayed your concerns. Certainly, if it's not for you, then it's not for you.
I would say that people are moving away from Python / Ruby and going back to Java, JVM is very powerful nowdays.
> dominant languages seem to be dynamic languages like Python, Ruby & JavaScript

Where?!?

JavaScript is king for those that need to target the browser, that is for sure.

Now outside the browser? There are lot of languages to choose from.

Python and Ruby are surely not the first to reach if one needs performance.
Yes and no.
"Bestiale" means literally "beastly" as you said but it is often used in Italian to describe something really big (huge etc..), like "ho un sonno bestiale" (I am incredibily asleep) o "ho una fame bestiale" (I am very very hungry - ok in this case "beastly" could make sense as well :))
So I suppose in English you would use Total (or "such as" or anything else?)
Of course - and thats fantastic! There's one less place that people will trust with a shared password.

A very large percentage of users reuse the same password on multiple sites. If you do that, a security breach in any site will leave your password exposed on all sites. And if you're anything like me, you have an account on all sorts of tiny sites.

You really can't trust the security of any startup thats less than 2 years old, or less than 5 people. Most software engineers don't know infosec well enough to implement a proper password database and protect it. Most startups are only 'secure' because they're such small threat targets that they don't have much value in attacking. However, if those small targets store username and passwords that get reused on lots of websites, everybody loses.

If the 'reset password' link sends an email, users have to trust their email security anyway. If I have access to your email, I can reset your facebook, twitter, etc passwords then delete the password reset link & notification from your email account. Google is going to do a better job at password security than a 3 month old startup with 1 engineer.

Absolving mozilla (or anyone else) from keeping passwords improves security.
"In all, it costs around Rs3 crore ($490,000). “It’s still in the trial stage,” said Sharma, “And we are still getting feedback on it.”

While the website looks sleek, I'm not sure the what the expected ROI is on the 3 crores spend. What are we to expect of this system ? That government officials can be held accountable for not maintaining attendance ?

It reminds me of the very first job I held. Work would be allotted to me and I'd finish it in 5-6 hours and head home. I'd work an hour or two on researching how to improve our existing systems and implement them the next day. At the end of the week a manager pulled out a report that said I'd clocked low hours and I was punished for it. Those who stayed back to have tea and a late supper clocked more hours and were considered `hard working`.

Attendance != productivity or progress
VB.Net is about as verbose as C#. There can be no perf differences because they both compile to the same bye code. Assuming the dev knows what he/she is doing when optimising for perf in either language.
Code Here – A more personal way of learning to code
Thousands of Britons seek 'right to be forgotten'
Or the atari st! Like a mac only at 1/3 the price :)
That thing is fucking old.

The JVM has been improving a lot since then.

In order for that content to be taken seriously, the tests should be re-run with modern runtimes for both C/C++, Java and Lisp.
I think your views on the GPL are spot on. At least we can agree on that.
Giving up on ag is an extreme response. The more reasonable approach is giving up on categorically insane water use policies that actually encourage waste by (a) placing a trivial price on each farmer's allotment and (b) reducing their allotment if they "fail" to use every drop allocated in the previous year.

The drought is serious, to be sure, but the severity of the crisis is not a direct function of the drought itself. Rather, it is a function of a serious drought converging with a deeply corrupt political culture that allows an obscenely reckless and short-sighted farming lobby to maintain the worst policy imaginable.

So I actually welcome this drought. I'd be very happy to see our major ag players ruined by the pressure they're under. Given the damage they've done to California, I wish them nothing but suffering in return. And no, we are not "all in this together". Commercial and residential users who have been steadily adjusting to reasonable and climate-appropriate codes for decades have been doing their bit. Ag has not. Indeed, they've been going so far in the opposite direction that they're risking permanent collapse in the aquifer.

A characteristically Californian way of looking at the very real pain they're suffering is seeing it as major karmic payback from their corrupt and corrupting approach to policy. If the outcome of this drought is that we finally break the backs of these people (politically speaking) and free the people of California to make water policy in something other than the most inefficient, wasteful, and environmental degrading manner possible, then I'd say the whole experience is a net positive.

Indeed, if I were a religious person, I'd call the drought an act of divine intervention.
I implemented this style of login in the app I'm currently building. I don't think its necessarily appropriate everywhere; the reason I decided to use it is that its the type of service you very rarely log into. For things like that, a large portion of logins are (anecdotally) going to end up going through the forgot password flow anyway.

I will admit that not being responsible for storing passwords was one of the reasons I used it. I'm by no means a security expert; one less thing I can screw up seems like a major plus.
5 madmen lessons for entrepreneurs
I find myself counter to the popular opinion on the use of controllerAs for mostly semantic reasons (IMO, a controller orchestrates services, $scope included, rather than containing data or references to data), though there are obvious and not-so-obvious tradeoffs with either choice.

That said, this style guide definitely has the strongest (almost convincing) argument I've seen for using controllerAs and does not have the inconsistencies I've found in other guides (`this` is not bound to `$scope` as a couple popular guides claim). Good stuff.
The relationship between the ACT and SAT may be changing as the latter is watered down. Or at least MIT has found as of late the ACT is a better test for its purposes.
I too would "like to see [this approach] used and pushed further by other designers and developers."

I'm one of those who have been trying to do so. I created an open source approach called Handshake.js that is re-usable for developers. [1]

I presented this topic to a good crowd at JS.LA [2].

At the current time, I'm finding developers still hesitant to jump into the approach. Passwords are familiar and there are many developer tools/libraries to quickly setup the defacto username/password approach to authentication.

[1] https://sendgrid.com/blog/lets-deprecate-password-email-auth...
[2] https://vimeo.com/90883185
COWL: A Confinement System for the Web
FinFisher Malware Analysis – Part 3 (Last)
Texas Health Worker Tests Positive for Ebola + CDC Response
Wikileaks Meets Surveillance Valley: An Interview with Julian Assange
Axent Wear Headphones – Raises $705K in Just 4 Days via Indiegogo
LibreSSL 2.1.0 released
Lead paint and lead gasoline are shocking examples of corporate misbehavior.

Interior lead paint was banned in many European countries by the 1920s because of the obvious health risks. But in the US the lead manufactures responded to health concerns with "Dutch Boy" lead paint, deliberately marketed to appear safe enough for a child to use. They actually had advertising campaigns promoting lead paint for childrens' toys, cribs, and bedrooms. Household lead paint not banned in the US until 1978, and it now a major concern and cost for people living in older homes.

The health risks of leaded gasoline were also obvious to many, and ethanol was known as a safe alternative anti-knock additive in the 1920s. General Motors and Alfred P. Sloan tried to hide the risks of lead paint via front groups and manipulation of regulatory agencies.

http://www.youtube.com/watch?v=TLoixnECec0
Video about Dutch Boy paint advertising to children.

http://www.theatlantic.com/health/archive/2013/04/why-it-too...
David Rosner is the Ronald H. Lauterstein Professor of Sociomedical Sciences and a professor of history at Columbia University. Gerald Markowitz is a Distinguished Professor of History at John Jay College and CUNY Graduate Center. Their most recent book is Lead Wars: The Politics of Science and the Fate of Americaís Children.

http://www.theguardian.com/commentisfree/2013/jan/07/violent...
Yes, lead poisoning could really be a cause of violent crime, by George Monbiot

http://www.huffingtonpost.com/2013/08/03/lead-paint-lawsuit-...
Lead Paint Makers Could Face The Same Fate As Big Tobacco

http://www.thenation.com/article/secret-history-lead
The Secret History of Lead
We shouldn't abuse email for this. Any one of LastPass, 1Password, KeyPass etc. or SSO with Google, Facebook or Twitter can do this way better. You will probably be using extremly long and random strings, i.e. you're storing secure tokens there. You can't call those passwords any longer -- and we should forget about the notion of manually creating and then remembering passwords to sign-in.
N2 Smartpen – Writes on Paper but Also Mirrors into Smart Devices
NASA's Mars fleet braces for comet encounter
It used to be that in the Midwest only a few people took the SAT, people looking to get into schools that required/preferred it or people looking to get a scholarship that used the score. The state schools were all fine with the ACT.
Does an average citizen in a car have an obligation to stop and render aid? What makes it any different for someone driving a Street View car?
"Yet, in 1987, professor Bestiale, supposedly a physicist in Palermo, Sicily, authored major ... ".

Just to clarify, there is no country called Sicily, and there hasn't been one for a while. The correct country here is Italy.
Just to put this paper in an appropriate historical context, I wrote it back when I was trying to convince NASA that flying Lisp on a spacecraft would not be a completely insane thing to do. The Powers That Be had already mostly accepted that it would be OK to fly Java, but they thought Lisp was too big and slow. This study and paper were designed specifically to address those concerns.
>We don't have a solution for agriculture yet

True, and not just talking about water. All aspects of "conventional" farming (aquifer pumping, mined fertilizers, fossil fuel-derived pesticides, diesel, etc) are by their nature only temporary solutions.

The start of a sustainable water management strategy might be P.A. Yeoman's Water For Every Farm[1], basically designing around land topology to harvest and store/infiltrate rainwater. Modern agriculture shunts rainwater off the land as fast as possible, maximizing runoff so that tractors can drive on it sooner.

Here's P.A. Yeoman's strategy (in cheesy 1950s educational video style): https://www.youtube.com/watch?v=cE-tJLQDZT4

[1]https://www.amazon.com/Water-For-Every-Farm-Yeomans/dp/14382...
Link dead
This article is a good reminder of why writing documentation (and commenting code) is important. Often the reader of your docs is you.
I've got an old-ish SVN repo at work with a ~115k loc Angularjs app, which is the end result of some very poorly thought through decisions to "allow all merges". It "works", but it's now completely unmaintainable (and has been since rewritten from scratch and the lowest effort way to add new features). It's a real shame, because the original dev (who wasn't involved in the botched merge) was actually doing some really good work, but the business kinda let him down with angular training for other staff, pulled him off that project, then let it crash and burn while not explicitly blaming him but making it clear they didn't blame anyone else... Not our proudest moment...