skysight-inc/HackerNews huggingface dataset:
> What do you do if your surgeon operates drunk and kills you?

Can you see that this introduces a level of recklessness that isn't present in the parents question? Parent is asking about normal death by medical error. That's likely to have complex causes and is rarely as simple as "doctor was negligent".

But assuming that a doctor does kill someone: most relatives don't want a pay out. They want to know that this mistake won't happen again; that people and the orgnisation have learnt from the death; and they want an explanation of what went wrong along with an apology.
Chinese entrepreneurs have responses to the government’s crackdown on crypto
> "be liberal in what you accept, and be conservative in what you send"

This is commonly known as Postel's Law, and comes from one of the TCP RFCs [1].

[1] https://en.wikipedia.org/wiki/Robustness_principle
I woke up this morning to several new labels in my gmail to delete all emails for "bank" "card" "paypal" etc, and paypal was hacked with purchases.

But my gmail has zero new logins, my 2fa wasn't triggered, etc.

How does a hacker create labels to delete my email but not register a login attempt or trigger my 2fa? I wish I was able to contact google.

EDIT: my only guess was accessing my PC where logins are saved, but I sleep in the same room and I don't think ninja spies broke in. Remote login? Seems farfetched.
Pretty sure it's domestic violence.
> Look like intrinsically. Color of skin, fat, thin, hair, no hair etc.

Clothes do change a lot like someone looks like though. On top of that, changing hair is almost as easy as dress. Thin/fat ain't rocket science to change either. Even skin of color is changeable.

Splitting by choices is generally not fine. Like my previous example - splitting by poor/rich or career choices.

Judicial system is splitting by immutable traits too. If someone has a pathology which causes him to do harm to society, he won't be let go because it's immutable.
I can just vaguely remember -- and I long for -- the "good ol' days" when one could simply show up at a venue and hand over cash in order to be allowed in.
for Yubikey U2F WordPress plugin only Chrome currently is supported.
The second point is - you cannot share fingerprints, while sharing passwords is common practice. I'd say, from UX point of view, Google and Microsoft initiative is bad for users.
Tracking the Illegal Shipment of Sarin Precursor from Belgium to Syria
" The thing is, people don't really care about animals. Especially not the kind, calm and docile ones."

That's the beauty of our modern society. Most of us never see the dirty stuff that's going on. We only get a very sterilized image of the world. Just go into a chicken or pig farm and see how horrific the conditions really are. But we get protected from having to see this and get our meat with nice clean pictures on it.

Some years ago I saw a video some journalists that got in a "surgical" airstrike. Same thing. We only see clean images from above but their footage showed had terrible such a strike is. Cut off limbs everywhere, people screaming, badly burned children. This took my excitement for modern weaponry down a lot.

We are now as cruel or probably more cruel than people in that past. We just don't have to see it anymore because only a few people will do the dirty work.
https://tools.ietf.org/html/rfc761#section-2.10
For Diaspora in particular, this archived article goes in depth. "What happened to the Facebook killer? It's complicated." (2012-10-02)

https://web.archive.org/web/20121009223506/https://motherboa...

Excerpts:

* The team of four young kids had little real-world programming experience.

* The team found themselves crushed under the weight of expectation.

* The first release, on September 15, 2010 was a public disaster, mainly for its bugs and security holes.

* Google+ imitated Diaspora core features such as circles, and invested lots of money, but still failed.

* The team ran low on money, and VC interested waned.

* Sadly one of team members suicided.
Sure, but it doesn’t scale well. Static-typing makes code easier to come back to a year later or collaborate on because it’s more self-documenting.

You don’t have to dig through the codebase to figure out that a function should have only accepted a number, because the interpreter/compiler would have screamed at you the moment you try something else.

Scripting languages may be easier to learn, but they aren’t as scalable and efficient. In requiring less scaffolding and structure, they’re not as well suited at creating correct code in large codebases. They’re still great for prototyping, though.
Couple comments already on "websites shouldn't accept biometrics as a password". They're totally correct, and that's not what is being shown here. This is "websites accept hardware or software generated FIDO logins that have access to them intermediated by a combination of several factors including device presence, session login, and biometrics".

The hard part is making that look and feel like "login with a fingerprint".
"We recommend NVIDIA DGX-1 with 8 Tesla V100 GPUs."

https://www.nvidia.com/en-us/data-center/dgx-1/#order-now-dg...

The NVIDIA DGX is available for purchase in select countries and is priced at:

DGX with P100 at $129,000*
DGX with V100 at $149,000*
DGX support plan is required and must be purchased separately.
>>Many countries that have essentially completely banned guns somehow have also managed to have low injury / death rates.

As long as you go back only a few years - many of those same countries have experienced genocides and holocausts from their powerful governments acting against a disarmed citizenry and driving their long-term violent death rates to astronomical levels.

