skysight-inc/HackerNews huggingface dataset:
Whether you should or shouldn't share that information with your doctor is a different question, and is the one where trust etc is relevant. The point here is that the choice to share or not share should be the patient's, regardless. If doctors want to turn down patients that wouldn't share something, that's up to them, of course.
Two things: they normally have a mass market / volume counterpart that is not rad-hard.

Second, they actually are full of bugs, and take a ton of money to qualify. Qualification, among other things, means thoroughly documenting the bugs.
15 Infrastructure as Code Tools to Automate Deployments – Thorn Tech
Failing and Other Uplifting Anecdotes
We troll bots for a living
What is it about corporate that makes everyone say ‘This is the way it’s always been done, so there cannot possibly be a better way.’?

Lets enjoy laughing at them after they fail, rather than before.
Sure thing, but who can guarantee they won't come with their own reason not to sell it next time, other than a background check? The mere fact they differentiate between clients and are non-domestic could probably be enough for a national intelligence service to view them as unreliable, and to develop their own alternative to a vital tool.
> It's important to me that my physical address not leak, I don't want people or packages showing up that I didn't ask to show up.

Because you think your physical address doesn't otherwise exist? Or are you talking about packages personally addressed to you?
I don't think you're that weird. I judge visual art by the amount of emotional effect it has on me. A well-written novel can be a way of teaching the unteachable, giving you a deep truth.

But maybe you already know that truth? Death Note fell flat for me because its core philosophical questions were already solved in my mind. Or maybe your solution is different? Atlas Shrugged is deep enough, but the opposite of a deep truth is another deep truth. Or you're just not ready to hear that story yet; the nostalgia level in My Antonia made no sense at all to me as a modernist teenager.
> Fun Fact. Lee Kuan Yew was a computer scientist before becoming politican

No, he wasn't. He was a lawyer with an undergraduate degree in economics. The closest that gets to being true is that his son, Lee Hsien Long, got a B.A. in Mathematics and Diploma (essentially an M.S.) in Computer Science before getting a Master of Public Administration. His work history immediately after getting the CS degree was as a military officer with a meteoric career path which appears to have been in field command and operations and general staff positions; he does not appear to ever have been a working computer scientist.

> Looks like computer scientists would make great politican's once elected but getting elected

