skysight-inc/HackerNews huggingface dataset:
Face unlock will always be for convenience, not real security.

To me it's like a front door lock. It's there to dissuade people. If someone is adamant enough they will get in.
It's not a gimmick, it's just better user experience. Look at it through the lens of an average user rather than a power user ("power user" in the context of someone who is fluent with technical aspects of computers, not the domain).

I'm not arguing that the app itself has better video editing UX -- it may very well be that local apps win there. But for onboarding, no installation wins.
> The issue is not solved and it remains as pressing as ever

There's nothing to solve. It is explicitly against Google's policies. You have to be a tax exempt organisation to accept donations from an app in the play store.
A dental technician once asked me what I did for my job, and upon hearing my reply said, "Well, as an engineer, you really should have a better concept of how to floss than you apparently do."
One must imagine Sisyphus happy.
There are also essay collections. You can write 10 20 page essays and turn that into a book.
Tangent:

There's an incredible amount of information stored in obscure web forums, often in posts with photos. The damage that services like Photobucket have done by deleting old files, or by restricting hotlinking, has been incalculable. I worry that Imgur has the potential to do even worse damage, as so many forum users have converged on their service after others became unavailable.

(Imgur's popularity with Reddit users leaves Reddit highly vulnerable as well.)
> I like Git commit messages. Used well, I think they’re one of the most powerful tools available to document a codebase over its lifetime.

1000000% agree!
Database could be later extended by feature of auto-generation of training plans for specific conditions or goals not only for one day but for a whole year because of so much information about each exercise that was in previous plans, that can be used to generate new plan with exercises that target the same muscle group but in a completely different/shocking for the body way. We have used this solution without technology and it works great - but without tech it is very slow to create each plan.
At first reading this I thought "My iphone recognizes me right when I wake up so I'm sure someone could use unlock it while I was asleep or unconscious" but I tried it a few times while making a 'passed out' face and it turns out, nope. At least I couldn't get it to. Even tried using my hands to hold open my eyelids and it didn't unlock. That's pretty impressive.
Jeffrey Epstein’s FBI Records
How are people still surprised about Apple's customer service practices? That's the real question.
what about "cutting your losses"?
Architecting a Decentralized GitHub Backup
I agree with your frustrations but I don't think the blame is on "let it crash".

As far as helping prevent bugs, let it crash won't help. It is not a replacement for a type system either. A type system for Elixir would definitely help you prevent bugs (but unfortunately implementing one is challenging).

Let it crash is a mental model and a technique to handle bugs and avoid undefined behaviour when all other attempts to prevent them (be it via static types, testing, code reviews, etc) failed. Imagine some data validation functionality had a flaw and that causes bad data to reach a core component, would you rather:

1. have the core component continue functioning with said bad input, which may have unknown repercussions?

2. have the core component crash and restart itself with a known state?

So let it crash can be useful to guarantee your system is not going to venture into undefined behaviour.

I wrote a small example of this in a blog post about assertive code (http://blog.plataformatec.com.br/2014/09/writing-assertive-c...). If you compare the two get_token implementations, you are 100% correct that in the second implementation, if you receive bad input, the code will crash over and over again. But I would say that I prefer the crash, so I can think about how I want to handle said input, rather than have an implementation that works by accident (and the accident may be a happy or an unhappy one). Would I prefer to have foreseen the bad input in the first case? Of course! And do type systems help avoid undefined behaviour? Definitely! But not all of them. It would be great if we could have both.

On a larger scale, especially when building complex systems, you are going to interface with client/server, database, apis, etc and you will run into unexpected scenarios. You likely can't prevent, model, or foresee all of them, so "let it crash" works as a default behaviour to handle them. It is also a legit strategy for things you know that may happen, but the best way to handle them is to start over anyway. It provides a mental model for you to reason when things go wrong at each individual component, instead of trying to reason how an exception may affect the whole system.

I am not sure if this helps, so questions and feedback is appreciated!
It's interesting how all the tedious tasks listed are a product of modernity. Vacuuming, driving to work, flossing, doing dishes, etc.

I wonder how repetitive life feels for humans who still have to hunt for their food.

Not to say that we should shift back to a hunter-gatherer society, but I wonder how much of the mundaneness of life is something we brought on ourselves and not actually an implicit part of existence.
Author makes many dubious and unsubstantiated claims:

* Claims to know what the heart of the matter is, and that it is power

* Claims those recommending antitrust are "mostly stuck in the industrial age"

* Claims publisher vs carrier dichotomy is a "trap" without explanation

Nonetheless, when he started talking about an API I got pretty excited.
You may also want to consider allowing the user to specify whether the default is read-only mode or read/write. In similar applications such as http://join.me, the default behavior is similar to a read-only mode.
[Shameless plug.] Funny, I'm in the opposite shoe, just released a product after a decade+ of work but it somehow didn't show up in the Show HN section. This won't answer your question but it is definitely 1 product that matches your criteria. Maybe there could be a monthly Early HN thread if others post here too? :)

Boomla - a web development platform which I call a Website OS
https://news.ycombinator.com/item?id=21292726
Not really an author, but I do some writing, and good writing is, in my experience _hard_. Obviously, just like software development, its kind of all-or-nothing, either you finish the it and get it in front of people (and then maybe make some money/fame of it), or you fail to finish the project that you have now sunk a ton of time into. Just like software, you can quickly finish something, but then it will likely not be quality, and won't receive the attention you maybe think it deserves. All of this to say I think authors probably get a lot of support and assistance and thats why dedications happen.
Totally agree but moving the dot a little further down the line towards security is never a bad thing. Perfect shouldn't be the enemy of the good, etc etc.
I loved Norse Mythology by Gaiman, but there are others readable versions of norse epics.
For example, Children of Odin[0] is in the public domain, there are free english audiobooks, and is very enjoyable. There is some version with very nice drawings too :)

Personally, I enjoyed Gilgamesh' epic a lot through its analysis in a mythology class[1]. It is a fantastic story anyway.

[0] The Children of Odin: The Book of Northern Myths by Padraic Colum, 1920 http://www.gutenberg.org/ebooks/24737

[1] Myth in Human History by Grant L. Voth https://www.audible.com/pd/Myth-in-Human-History-Audiobook/B...
So many side projects I could have simply done over the years if I wasn't trying to figure out which LAMP/Rails/etc framework would get me there fastest... despite my not knowing PHP/Ruby/Python/etc
Not trying to be pedantic; it just seemed like an interesting problem. I’ll take your word for it that it isn’t interesting:)