I would say that this observation is relevant because the argument for citizens being armed is to curtail the abuse of a powerful government.
My favorite is The Cyberiad.
I'm not sure why you're talking about judges making money on the side when the original "conspiracy theory" was about governments making money, not about corrupt people making money for themselves. We're talking about action by a government against a corporation. I'm not even sure why are we talking about corruption, this has nothing to do with it.

This is not about judges applying GDPR. The lawmakers will apply it, and then the state could sue a corporation for breaking laws. Local highest court will then eventually look into the intent of the local implementation and see that yes, this was the intent - and the corporation will need to pay up, because the court can't change laws, they can only cancel them in a few special cases (specifically if a law is ruled unconstitutional by a majority of the country's constitutional judges). The corporation then has an opportunity to go to Strasbourg, but since GDPR is very broad, its chances would be very slim - and most probably none.

About Makedonia - you're right. Croatia is entering the EU though.
Consumer behavior can change. With good marketing, it seems plausible that humane meat and dairy could become a big market, way bigger than veganism.
Yeah, the grandparent is hung up on the theory vs. application delay.

By the same logic, nothing in modern CMOS logic or its production process requires physics or chemistry of a vintage later than the 1940's to explain, so why did it take us three quarters of a century to get where we are? Because it's hard. Knowing how it works and figuring out how to do it are two different things.
But such a simple solution goes up against the developer claiming that Amazon is the big bad that wouldn't let them update their buggy software...

That being said, if someone can point out to me where this code is in the source I can hack out a solution for the next week or two.
> I just wanted to say that GitLab is a great project to contribute to, with a very friendly and professional community!

this. I've had a fantastic experience as well. Its one of those communities and projects that has been so good I have to leave a comment about it :)

Thank you GitLab team and contributors!
If your API takes json input, some of those issues are potential security or DoS issues.

For example, if you validate your json in your web front-end (EDIT: I used the wrong term. What I meant here is the server-side process that’s in front of your database) and then pass the string received to your json-aware database, you’re likely using two json implementations that may have different ideas about what constitutes valid json.

For example, a caller might pass in a dictionary with duplicate key names, and the two parsers might each drop a different one, or one might see json where the other sees a comment.
They have a similar law in New Zealand, but there is a debate around abolishing it so that disabled people would have to be paid normal minimum wage.

The flip side to this was that a whole bunch of workers basically stood to be made redundant, because the companies employing them could't afford to pay them minimum wage. The reason that a lot of companies were hiring these people was a as community service.

The coworking space I used to work at does this. They have a special needs guy who is the community assistant, he'd come in like 3 days a week and help with keeping the kitchen clean and other stuff. It was great, we loved him and he loved being there. It would've been cheaper and easier to hire a fully-abled person to do the job, but that's not why they hired him.

It's common for supermarkets in New Zealand to hire people with learning disabilities to do things like collecting trolleys. To be honest, they look like the most satisfied employees in the whole store.

The sad thing though is that people do abuse the system and use them as a cheap source of labour, which is disgusting.
who believe that some guy who founded PayPal can just "think from first principles" and outwit nearly a century of manufacturing and industrial innovation

I believe someone surely could, maybe Musk or maybe someone else. It does happen. The right smarts at the right time with the right money, etc. But were I to worship that hero I'd certainly keep my mouth shut until after he has delivered first.
The Melt was one of the most moronic restaurants to ever grace this Earth. I have no idea who thought it was a good idea to charge people fifteen bucks for half a slice of a grilled cheese and a small cup of soup.
Yes, if this happens to be noticed by the media, I'm certain we'll see a press release or interview with the Chief Damage Control^W^WMarketing Officer in the next couple of days where they explain how this is all just one big misunderstanding ("no no no, we didn't mean that, we promise!") and they are working quickly and diligently to clarify and simplify their new Merchant Agreement and straighten this little issue out.

A few days after that, some other newsworthy event will happen, everyone will forget about this, and we won't hear another word about it until the first lawsuit over this Agreement is announced.

I think the only thing that might be missing is an indemnification clause -- although it may very well be in there (I freely admit to not reading the entire Agreement, just this section 7). That way, when the venue you've booked for your event -- or one of the participants or attendees -- decides to sue Eventbrite, they can point out how YOU promised them you had everything taken care of and so it is YOU, obviously, who is entirely to blame. For everything. I expect that elsewhere in this Agreement, however, you have likely given up any right to sue and agreed to have someone of their choosing handle any "disputes" which may arise.

IF I, by chance, ever again desire to attend an event where Eventbrite is the vendor handling ticketing, I will certainly make sure that I read, very carefully, every word of any agreements they try to get me to click through during the ordering/checkout process. Considering everything I just read here, I cannot imagine the things that they will expect an attendee of an event to agree to.
Not really, the GM product is a loss leader, well, follower, the lose $9k on each one.
> For instance, RFC 8259 mentions that a design goal of JSON was to be "a subset of JavaScript", but it's actually not.

