skysight-inc/HackerNews huggingface dataset:
I don't see how this is "not compliant".

Expert knowledge just mean that he/she read the entire directive. The same way that most employer in europe have read their country's labor law.

The reason why they say that is because the "Data Protection Officer" is the person liable for GPDR violation. The same way the CEO is liable for many wrong doing a company could do. They require no certification, no degree for a person to be a "Data Protection Officer."
Cilis fil – Macho power
That's so reductionist as to be useless. What is a "good" reason? Are you a judge that will be presiding over these cases? Things like that are massive holes for litigation and the cause of all these compliance issues in the first place.
The problem isn't to delete 1 piece of data 1 time. The problem is different people demanding thousand+ rows randomly spread out in your database deleted every day that is the problem.
Automatic complaint-letter generator
I can easily see small websites just ignoring GDPR and hoping they fly under the radar.

This is my plan. What are they going to do, extradite me over claims that my access logs includes IP addresses? Claim that I do business in the EU when I don't take payments, every side project I've made is in English, and I've never set foot there?
Credit card company is not a government. It's helpful for business purposes to have records, but it's not always a legal requirement.

Anyway this stuff is super complicated and there's no rollback for data that was mistakenly deleted and shouldn't have been, so the point is there are layers and layers of complications and scenarios and it's not as simple as everyone likes to make it out to be. It's not impossible, but it's definitely a lot of difficult work.
A trend I've noticed from lurking and browsing these comments: commenters who have experience taking risk and operating under existential conditions in stressful, budget constrained companies (AKA, startup founders) tend to be critical of the GDPR.