I don’t know how they make money. Ad rates aren’t that great and bandwidth isn’t that cheap.
1. Github encourages us to specify a license on our repositories. This specifies the expectations a user can have.

2. There is a mechanism for people to participate - a pull request. The owner has the right to decide if this is consistent with the project goals and respond accordingly.

3. Charitable interactions are productive. It encourages collaboration and the result is the whole is greater than the sum of the parts. That is fun. Too much drama causes developers to find other uses for their time and talent.
I think that you may have replied to the wrong thread[0]

[0] https://news.ycombinator.com/item?id=21289827
Yeah, one workstation. If you need to build out 1,000x as many GPUs, the cloud becomes more economical. And that's where the money is, in large customers, not someone who needs 1 or 2 cloud GPUs.
Build Your Own Async [video]
AoA sensors are far from specific to MCAS. They may have been injecting AoA faults to test some other system that depends on the AoA sensors.
Yeah, I'm not claiming it's accurate, but what do you expect from a mushy modern version? I've read Mitchell's version, as well as couple different scholarly translations, but it's been years and I don't think I could cite specific differences besides cutting out most of the super repetitious parts (Babylonian comedians thought it was funny to say the same thing way too many times when describing a long journey) and filling in broken sections with words that worked well enough to continue the story. My memory of his Tao Te Ching "translation" is a bit better, and it's usually the one I recommend to people who have never read the Tao Te Ching just becauee it's worded so beautifully. He has some changes I really dislike, though; at one point he replaces a line about animals being like "straw dogs" (a sacrificial idol crushed under foot in a traditional ceremony) to the tao and people being like straw dogs to the master with a line that promotes pacifism, which is the change I hated most due to it actually seeming antithetical to what most scholars translate the passage as. He also replaces references to ancient weaponry with references to nuclear weapons, and stuff like that -- but I don't think he gave Gilgamesh an AK, as far as I recall ;)
http://tech.groups.yahoo.com/group/concatenative/

... oh, it seems it's already gone.
The issue is not about accepting donations through Google Play Billing, but about having a link in your app to the external donation page of the project.

Could you link to the policy section that explictly bans external donation links from being present in apps, unless you're a non-profit organization? People have been referring to the Google Play Billing terms of service, but that has nothing to do with linking to external donation services such as Patreon.
Don't see any mention of how many false-positives they had in the article so... Yeah we'll see how effective this actually is.
Standard object out: streaming objects with polymorphic write streams
They have their version of mundane tasks.
The benefit / drawback ratio for mushrooms is close enough to plants that it should be a non-factor. The real issue is familiarity. When you’re out in the woods, you’re surrounded by plants that are mostly inedible and often toxic. But you already learned that “most plants are inedible,” and you are familiar enough with the plants/parts that are edible to make it seem much less risky, since you ignore 90% of what you see before asking “can I eat that?” You don’t eat random berries; you stick to easily-recognized ones like raspberries or strawberries. You’ve been warned about poison ivy since you were a kid. Very few people eat the common herbs that are around because they don’t recognize them as edible.