Actually, it's really close https://github.com/tc39/proposal-json-superset

This is a stage 3 proposal likely to make it to the next version of the spec. At which point JSON would truly be a subset of JavaScript.
Disagree.

I can always make my JSON act like XML if I want to. When I'm following something like JSON API v1.1 I get a lot of the advantages that I'd get from XML with 99% less bloat. You want types? Go for it! There are even official typed JSON options out there. The security / parsing issues with XML alone are enough for me to rule it out.

How many critical security issues are the result of libxml? Nokogiri / libxml accounts for 50% of my emergency patches to my servers. ONE RUBY GEM is the result of half of my security headaches. That's insane. I only put up with it because other people choose to use XML and I want their data.

How many issues are the result of browsers having to deal with broken HTML (a form of XML)?

JSON isn't perfect, and I wouldn't use it absolutely everywhere, but it's dead simple to parse[0], readable without the whitespace issues of YAML, and I can't think of one place I'd use XML over it.

[0] http://json.org/
It sounds like it would sacrifice the first playlist, which you describe is the problem, and leave all other playlists intact, which is what Amazon requires.
Intro to FoundationDB
Biometrics should never be the only means of authentication. They can only be complimentary.
My first question, looking at that graph, is "how does that graph calculate a global temperature for an entire year?" Do you know the actual source of the global temperature readings going back to 1880? Sure, the webpage says the dataset came from https://climate.nasa.gov/system/internal_resources/details/o..., but where did they come from?

These are the first 10 lines of the linked dataset, showing land and sea temperatures for the entire earth from 1880 to 1889.

1880	-0.19	-0.11
1881	-0.1	-0.14
1882	-0.1	-0.17
1883	-0.19	-0.21
1884	-0.28	-0.24
1885	-0.31	-0.26
1886	-0.32	-0.27
1887	-0.35	-0.27
1888	-0.18	-0.27
1889	-0.11	-0.26

I'm curious where this data originated - and that curiosity has nothing to do with belief in or disbelief of climate change.
Awesome :) I think I've tried "Go Veggie!" and "Daiya" brands from the super market. If you melt the Go Veggie brand into vegetable chili and then put that on top of some baked pita chips, you are in for an enjoyable meal ^.^
2-in 1 Ionic Hair Straightener Brush MCH Heating Hair Straightening Irons With
Totally deserves what? What’s “it”? This seems overboard.
New Patterning Options Emerging At 10/7nm and Beyond
This is also widely considered a bad idea now. Making liberal consumers allows for sloppy producers. Over time this requires new consumers to conform to these sloppy producers to maintain compatibility.

Just look at the clusterfuck that HTML5 has become. You need to have extremely deep pockets to enter that market.
Well, under this ruling they don't have to. But the victims didn't sign off on this, they are perfectly entitled to sue for whatever they think they deserve. (Though if they intend to do so they should absolutely not accept the money they try to give them as a result of this deal, as that will make their case that much harder to win)
Please don't forget the treasure trove of data Apple gets via iCloud services, which rival Googles if you're invested in their ecosystem - contacts, calendars, emails, location (Find my phone), all application data (backups), etc.

They don't also fully encrypt all of that information and give it to government on request.
I think the idea of humans sharing a language with computers is problematic at a fundamental level.

(the whole $dataformat "easy to read for humans")

It becomes a source of never ending lose-lose compromises where the more points you give to human convenience the more points you take away from machine convenience and vice versa.

Then you end up having to "settle" for something in between that is just ambiguous and problematic for machines to be able to deal with it and just noisy enough for humans to be able to cope looking at it and edit it. That's basically what JSON is.

If we accept to use a transformation step and better tooling we can free the representation from this tension of "friendly for computers vs friendly for humans".

It's also a bit odd that we apply this readability obsession only to these data formats.

I don't hear people wanting a human readable text representation of their audio, video or images.
But isn't it still a stronger form of authentication than the average password?

I would not use it for authentication against the missile launch system, but my ex will probably not chop of my finger to access my Facebook account, nor will random bots trying to access my Gmail account.
For a subset of cases, but not all of them, as traffic safety statistics show.
Except that Tesla is now producing at a weekly rate equivalent to hundreds of thousands of cars per year at their Fremont factory, comparable to other car companies.

But they're still ramping up. The factory will be outputting something like 500,000 to 700,000 cars per year after they're done ramping. They'll need Model Y and/or Semi and at least another factory before they're going to be comparable to other mid-range manufacturers. They'll need at least half a dozen factories to be a major manufacturer. Or they'll need to change how cars are made entirely.

