Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

No Cookie for You

github.blog

Post reply on HN
Print view View original

531–540 of 634 posts

Re: No Cookie for You

#531

Post by nicky0 »

dessant wrote: post #217

Until now GitHub has sent client-side requests to Google Analytics with a client ID that was also sent in a second client-side request to an in-house analytics API at GitHub for augmenting and cross-referencing user data. The client-side Google Analytics request no longer appears to be sent, but a request containing personal data is still sent to collector.githubapp.com. The privacy policy page which lists third part…

When you say GitHub is collecting personal data in a JS request, what data do you mean exactly? IP address, browser, screen resolution type stuff?

Re: No Cookie for You

#532

Post by gullevek »

Without the LAW we still would have those cookies.

And github wants us to look at them with big eyes who amazing they are.

There should have never been any other cookies first hand.

The end.

Re: No Cookie for You

#533

Post by nicky0 »

Seirdy wrote: post #155
FriedrichN wrote: post #65

This is great. My experience is that many people claim to want analytics for their website but end up looking at it a couple of times and then never using it again. Meanwhile they're sponsoring and bolstering the position of internet tracking giants who - despite their claims - have no regard for user privacy. Just sell your product instead of wasting time and money on bike shedding your website with whatever you bel…

I'd go a step further, and say that most sites don't need cookies either. I wrote about it elsewhere a few days ago: > Avoid having to put annoying EU cookie consent dialogs on your website with one weird trick: > Don't use cookies on your website. > If you want users to be able to sign in to access your premium paywalled/onlyfans content, put that on a subdomain that has cookies and requires login. > (yes this isn't…

You don't even need cookie consent warnings for login cookies. Just for "drive by" ones.

Re: No Cookie for You

#536

Post by BlueTemplar »

p_l wrote: post #441
BlueTemplar wrote: post #373

Earlier quoted context omitted.

How long can you keep people logged in before it becomes the bad kind of tracking?

Depends only on whether the fact that they are logged in is used to process any kind of personal data. The question is not "how long". The question is what data, and what happens to it.

It is, because "logged in" is an abstraction - someone has to decide how frequently you have to contact the server before being considered to have "logged out".

Re: No Cookie for You

#538

Post by BlueTemplar »

rlpb wrote: post #503
BlueTemplar wrote: post #423

Earlier quoted context omitted.

Yes, and it's not like the EU is going to send surprise inspections to go dig into Microsoft's code and databases to check whether they are violating this or not?

They don't send surprise inspections to your house to check if you're engaging in criminal activity, either. My point is that you're moving the goalposts. Law enforcement generally always requires a complaint that justifies an investigation, and people and organisations get away with breaking the law all the time. However that has nothing to do with whether or not GitHub put their website behind a "consent" wall, or…

I'm not moving the goalposts. Aren't you aware that some businesses get regular inspections, which do not require any complaints?

Re: No Cookie for You

#539

Post by dessant »

natfriedman wrote: post #527
spinningslate wrote: post #280

Earlier quoted context omitted.

Came here to say this. Eliminating Google analytics is unequivocally a good thing. A strong B+ assessment. But the blog doesn't say anything about eliminating _tracking_. Personally, I can live with analysis that's used solely for product improvement. If that's all github is doing, then the score goes up to an A. But if they're siphoning off data for any other purposes - whether passing to the mother ship or otherwis…

This is all detailed in our updated privacy policy: https://github.com/github/site-policy/pull/336

Thanks for the update. It appears the data will continue to be sent to Google Analytics from the backend.

Re: No Cookie for You

#540

Post by BlueTemplar »

kelnos wrote: post #451
rlpb wrote: post #387

Earlier quoted context omitted.

Doing "tracking in-house" does not exempt you from GDPR requirements. The requirement is exactly the same: explicit and freely given consent is required to collect extra private information not specifically necessary to provide the service requested.

What "private information", though? If GH is putting in a database the order of clicks that you made to navigate around their site, is that "private information"?

If there's an identifier that can be tied to you (like an IP address), then yes?
Post reply on HN