Commenters who work as 9-5 employees or have never started a company (or at least, don't mention as having done so in their profiles) tend to be more supportive of the GDPR.

Funny how that works..
I'm glad see that the EU has created a potent reason for US internet services to take a hard look at their tracking/privacy feeding-frenzy.

When my ad-blocker tells me that 50 to 200 trackers are interested in me reading some innocuous, unparsable word-blob, or watching some throwaway video, I see that as a symptom of thoughtless hoarding and unreasonable prying. This is not gathering intelligence: quite the opposite.

Were there some demonstrable, substantial benefit to all this for the end-user it might make a bit more sense. But there are no upsides to seeing shark fins at the beach.

When I guesstimate the costs -- just those of energy usage, bandwidth and man-hours, not to mention the rest -- and compare that to the supposed results (only imaginary to me, the end-user)? Sorry, it looks like madness.
A lot of commercial dishwashers have multiple trays - they're integrated into a counter and have two guillotine doors that lift up, allow a new unwashed tray to be slid in one side, while the previous washed one slides out the other side.

If you're washing hundreds or thousands of dishes for lunch or dinner rush, this assembly line is the way to do it.
NVIDIA was amazing. They drove a bulldozer through the walled garden of HPC Welfare Queens (ask any grad student from the 00s trying to get supercomputer access what GPUs meant to them) and set the stage for the current AI boom.

IMO they deserve an entire fulfillment center of ice cream for that alone.
Diimtech
> I see that as a symptom of thoughtless hoarding and unreasonable prying

It's a symptom of people not paying for content and news. Also the fact that publishers want to provide equal and easy access to everyone regardless of affordability.

> demonstrable, substantial benefit to all this for the end-user it might make a bit more sense.

The content you're consuming.
I generally follow this convention:

1. Any string literal that contains either ' xor " will be delimited by the other one.
2. For all other string literals, delimit by " if it's meant for human eyes only, delimit by ' if it's meant for computers as well.
> Pretty straightforward choice.

It is, if you don't think the rest of what I wrote is worth any consideration.
It doesn't make the law right either. Also, those VP's might be doing their job perfectly and the net effect could be that they cannot share data with any non-EU companies stifling their competitive advantages.

There are many real world effects of GDPR and we are just starting to see the pros/cons of it.
Why? None of it requires saving info on an individual server-side. As long as you don't do that the GDPR doesn't even apply to you.
Fun fact: you actually used to be able to do this and it caused some security problems! There are probably zones out there that are still able to do it today from back when it was allowed.
We did this last summer. The 35AH battery we're using cost $64 at the time. I probably ended up spending more per cycle, but I'm guessing my out-of-pocket at the time was lower (and it was kind of a gamble as to how much we'd actually use the rig).
Emacs Mini Manual – The Basics
That makes it seem like gravitationally, the anchor star would just be expanding. My intuition thinks the remaining star gets slammed by debris before the direction and strength of the anchor dissipates enough to launch it away, though my confidence in my stellar intuition is low.
I think he’s just saying that some reasonably large amount are just thrown away. Not most or all.

I threw away at least 20 or 30 after my appendectomy.
Fine, edited. Although you seem to be missing the point...
Android isn’t “free” in the FOSS or Beer sense of the word.

The important bits (hardware drivers and core applications) aren’t open source (AOSP doesn’t include the new default apps or standard libraries.

Also, the important stuff is tied to google services that spy on you.

I think it’s completely reasonable to reject that stack, and lament that no one offers a high quality, supported alternative software stack at a reasonable price.
Here's a thought: regulation like this is, along with the heavy-handed ideology that lead to it, is the reason why the EU is still lagging regarding technical innovation. I think this attitude is the primary reason Silicon Valley took hold in the USA and that the EU has nothing comparable. If the EU wants to legislate itself out of the future they're more than welcome to do so -- and I applaud every site who makes the tough decision to stonewall EU users.
I only know of two group of people, either incompetent or just plain dishonest.

Because they either argue that it is hard to design a database that allows deleting or anonymization, or it is that they're in the business of selling data and won't delete anything and rather lie to their user and customers.

I would be interested to know if there is any other argument for this.
> Most startups are doing their best to be good stewards of data, and they didn't need big global regulation to force them.

lol
> And if you can't depend on it, why have it?

That's a bit rich. There are other conventions in programming that you can't depend on technically but serve a real purpose. Identifier naming and comments are the first that come to mind.

If a language gives you a choice of token that has no semantic distinction then different people will adopt different semantics by convention.

As an aside, calling a tool "opinionated" is code for "my conventions are better than yours". That's fine if I don't have any conventions or I can't decide, but if I have decided, then it's just offensive.
You're making a philosophical argument about what is a "real choice", precisely the problem with the "based-on-principle" GDPR. All this will do is create a big mess if/when this gets into real litigation.
See http://www.michaelnielsen.org/ddi/if-correlation-doesnt-impl...

And

https://www.statisticssolutions.com/structural-equation-mode...
Well, that's true to a degree, but only to a degree. If I wrote my database in Ruby, it would be slow compared to the same database written in C++ (assuming equivalent competency in the developers and equivalent architecture). Even a database written in Java benchmarks slower than the same database with the same architecture written in C/C++. Of course architectural changes can make further improvements.

To the point of Twitter, what we _didn't_ do, despite a lot of Ruby expertise on the team, is write a lot of microservices in Ruby. The reason for that is that I don't think you can get the same RPS out of a Ruby service that you can out of a JVM service, all else being equal. In fact HTTP benchmarks for various platforms show this, if you bother to look.
We use Sonatype Nexus OSS to host private as well as mirror public Maven, npm, and Docker repositories. It took a small amount of fiddling but in less than a day we were up and running, using our LDAP for auth, and it’s been pretty much trouble free from the get go. In fact, we even use it to host our own completely custom internal package system (based on Ivy) for our content packages and database modules. It’s been a huge boon to us.

Artifactory is another competitor but last I checked npm and Docker registries required the paid version.
> This may be an edgy and rebellious sentiment that makes me a radical anti-privacy activist, but unless you're storing levels of information on me that are similar to facebook/google/etc., I do not give a damn whether you're soft-deleting or hard-deleting my IP address and my user account. If your web app is just a web app, and not one component of a vast surveillance octopus which puts tentacles on almost every website using social media buttons and GA.js, I don't think it matters in the slightest.

> It feels like all these tiny companies, one-man shops, and early-stage startups are going to be collateral damage to a regulation designed to stop facebook and google from knowing a horrific amount about everyone. In fact, it feels like a regulatory moat that will do very little to impede any big tech company while forcing me to do twice as much work for any side project I try to develop.

If you don't store PII, you don't have to do any work. Done. If you need to have PII for your webapp to function, you barely have to do any work besides giving the that care people their rights

> There's so much smugness about the GDPR being a "good reflecting moment", etc. which makes me think that people who support the GDPR believe that there's no way detractors could disagree with it in good faith or for good reasons.

I think it's mainly a difference in viewpoint: this is my data for me. Not yours. GDPR makes it easier for me to enforce that. From my perspective I don't care about you violating my rights "in good faith", just like most people don't cares if you trespass on my property and steal something "in good faith".
Learning Nix by Example: Building FFmpeg 4.0
> There is no way on earth that the EU as a whole has looked on your company/project or whatever and decided to screw you.

The rules are enforced via third-party litigation. So its not the "EU", but some lawyer looking for a nice payday that you have to worry about.
> surprisingly clear

This is an 88 page document with extremely dry language. Just confirming your assertion will be time consuming. No wonder many American services would rather shut out EU users than comply.
"The one thing I want to see, but nobody seems to be doing it, is a phone that converts into a desktop."

Samsung has its "DeX Dock" which lets you turn your Samsung phone into an Android desktop, and use the phone as a trackpad.
Ghostery exposed everyone's email address in its GDPR email by not using BCC
Hounding another user like this counts as personal attack, and a virulent strain of it to boot. If you do this again we will ban you.

Please treat others respectfully on this site, regardless of how strongly you disagree with them or their employer.

https://news.ycombinator.com/newsguidelines.html
Can you give me a concrete example where the GDPR forces you to do a lot of relatively costly stuff that are not worth doing otherwise?
> That’s pretty crazy considering smart phones have become ubiquitous relatively recently.

They’ve been a thing for 8-10 years, and the window for kids to be influenced this way is only a couple of years, so we’ve had several cohorts of kids grow from 1-4 in the smartphone era.
It would be good (and bad) for the same reasons it was for microsoft + intel back in the ‘80s.
Which is fundamentally stupid because the beta-carotene to vitamin A pathway is highly limited. The whole idea is wrong. Vitamin A deficient people need vitamin A. Stuffing extra beta-carotene into them will just turn them orange and have other bad effects.
I agree with pretty much everything and I also advocate for that. However, how do you invoice your clients? Its hard to say: hey I'll charge X for each two weeks increment. Client: Great, how many increments will there be? Me: dunno, we'll figure it out somewhere down the increments.

The agile approach is the way to manage projects, but how do you quote them?
If only ifconfig was standardized on the output... it's output has changed over time

Let alone the non-conformity of other OS's like Solaris, HP-UX which really might not matter now. I'm sure FreeBSD matters to someone... just not me
RE: non-deterministic formatting: I'm not familiar with YAPF, but what kind of behaviour does it have? Like if you run it on two copies of the same file you might get different results, or that it's not idempotent (i.e. sometimes YAPF(YAPF(source)) != YAPF(source))?
If you back up a list of things to delete is that GDPR compliant? Ponder.
So basically this is a worm?
for anybody who didn't attend high school in the USA: https://en.wikipedia.org/wiki/Quartering_Acts
The opioid crisis is out of control. Even mussels are ODing.
If they never started those products, then those products have not failed since they never existed.

There's a difference between a product and a company by the way.
I get where you’re coming from, but maybe the bar has to be raised. Computing has gotten more capable and software frameworks are exponentially more powerful than they were even 20 years ago when the internet started going bananas.

The barrier to entry is so low that anyone with a credit card can setup complex IT environments quickly and collect valuable and sensitive information with no consequence to the principals.
I mean, come on.

1. GDPR gives you 40 days to respond. You don’t have to run VACUUM everyday.

2. The entire point of my post was acknowledging that there are costs to being GDPR compliant, and why it’s responsible to have that cost.
You can see how this was done for Fabric, PyPA/Warehouse, and pytest.

General guidelines:

1. One commit with only the automatic formatting. Afterwards you'll be able to skip over it easily with `git hyper-blame` or `git blame $BLACK_REV^ -- $FILE`.

2. Avoid leaving open pull requests. If you do, after landing the blackening commit, blacken all pull requests, too. They shouldn't conflict then.

3. Set up enforcement with pre-commit or CI (you can run `black --check` on Travis or similar).

4. Don't forget the repo badge ;-)
There are plenty of condominiums in WA, especially on the east side.
Ask HN: What is some advice that has made your life better?
This free book is good, but assumes you've done calculus like Stewart's calculus book or something similar https://infinitedescent.xyz

Really the only way to learn is get a beginners book like Stewart, Apostol or Hoffman &Kunze and do the exercises once a day for an hour or less. In a month you'll have done so many exercises you'll begin to understand basics.
> ...the Gaia satellite – which precisely measured the positions, motions, colors, and luminosities of over a billion Milky Way stars ...

Can any physicists here explain how the coordinate system is constructed here?
Seems a cool concept. UI is fine. I think you'd get more interest if you could seed it with fake data for the sake of demo'ing it. Like a proof of concept: "this is what it could be". Just my $0.02.
Maybe I did not word it well enough, too.

I am not sure if being viewer-funded by itself guarantees accuracy and relative lack of bias -- people will support what they want to see, not necessarily what is accurate, and the selection of news on DN front page certainly skews in the left direction. Writing for newspieces that are there however seems to be unbiased.
What is the fear about startups? If you look at the ones you actually use reliably for a decade, very few would have been stymied by GDPR. To add on to this, for every successful startups there seem to be many mostly replaceable ones.

If anything, a reduction in the rate of new startups would indicate that perhaps the market is growing MORE rational, which corroborates the recognition of risk of PII that the GDPR manifests.
It's not breaches that worry me, it's their right to exist in the first place. Credit reference agencies put Facebook in the shade when it comes to abuse of privacy and acting as a law unto themselves.
I'm really curious what could demand $10k per day :) not at all because I don't believe it, but because that sounds very very nice...

Vaguely speaking, the impression I get is maybe you were doing senior-level "emergency fix the unfixable" type work, like recovering a petabyte-sized Oracle database that had chewed itself, or PMing an 11th-hour restructure of a 50% finished 10M-LOC project due in 4 hours. (I recall an uncitable story I read/heard somewhere about a bank that nearly missed a deadline and had 1000 developers working simultaneously to get the work done at the last minute)

(I can't figure out/guess what the lower-rate work might have been.)
How Can We Stretch GraphQL to Its Limits, and Beyond?
If you don't store PII, you don't have to do any work. Done. If you need to have PII for your webapp to function, you barely have to do any work besides giving the that care people their rights

The problem is not the work that the GDPR requires, the problem is the work I'll have to put into understanding the GDPR.

I think it's mainly a difference in viewpoint: this is my data for me. Not yours.

This is the part that I don't understand. If I own a shop, and you come in and buy something, you have absolutely no right to demand that I forget your face and your purchase. In the real world, it's not your data, it's my memory. If I go home and write in my diary that today hekfu bought lots of broccoli, you don't have the right to come to me in five years and demand that I remove all mention of you from my diary at my own cost.

I don't understand the concept of data ownership, because it does not align with how I understand the real world to work.
I am very familiar with Taleb's ranting work on this subject and don't find it at all convincing.
The best monitoring system was the TV in the Ops area scrolling a constantly updating search for #failwhale.
Love the idea of eliminating formatting debates when writing Python.

At the risk of being redundant, I also raise an eyebrow at the choice to prefer double quotes for strings. My company standardized on single quotes, mainly to be consistent with repr and also encourage the use of double quotes in messages displayed to the user.

Everything else seems in order. I might increase the line width to 90 just to use an easier value to remember when configuring editors and other tools ;)
Change one letter in your username and your comment suddenly makes a lot more sense.
This was our plan: prod load, but not super load, not a lot of work that we'd disrupt with bug shakeout. I don't have a good way to simulate production load on our staging environment right now (some day) and that wouldn't have shaken this one out anyway.
Your snarky attitude is the real embarrassment, and you misread into what my feelings are about GDPR.

Agreed that our company handled it poorly -- and that's on our leadership (which is a much much longer story) -- Note: my opinions are not the opinion of my employer.

But your real anger should be directed at your technologist/programmer peers who work at Facebook and Google who take six figure salaries and compromise moral dignity, not at media outlets, or small companies -- and from reading your comments on HN -- we can agree on that.
http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX...

(see below for my response wrt SS85) I prefer to dwell on things like this:

The processing of personal data should be designed to serve mankind. The right to the protection of personal data is not an absolute right; it must be considered in relation to its function in society and be balanced against other fundamental rights, in accordance with the principle of proportionality. This Regulation respects all fundamental rights and observes the freedoms and principles recognised in the Charter as enshrined in the Treaties, in particular the respect for private and family life, home and communications, the protection of personal data, freedom of thought, conscience and religion, freedom of expression and information, freedom to conduct a business, the right to an effective remedy and to a fair trial, and cultural, religious and linguistic diversity.

Below:

A personal data breach may, if not addressed in an appropriate and timely manner, result in physical, material or non-material damage to natural persons such as loss of control over their personal data or limitation of their rights, discrimination, identity theft or fraud, financial loss, unauthorised reversal of pseudonymisation, damage to reputation, loss of confidentiality of personal data protected by professional secrecy or any other significant economic or social disadvantage to the natural person concerned. Therefore, as soon as the controller becomes aware that a personal data breach has occurred, the controller should notify the personal data breach to the supervisory authority without undue delay and, where feasible, not later than 72 hours after having become aware of it, unless the controller is able to demonstrate, in accordance with the accountability principle, that the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons. Where such notification cannot be achieved within 72 hours, the reasons for the delay should accompany the notification and information may be provided in phases without undue further delay.
> Specifically, they're allowed to consent to give you that data, but that's not allowed to be a condition for the use of the service.

You seem to be trying to say that Recital 43 rules out certain types of items as being part of the terms of a contract between a person and a service provider. Namely, the term `you will be shown targeted ads` is an invalid term in a contract. (If this is a misunderstanding of your position, please let me know.)

But this is not what Recital 43 actually says. Recital 43 talks about the performance of a contract. It does not speak to the terms of a contract.

The phrase "performance of a contract" is, I believe, a specific thing in contract law: it refers only to the execution of some established contract.

If Recital 43 or some other part of the GDPR wanted to limit the terms of legal contracts to exclude targeted advertising, they could have done that. But they did not, AFAICT.
Not many companies are going out of their way to learn that their users are lying about their age.