If they can get millions of cars from a single factory, then the high automation that they're shooting for (and which Model 3 had to back off of) might make sense (and is required for getting that kind of production from a single line). But even that will likely need multiple factories to justify the R&D into the factory line itself.
While I agree, integration tests can be pretty costly in term of time to set up.

In the small places I have worked, it been acceptable to have a few bugs, and the applications were completely or partially used by internal users, so maybe 40 -50 people who can put up with a bug here or there and report issues personally.
The reason you get calls from similar phone numbers is because they crawl from their own number. If we change up the way numbers are assigned so your number +- 1 isnt valid, this technique will no longer work.
Like those on a debit/credit card, or like NFC on phones?
It's easy to be strict if you are both a producer and a consumer.
I wouldn't even give Tesla the credit of revolutionary for connected cars. On Star has been in GM vehicles for a very long time (1996 says Wikipedia), offering various levels of connectivity.
How to Cook Smarter by Cooking Smaller
The reason we don't have zones in Node is because they mess up with error handling. I recommend anyone considering Zones to read trevnorris's domain postmortem https://gist.github.com/trevnorris/d19addf4aa09a0a31a4a14e90...
Maybe something from our own meaningless existence resonates
I've used it a couple of times now not to develop, but to incorporate review discussions and minor other fixes. But from my perspective the true value is for non developers, or when you're starting with Git. No need to worry about remotes and what you did or didn't sync. Or if the branch is even there and you need to set the upstream. Concepts one need to get now are branches and commits. No cloning, fetching, pulling or pushing. When starting, branches and commits are hard enough.

Than, when the new user is comfortable they can work their way up.
> I wonder why it's so sad for us

We place value on motherhood, selfless sacrifice and planning. Here, those virtues (exhibited by anthropomorphized mothers) were thwarted by a dice roll.
HTML isn't XML. It's close, but it isn't. There's XHTML for that.
As a counter viewpoint - Google has one of the best security infrastructures and security experts in business. If anywhere, data is safe there (for certain definitions of "safe"). Do you trust all other small companies to secure and lot leak your data in the same way?
I was able to find this page through Google search: https://chronicdata.cdc.gov/Behavioral-Risk-Factors/Behavior...

and I found the survey question by searching with the filter Question > contains > "firearm."

At this point I'm tempted to say that the author's complaints with respect to data suppression are exaggerated.
If anyone reading this undertakes this challenge, it would be a mistake for you to focus on privacy despite the recent headlines. The problem is that privacy, something that few people care about (as evidenced by the lack of impact all of this has had on Facebook usage), is not a selling point. People have something that serves their needs for social networking purposes, and that something is Facebook. The only way to beat them is if you offer features that help serve their social networking needs better than Facebook and in a way that is so compelling that it would be worth it for an average user to make the switch.

Most people don't buy a $100K+ Tesla to save on gas or save the planet. People buy them because they are amazing cars. Similarly, people won't switch social networks because you offer better privacy. They'll switch only if you make an amazing social network.
Netflix open sources container management platform Titus
Quantum computing is not parallel computing: https://physics.stackexchange.com/a/3400 briefly talks about the mechanism of quantum computing and how it is not general parallelism.
A possible alternative:

https://eventil.com

Started a while back by some of the guys from (I think, it's been a while) the Ruby scene. Seems decent.
It could be "Argument of the Beard", "Causal Reductionism", or "Fallacy of Composition" (http://www.don-lindsay-archive.org/skeptic/arguments.html).

In any case, you're right to point out that it's troll behavior to dump all of the effects of industrial pollution and the resultant politics on a single individual's shoulders, as though one person would have a measurable impact on global climate.

~southern_cross is just framing their argument as, "if you haven't killed yourself yet, then you can't care about the environment", and that's an easy argument to ignore.
I, for one, am very impressed by the capability of this (mostly-remote, IIRC) team to ship so many releases, so fast. We have now one release per month!

We host most VideoLAN projects on our own instance, and the updates are now very smooth, especially compared to the beginning.

Of course, there are features that we care about a lot and are not implemented, because they don't consider them important (or maybe not worth their time, which I understand) but it's a very solid software. I hope it can replace our wiki and bugtracker soon...
2, 3, and 5 seem to be problems that only occur at scale so it seems odd to focus on solving these in the beginning when the nascent social network wouldn't be big enough to even have a breath of these symptoms.
Nothing in your argument seems relevant to whether your mythical format is "readable" or not. The industry has had extensive experience dealing with interchange of commonly-used binary formats (.xls comes to mind as one that still seems some use) and if anything that experience was even worse.

You're just saying that if we stopped trying to adhere to "our" aesthetic and replaced it with "your" aesthetic when we created an all-new format, that it would be better. I think there's an XKCD to cite about that...