That generalization goes far beyond what the single example you seem to rely on would support even if it were accurately described.
Some anesthesiologists believe that, but there's really no solid evidence for it. The reality is that no one really knows how or why anesthetics work, we just know what generally does work. I was told this by an honest doc, who also told me this scary fact: Because it's best to minimize the drugs that put you under (especially gaseous), and b/c we're getting better at walking that line, it's increasingly common to have patients wake up and freak out at the sight of their chest spread open. That's why the anesthesiologist keeps a couple of loaded syringes on the cart ready for emergency use: one is an instant paralyzing agent, the other a powerful memory blocker.
In five years, this style of device will be huge in robotics. NVIDIA is getting the industry hooked now.
Is there an advantage to freeze-dried compared to frozen or raw (other than, I'm guessing, shelf life)? Is there a loss of nutritional content?
They explicitly said that they don't think getting a 30 year mortgage is a bad decision for an individual. They are complaining about 30 year mortgages from a policy perspective.

> For the individual, the fact that encouraging 30-year mortgages is a bad policy does not imply that getting one yourself is a bad deal. The policy wouldn’t be bad if it weren’t effective, and it’s only effective to the extent that it encourages people to actually get the loans. So while I think there are prudent asset allocation reasons to favor renting over buying, if you don’t buy into those a standard mortgage is a relatively tax-efficient way to pay for housing.
I would believe that some of the distortion on the edge of perception might cause a little bit of stress (like, say, the barely audible whine of bad fluorescent lighting), but not really the bit about the brain working harder.
The proposals last year included massive cutbacks on H1 and L1 visa programs, among other things. As I recall, their purported replacements for the work visa track were much more constrained, so the result was a reduction in skilled immigration.

But we know that's what that crowd wants, anyway. They haven't exactly held back in op-eds. CIS, for example, is explicitly arguing for pre-1992 annual levels specifically for the skilled category, which would imply massive cuts.
Have you recently used Javascript? I ask because it's evolved pretty fast in the last 3 years. Even the past 2 years seem like a blur to me. Before 2015 it was unusable for me for large app development. Typescript evolves just as fast since it's a superset of javascript. 2.x was when it was usable for me. With 3.x, I have even fewer complaints. imo both are improving way faster than I can complain. That said, I still can't go back to Javascript after using Typescript. With rxjs and other popular 3rd party libs, it's hard to notice any limits. I'm not in love with Javascript, but it's just hard not to work with it since it's become the franca lingua of programming. Everyone knows it because everyone probably has to deal with it sooner or later. The ecosystem is also really strong. I have yet to had re-invent any wheels, which is something that's hard to avoid when using tech with smaller communities.
My personal preference:
React on the Front-end,
PHP7+Symfony4 on the Back-end with Postgres, RabbitMQ for messaging and NodeJS for microservices that deal with various real-time tasks based on those messages.
Window may be shifting - ASCAP's top 25 for 2018 included:

1. "All I Want For Christmas Is You" (1994)
7. "Last Christmas" (1984)
22. "Christmas Eve/Sarajevo 12/24" (1995)

(OT: 25. "Wonderful Christmastime" (1979) persists as a favored lump of coal for radio/streaming Krampuses everywhere.)

https://www.ascap.com/press/2018/11/11-29-holiday-songs-2018
It's pretty much entirely a cool trick and a joke. It was framed as a social commentary on gluttony, but I doubt that was ever the real reason for it or taken seriously in any way. It's just a cool thingy.
Blockchain is the second or third best solution to a lot of problems, and the best solution for running a currency speculation scheme.
http://opentaxsolver.sourceforge.net/
Cooking spinach degrades the antioxidant lutein.

https://www.sciencedaily.com/releases/2018/12/181221123810.h...
Most significant genomics news of 2018
Just want to say that this quite an amazing solution to a problem that has plagued pro apps for years.
That’s a good point. Unfortunately kiva doesn’t give you many tools to make those assessments. You get a picture of the person applying for the loan, and then about a paragraph describing what they will use it for. Very light on numbers and no follow up on how their business is doing post-loan. After a while it felt like the site was selling me the feeling of being a good person, above all else.
As long as people will think that privacy is a normal thing to seek, we'll keep using personal information and secrets as authentication methods, and those whose data leaks will suffer the consequences.

What we should do is think about the post-privacy world, where all data is available to everyone. We won't be able to keep secrets and passwords anymore, but we won't have to secure them either, as we will have better authentication methods. No more paranoia, encryption, or fear of data leaks.

It blows my mind how few people are willing to concede the benefits of transparency, even if they're not willing to fully endorse it.
> The handle looks rather contrived

Maybe you could stuff a dozen flat little drain pipes all the way around the walls of the cup, in addition to or as an alternative to routing through the handle. That way the handle could be petite and unsuspicious. Would that be harder to reliably print?
Absolutely, I'm talking about the collection as a whole, not necessarily every individual talk. The problems though are pretty pervasive and try hard to elicit that "I found fascinating" feeling, but you find more that accuracy and meaningfulness take a back seat to fascination.
Thanks for the awesome work!
If the purpose is to run specific apps with minimal OS, can buildroot or some container-based approach achieve the same goal?
Most mobile apps are really just glorified websites that don't need anything above and beyond the web sandbox. But they're going to ask for those permissions anyway, because when an app is the only way to use a sufficiently popular service, people will grant them.
- Python, PHP, GO, depending on what I need to do. No frameworks.

- Vanilla JavaScript and CSS. No frameworks.

- Relational db and Redis

- NGINX and Ubuntu. NGINX for caching.

- AWS or DigitalOcean depending on what I need to do. I strongly prefer working with DO whenever I can now vs eg AWS or Azure. I've had a good experience with Linode and Vultr in the past, however DO's ever-improving offerings keeps putting distance between them.

I've built up my own frameworks for authentication, APIs, etc. over many years that I evolve regularly. Over the last ~15 years I've strictly only been building my own things, so I don't have to consider other organizations or teams and what they want or their pre-existing approaches. My approach only makes sense because of that.
react & redux with typescript, firebase for authentication & hosting, database depends on the application. prettier & eslint. optional: commitizen for git commit standardization
N is a Number and E is for Erdos
Unfortunately passport number is considered semi-secret to the point where you can retrieve very personal information with it or with a tiny amount of extra info such as last name + passport number. Passport numbers are also permanent, until replaced.

Or to put simply: Passport numbers make identify theft easier.
Note the key difference between Space X and Boom. Space X took well-understood rocket engine technology and made it cheaper. It didn’t try to fight fundamental physics. Boom is entering an area where the large incumbents have failed because the physics doesn’t work with the economics. And there hasn’t been fundamental changes in the physics since those prior efforts. It’s a different bet.
The more time I spend working with studies and research data, the more I'm starting to realize that a lot of it [numbers] is complete and utter nonsense.

197 billion app downloads? You don't have to be a researcher to know that the number is a "little" far-fetched. And maybe I'm delusional to the fact that might be possible. After all, I have only ever used Android and only with the default apps it comes packaged with. Other than the exception for WhatsApp and Messenger.

But honestly, in the markets that I work with, I see such blown up statistics that it makes me throw up on the inside. E.g. In 2018, 20% of all web searches are done using voice (assistant, Siri, smart speakers, etc.), and by 2020 that number is "going to be 50%".

Holy macaroni... I can already picture the dystopian reality where people walk around airports all talking to their phones just to look something up.

All that aside, mobile apps suck! I prefer a well-designed mobile website over an app at any time of the day.
no, the conclusion actually is to make friends with the core developers. contributing good code is one way to do that, but writing excellent documentation, or filling some other need in the community can also work.
Linear is easily modelled. Nonlinear isn't - Lorenz attractor, weather forecasting etc.
Looking at the figures in the paper, cooking for 4 minutes (which is way overkill for spinach leaves) decreases lutein by 25-50% (with relatively large error bars).

I haven’t done the math in how much lutein is in spinach vs how much we need but to a first order of approximation that’s acceptable.

In the abstract they say they cooked spinach for up to something absurd like 60 minutes. Spinach leaves are cooked within a minute or so in my experience, so not sure why they performed the study that way.
The relation between full name, telephone number, and physical address is not secret at all. Sometimes I feel like I'm the only person who grew up with a phone book.

The financial sector abuses some of the more obscure facts about people (SSN, DL/passport number, bank account number, address history, mother's maiden name) as authenticators. They aren't. In the short term, someone can create a lot of bureaucratic hassle for you by knowing these facts. In the long term, institutions will adapt to the reality that knowing them no longer proves anything.

The stuff you should really care about, IMO: Contents of private conversations. Interests and opinions expressed online that could harm real-world relationships. Habits and characteristics that could signal insurance, credit, or crime risk. Political activity far from mainstream. Relationships with controversial or high-risk people. Evidence of excessive wealth for your context.

The fact that person with your metadata exists and does normal life things like having a home, a job, a cell phone, and a bank account is always going to be well-known. This information is more or less neutral. The real secrets are those which might prompt some actor (friend, lover, ex-spouse, family member, boss, insurance underwriter, lender, police, secret police, conman, vigilante, person who is wrong on the internet, etc) to turn against you, or to do worse damage than they would otherwise.
> but they don't know that your client-side framework will execute code inside a {{ }} block

Isn't that why they added a verbatim tag?
That "something else" is already crowded out by running through a multi-megabyte image.

At least the instruction cache is barely affected, which would not be the case for a math library function.
oh im sorry what i was suggesting is hard to do?
how about pervs and thier motivations.
There are more subtle ways of transferring money from lobbyist to political party than just cash payments. Let's say that the lobbyist sponsor company promises to use a hotel chain owned by a party member for its bussines trips, or buy office supplies from a company owned by other member of the same party, or something similar. You can buy their support for your cause this way.
> No PWA competes with a native experience. Not performance wise, not usability wise, and ultimately for the developer not even development wise.

This would be correct, in theory, if companies only made apps where the extra power that the app has is necessary, and would stick to websites otherwise.

In practice, this isn't true, and anyone who has ever opened any major app store knows that many popular apps in it are, in reality, just wrappers around a webview, and the only reason why they are apps at all is because the management demanded that there is an app, like all the cool kids have these days. Most apps really would be better off as just websites precisely because they don't need anything that an app gives, but often suffer from what it takes (e.g. ad-hoc navigation versus standard browser controls).
Did you miss the part where I pointed out the reason to abstract ntdll is dead? There is no more 9x. There is no more CE. It would already be serious work to move away from NT. eg. Why should all the filesystem APIs be path-based and introduce an extra CreateFile with who-knows-what sharing flags behind the scenes, when NT was built to work with handles and path lookup is slower than on Unix?

Abstractions are good but they need some basis in reality. The situation in Windows is in many cases layers atop layers without an actual need.
Not waving but drowning.
UMap: create maps with OpenStreetMap layers
I hate the good for you / bad for you dynamic so common when talking about food.

Ranking vegetables by how "healthy" they are is ridiculous. A diet is healthy and is specific to a person, lifestyle, and contains many foods and also how they are prepared. You can't separate it into tiny pieces and sort it into good and bad.
Similar attitude to cyclists in Australia, especially in rural areas.
Very nicely done. Here is part 2: https://codea.io/blog/detailing-the-ios-menu/
Notes on Floppy Disks
Win10 store allows PWAs, and even automatically lists the ones it finds online (via Bing crawler).

https://developer.microsoft.com/en-us/windows/pwa

I find it all oddly ironic. Remember back in late 90s - early 00s, Microsoft was generally hostile towards open web and the (then only just appearing) web apps, because that undermined its desktop app monopoly? Here we are 20 years later, and now it's Apple and Google protecting their turf on mobile, while Microsoft is promoting PWAs to entice the mobile devs into supporting Win10.
In this diagram: https://i.imgur.com/0Smz0Nk.png

Legal right on red is contributing to the behavior of the car driving east and turning south (who hasn't noticed they now have a green light), as well as the the car driving north and turning east (who's LOS is blocked by a truck, SUV, small van with tinted windows, etc. and is pushing that far up so they can see left enough to spot a gap which they can use to turn right on red)
Rails + Vue
Possible target for spear phishing (easier to social engineer when more information about a target is public).

Account take-over if the password was used elsewhere (credential stuffing).

Become a target for Extortion or Blackmail: https://www.troyhunt.com/the-opportunistic-and-empty-threat-...

Edit:
Some companies still use birth dates, security questions or social security numbers for identification. If the information is public, any one can identify as that person via a phone call. https://krebsonsecurity.com/?s=SMS&x=10&y=14 https://krebsonsecurity.com/2018/10/voice-phishing-scams-are... https://krebsonsecurity.com/2018/08/hanging-up-on-mobile-in-...
It's not only hard, it's completely unnecessary. Most people are assaulted by someone they know in real life. You don't need gigabytes of data and a "dynamic probability schedule" to figure out that someone is at work during the day and at home in the evening, and they probably take one of 2 or 3 convenient routes to move between the two. If they actually know their target, they might even know something more like "they have a yoga class on Wednesday evening".

For a second, pretend you're one of these "pervs" you're worried about. Are you going to randomly pick a name out of a data dump from Marriott's database, and try to correlate that with other leaked data to figure out the likelihood of this person you've never seen standing on a particular corner at 5:37pm on November 3rd?

Or are you going to say "Sharon from accounting smells nice, I'm going to follow her home after work"?

I think the latter is something more reasonable to worry about.
That's crazy. They should just stop everything, full-stop, for pedestrians to cross.

Every red light in this situation has a get-out clause, and no green light can be trusted.
> What we should do is think about the post-privacy world, where all data is available to everyone.

Either I don't fully understand what you're suggesting, or you don't fully understand what you're suggesting. ;)

Right to privacy is part of the Universal Declaration of Human Rights for good reasons. Violations and abuses of privacy have done a lot of damage to a lot of people throughout history.

So what does authentication even mean to you if all data is available to everyone? Why would you still need to authenticate?

Do you think it's a good idea for me & everyone else to see your bank balance? Personal emails? Personnel reviews at work? Letters to your girlfriend? Late night browsing habits? Purchase history? All your photos along with the video feed from your phone?

I don't see privacy ever not being a normal and reasonable thing to seek, not to mention rather important for developing democracies and as some protection against government abuses.

https://en.m.wikipedia.org/wiki/Right_to_privacy

https://en.m.wikipedia.org/wiki/Nothing_to_hide_argument
Google Photos and the unguessable URL (2015)
Can we strike at the root and try to reduce rent-seeking behavior? Even if we can't eliminate it, there was a time when 'usury' an ugly moral sin and Jubilee was an actual event, so at least we understood who the jerks were, instead of blaming ourselves for being indentured servants in a rigged system.
I actually wanted to do this, and went as far as drawing a sketch on paper, but then I realised it would be impossible to drink from :).