Mushrooms are harder to find and less familiar. If you take a few hours to study up on one or two edible mushroom species (and their lookalikes, if they have them) you’ll find that it’s just as easy to positively identify them as it is an edible plant—which is to say, it’s not trivial but not too hard either. The defining characteristics are just different from what you’re used to looking for.

Chanterelles for example have a couple of lookalikes, but the real ones have ridges that run down the stem and not gills. Morels have a few lookalikes, but the real ones are hollow inside.

The differences between edible cow parsley and deadly water hemlock are IMO harder to spot than either of the above.
I bet this half-assed implementation is only there so that potential shoppers with a checklist in hand will be able to mark the feature as present. I wonder how many reviewers fell for it.
Apple is terrible, but this isnt exactly new information. The author also strikes me as someone who should have known better. Their whole business model is selling overpriced hardware and then nickle and diming users through adapters and bullshit care plans. This has been the norm for over a decade. They killed the iphone headphone jack 2 years ago. Stories just like this one continue to abound.
Its one thing to have your employer buy an apple laptop and deal with all the nonsense, but why for personal use? Do people expect to be an exception to the rule when buying apple stuff? I dont get it.
> One might reasonably assume that an article about workplace deaths isn't counting employees who slipped in the shower at home.

I disagree. With these kinds of sources, you can't reasonably assume this.

> But we don't have to assume: the linked Dirty Dozen list published in April 2019 says "Six workers have died at U.S. Amazon facilities or operations since November 2018." Six on-the-job deaths in six months, November to April. Not all of them were in warehouses, but all of them were preventable.

You're right, I should have paid more attention, because those deaths aren't Amazon employees at all and none of them are warehouse workers:

- Andrew Lindsayand Israel Espana Argote, contract workers, died when the wall of an Amazon warehouse collapsed during a severe storm in Baltimore in November 2018.

- Brien James Dauntfell to his death during construction of an Amazon warehouse in Oildale, CA in January 2019. Falls from a height are a well-known –and preventable –hazard in the construction industry, with long-established protocols to reduce risks. CalOSHA is investigating the incident.

- Aviators Ricky Blakely,Conrad Jules Askaand Sean Archuletadied in February when an Air Atlas plane, carrying cargo for Amazon, crashed into Trinity Bay, southeast of Texas. Blakely and Aska worked for Air Atlas and were members of the Airline Professional Association (APA), Teamsters Local 224. The National Transportation Safety Board (NTSB) is investigating the incident.

None of these incidents hint at negligence on the part of Amazon.

This also explains why over the period of several years, Amazon workplace fatalities were well below average: They counted those properly. Working at Amazon is actually very safe, statistically speaking.
There’s a setting “Require Attention for Face ID” that controls this. It’s enabled by default, but if you’re unable or find it difficult to look directly at the sensor (or wearing sunglasses that block IR) you can turn it off and make it behave like the Pixel.

You can even point it at your face while looking away, and it won’t unlock until you make eye contact.
> the evidence of ill intent is relatively weak here

Most people are referring to negligence, not ill intent. "Let's make more money and rush this thing out! (Even though this could kill people)", not "Let's deliberately design a system to kill people".

Regardless, one sensor failing should not induce a plane to fly itself into the ground, despite the best efforts of the pilots to recover (and despite the fact they were not necessarily the best trained pilots). 2 / ~400 complete hull losses of brand new jets is completely unacceptable. That is dismal. Don't try to downplay it.
Boost.Preprocessor is the only part usable from C, though I wouldn't generally recommend using it.
The dynamics between hospitals and payers depend on market and negotiating leverage. A small hospital in a competitive market will struggle, while a large hospital system in an unsaturated market will do very well.

Are hospital failures due to payers, or due to competition from other hospitals? If a payer is getting squeezed by a big hospital system, it may in turn squeeze a smaller hospital or provider.

One of the biggest for profit hospital chains, HCA, generates 20-25% EBITDA margins. Many non profits are very powerful and make lots of money, they just spend more on salaries so their net income is lower. But yes many hospitals do struggle.

Insurance companies must spend 80% of their premium revenue on healthcare services. So their profits are in effect capped.
This is already the case with the FDA 1962 "safe effective" regulations. There is little downside to the FDA wanting to take no risks whatsoever in approving a drug, but a huge downside to the regulators if they approve a drug that turns out to have a fault in it.

The result is that developing new drugs got enormously more expensive, far fewer new drugs get developed, long delays in effective treatments getting approved, diseases that don't affect large numbers of people don't get cures developed, etc.

The net result was a negative for patients.

This was all discussed in "Regulation of Pharmaceutical Innovation" by Sam Peltzman.

