Live data from Hacker News

No Cookie for You

github.blog

381–390 of 634 posts

Re: No Cookie for You

#381
post #296

Earlier quoted context omitted.

what about identifiable information like ip addresses?

generally they are used to protect against DDOS and to have forensic data in the case there is malicious behavior and are allowed as essential to operating the service.

But then they can read the logs and track you anyway?

Re: No Cookie for You

#382
post #324

Somehow the rest of the internet was sold to the idea of "EU is forcing you to put cookie banners, these are nothing but annoyance" rhetoric. Whoever pulled that off, bravo! In reality, the idea was to make people aware that they are being tracked across the web and and give them options and somehow everyone pretended that "No tracking, no banners" is not an option. I am so glad that GitHub is coming forward and poin…

I am pretty sure that they are still tracking you - but Microsoft can easily afford to do tracking in-house...

What do you mean by in house tracking?

Re: No Cookie for You

#383

Earlier quoted context omitted.

GitHub still sends the same personal data to their own analytics endpoint, and the privacy policy which lists third-party data subprocessors [1] has not been updated. See my comment below for details: https://news.ycombinator.com/item?id=25458635 Tracking cookies have little value for GitHub when they can collect data about users that have already been authenticated, and they send the username and user ID as part of…

What is the real value in a privacy policy? I assumed they were similar to EULAs - totally unenforceable. Are there actually any legal repercussions if they lie in their privacy policy? Or is it just ill will that might be accrued (and probably quickly forgotten) if they are found out to have violated their own privacy policy?

GDPR should have given some legal teeth to privacy policies.

Re: No Cookie for You

#384
Since many comments are already a mix-up of "Cookie Law" and "GDPR" (2 separate EU directives) related to Google Analytics, I'll also throw in this bit:

Google Analytics offers an `anonymizeIp` setting [0] to tell it to not store IP addresses of your users. This might be a good default in light of GDPR.

[0] https://developers.google.com/analytics/devguides/collection...

Re: No Cookie for You

#385

Earlier quoted context omitted.

Sure, but considering GitHub doesn't have advertising[1], and they're not sending it to a third party (like Google, who does), it's very hard to imagine any use for first party "tracking" that might harm you. Presumably the most they're using this for is recommending potentially interesting repos to you. [1] Potential concern would be if "Microsoft" was considered "their own", since Bing does have an ad network. But…

Remember that they have LinkedIn as well, and quite possibly could put together a fascinating view of software job profiles, candidates, and repo language/activity to gain value entirely within their own organization. Something like LinkedIn recruitment recommendations improved with GitHub contribution activity might be a fascinating recruitment product: ads are not the only way to gain value.

Yeah, I think my comment is still applicable as is: The risk here is entirely dependent on whether or not "first party" means "GitHub" or means "Microsoft and it's various properties".

My guess is that, at least, for now, it refers to GitHub, as you agree to GitHub's Terms of Service, which doesn't actually mention Microsoft as a party.

Re: No Cookie for You

#387
post #324

Somehow the rest of the internet was sold to the idea of "EU is forcing you to put cookie banners, these are nothing but annoyance" rhetoric. Whoever pulled that off, bravo! In reality, the idea was to make people aware that they are being tracked across the web and and give them options and somehow everyone pretended that "No tracking, no banners" is not an option. I am so glad that GitHub is coming forward and poin…

I am pretty sure that they are still tracking you - but Microsoft can easily afford to do tracking in-house...

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.

Re: No Cookie for You

#388

Earlier quoted context omitted.

Does anyone happen to know of a service like this that is free (not self hosted) for non-commercial, low-traffic sites? Or which costs less than ~$10 per year. I have a basic Github Pages site, and I currently don't know whether anyone is looking at it, beyond the very few who take the time to email me. I don't need (or want) to know anything about my visitors, but it would be nice to know that I'm not simply tossing…

Netlify Analytics is $9/mo

[deleted]

Re: No Cookie for You

#389
post #307
post #3

A lot of people have the misconception that the EU cookie law applies to all cookies, but as the blog post correctly points out, that just isn't the case.

I really hate the lies you see on a lot of new sites that they will send cookies "necessary for basic functionality." You're serving articles, there's no reason for session tracking!

I can see a need for cookies to mitigate against things like DDoS attacks, session management for paywalled content or just to leave comments on articles, favoriting certain sections. There are several reasons why as a reader you would want the site to be stateful.

Re: No Cookie for You

#390
post #324

Somehow the rest of the internet was sold to the idea of "EU is forcing you to put cookie banners, these are nothing but annoyance" rhetoric. Whoever pulled that off, bravo! In reality, the idea was to make people aware that they are being tracked across the web and and give them options and somehow everyone pretended that "No tracking, no banners" is not an option. I am so glad that GitHub is coming forward and poin…

I think you mean "you don't need cookie banners if you have your own identifier" which they certainly do and affords them the luxury of this blog post.
Post reply on HN