As soon as you tilt the cup towards your lips the nearest tubes would fill up and start siphoning.
Scalable Tech Stack – Cost Effective Secure Infrastructure for Bootstrapping
While it's true that a 20 ounce Venti drip coffee has much more caffeine than a 2 ounce espresso shot, it seems unfair to call them both "a serving". It seems unlikely that the person that's going to drink an entire Venti coffee would just drink a single espresso shot.

A 12 ounce tall Starbucks coffee has 193mg and a double espresso shot has 150mg. (a tall Americano has 2 espresso shots, so it too has 150mg of caffeine)

https://globalassets.starbucks.com/assets/94fbcc2ab1e2435985...

(just in case that link doesn't work, it came from this page: https://www.starbucks.ca/menu/nutrition-info)
JS has its uses. Once in a while I see a site which actually needs it and makes proper use of it. Much rarer, I have to develop such a site myself. But generally, I hark back to ancient times when websites meant html and css. When I do need a dose of JS, I usually go with something raw, or the unfashinable jQuery. I abhor the thought of JS in the backend.

Html and css always via Pug and Sass.

Out back, I really, really like minimalism, usually in the form of a single executable made with Nim. Static link whenever possible, so I can just bang the thing unto anything linuxish. For a reasonably low-volume site (meaning 99.9% of all sites), I go with SQLite for data. Yes, there'll be shouts of outrage that I shouldn't do it. These I know I can safely ignore, but keep my code clean and simple and easily portable to Postgresql if the should occasionally arise.

Sometimes I need easy access to every library function ever written, so I'll drop the purity and go Python. Bottle or Cherrypy is what like to build on, then.

No matter what, these days run the whole thing behind a Caddy server and be done with any headaches over configs and https.

I realise, of course, that I am completely out of whack with current general consensus. So be it. My stuff works, and works fast, and I can cram amazing amount of it into a fairly low-end VPS.
i agree, its way easier to purchase a domain and launch a site!
Good Engineering Practices While Working Solo
You're agreeing with me. Tesla in all likelihood does not freeze development of a chip model for 4 years before releasing it. So you cannot compare Tesla's current chip with a Google chip that is 4 years old.