There have been a lot of deadly aviation crashes due to mistakes, false assumptions, oversights, incompetence, human failings, etc. But somehow we've wound up with incredibly safe airline travel. Millions of flights with no incident. Do we really want to start jailing people now? What improvements will we forsake if we give airframe makers powerful incentives to hide mistakes? or simply avoid making improvements to safety, because who wants to risk jail for making a mistake?
Maybe they're also using the Accept: header, which would reveal whether the browser is loading a page or an embedded image?
Sure - but either way it doesn't look good.
That's a totally backwards take. Most of these things are modern labor-saving devices that replaced even worse drudgery. Sweeping takes longer than vacuuming. Washing dishes by hand takes longer than a dishwasher -- especially if you don't have unlimited running water, or dish detergent, or if you need to start a fire to get hot water. Ancient Romans didn't have to deal with rush hour traffic, but research says their commutes were just as long as ours.

To put it another way: we used to required half of all human beings to attend to household tasks. That setup wasn't put into place because of malice, it was there by necessity. Managing a household used to take as much effort and thought as running a small business does today. Modernity has saved us from that.
are computers any smarter or are they just good test takers
The government can legally take away my property (eminent domain), my liberty by putting me in jail, they can force me to join the military, etc. Corporations have none of those powers.
The money isn't the important part. I should have just left that part out. The important part is where SO says "by posting content you agree to license it to us, and we agree to relicense it as cc-by-sa."

I didn't understand what you were getting at with the comparison, they seemed totally unrelated to me. I think I see now though. If I look at it a certain way I see "receiving content and then relicensing it" in both circumstances.

I think that the context which needs to be ignored to make them the same in that way is very relevant though - the devil's in the details. In one circumstance you are posting content under the agreement mentioned above, in the other you are receiving content from someone who has agreed to no such conditions.

Seems like the disconnect here is whether SO should be able to put the relicensing terms in their terms of use and have that be enough. Personally I lean toward yes, but could probably be persuaded in the other direction. Would a check box next to the answer box be enough consent do you think? Or do you feel no one has a right to relicense any content they haven't produced themselves?
I don't know why anyone would want a face unlock instead of a simple fingerprint sensor. My phone is unlocked and ready for me before it even leaves my pocket.

The lack of it is one of the major reasons I'm not upgrading my Pixel 2.
> Most treasured memories are agonies that won’t get out of the mind and have to get turned into a character-building story to maintain sanity,

My world is changed by how obvious yet insightful this is.
Just pick a point and rotate a line around that point continuously.
Keep track of the number of points on the left.
Since this count is essentially continuous (the jumps are of size 1),
at some point during this rotation you will have an almost-balanced configuration (same number of points on left and right, up to parity error).
Some project managers cling to the fantasy that work will get done in a predictable and orderly fashion if only they wrote down everything that needs to be done and put checkbox next to it (preferably with a target date)

That sounds more like a to-do list, rather than a checklist. The way I understand checklist is to have a short (or manageable) and repeatable list of very important items that need to be checked before major events (surgery, software release, flight take off etc). If there are dates next to items and every single tiny item is in the list, then it is a todo list.
> The elephant in the room in US health care costs is inefficiency on the provider side. Payer-side reforms have limited impact, because contrary to rhetoric from both sides of the debate, we could probably zero out administrative costs entirely and still deliver little more than a grocery store discount to American consumers.

Certain kinds of payer-side reforms (e.g. single payer) could allow the providers to be bullied by the payer until they're forced to get their acts together.

The only thing that couldn't really address is doctor shortages, but that can (slowly) be addressed by a change in medical education regulation. Right now it's basically controlled by the AMA (basically the doctor's union), which limits the supply of seats to keep graduate salaries up.
I use 1984 for my mail server and I've been pretty happy with them. Decent pricing, and they support OpenBSD on their VPS offerings (which is perfect since OpenSMTPD + Dovecot is my preferred mail stack).
I am taking CS 236 (Deep Generative Models) at Stanford and this course really helped me a lot in reviewing the math I needed for the class. This is because the chapters focus on the concepts and ideas you should know, so you don't have to waste time learning everything there is to know about linear algebra and convex optimization, but the essentials for machine learning.
> Van Gogh was utterly miserable though.

Geniuses usually are.

That does not in any way diminish their contribution.
If someone is going to rise to the level of creating a mask in your image to unlock your phone then you have already failed by using this feature to secure it. MI6 is coming after you and you're relying on something like this? C'mon.
I mean, hell, couldn't you have tried this before taking it to apple? I have a iphone 6 that apple fixed a year ago and I'm not sure how many samsung/pixel would do that? where do you even go to get those fixed?
> By the time AMD donated their Mantle code to Khronos to serve as the basis for Vulkan, Apple had already shipped Metal.

Metal v1 was so woefully incomplete, AMD was in no position to ship something similarly limited. Vulkan 1.0 is functionally similar to Metal v2, which shipped several months after Vulkan 1.0.