Live data from Hacker News

No Cookie for You

github.blog

431–440 of 634 posts

Re: No Cookie for You

#431
post #425

Earlier quoted context omitted.

Across Microsoft services like Github, Office365, Bing, LinkedIn, Windows...

yes but what does it mean tracking? having an account? keeping a tab of last time you used it?

Some identifier tied to a time and "place" (service)?

Re: No Cookie for You

#432
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...

>We use Usage Information and Device Information to better understand how our Users use GitHub and to improve our Website and Service.

https://docs.github.com/en/free-pro-team@latest/github/site-...

Re: No Cookie for You

#433
post #24

Earlier quoted context omitted.

True. Also even if you do track your visitors you can use privacy friendly (and ideally selfhostable) Analytics like Plausible https://plausible.io/ so you won't need the banners either. Just don't include facebook like buttons or any of these widgets

I would like to add https://pirsch.io/ :)

This looks really nice, but what’s to stop it getting blocked like all the other trackers once apple/uBlock/etc. add it to their database?

Re: No Cookie for You

#434

Here's a cookie set in my browser from github in a fresh browser: Cookie: _gh_sess=eAAHHEQEjZlQKwq8kaSMpTeHC7tyMGwhVexbpZMVfDbjWCf764z4UMG7S%2FeLZpE0ML5y8%2FnmSEd2ZhiDLBHlZyA08Dj8cGob%2BGXSbGSjztMyc5pdd8uxj8qgxc78SHYw01E6pnOnWHRo7XoeTjKje%2FktOx5wObpjZj8JhfOnngdIlhfxSc1EctIth6RDFIsr2HPw9pbDczMfDwwKuswMrkMIt1JEOglF2L%2BxAdscMjeuXu2zFei58AR%2FwRQ%2FGgY3RbQigWt2w%2BKHDIY7a6pISw%3D%3D--H9M6LNV7YPDc1Dvm--vbgFN9CpCkCxTdfhd…

How is that opaque string any different than any shorter, random string that uniquely identifies the user such as "da39a3ee5e6b4b0d3255bfef95601890afd80709"? They can store whatever data they want in the session store in the backend.

Re: No Cookie for You

#435
Prior to the GDPR making this law, Silktide, the creator of a popular cookie banner software, got fed up, removed the banners and asked the ICO to sue them.

The ICO responded. They said that they accomplished the goal of bringing awareness to cookies and it’s usage.

https://nocookielaw.com/

Re: No Cookie for You

#436

Earlier quoted context omitted.

My understanding is that this kind of active consent that we see as popups everywhere on the web nowadays applies to cookies only. So I would assume that if you can track user activity without a cookie you wouldn't need it. It should probably be stated in the privacy policy though. I'm not an expert in this even though I'm a webdev from the EU, so I'm also interested in other people's input.

GDPR doesn't care if you're accomplishing the tracking with a cookie or using a different mechanism. You're not allowed to do it either way, unless the user has consented.

Since I’m being downvoted: The EU directive that specifically obligates websites to collect informed and active consent for the use of cookies is not GDPR, it’s the ePrivacy Directive.

I don’t believe that one should automatically conclude that just because a cookie requires active consent, any kind of ‘logging’ (local and temporary storage of IPs in order to track website usage) requires active consent. Those are two fundamentally different things.

I’m not saying you should hide the fact that you’re doing it. I’m saying it should be stated in the privacy policy.

Also remember that there is a big difference between ‘personally identifiable information’ and ‘sensitive information’ which are clearly separated concepts in GDPR. Not all collection of data requires active consent.

I did read my EU state’s guideline on GDPR in full, but I’m not an expert. I would suggest reading up on the ePrivacy Directive though, which is still in effect.

Re: No Cookie for You

#437

Earlier quoted context omitted.

The new one I'm seening is you opt out easily enough, but there's a subtly hidden tab called 'legitimate interest' and every ad network claims to have a legitimate interest in harvesting your data, even though you've got no business relationship with them. What should be happening is every company that's done that should be getting massive fines, but instead all the enforcement agencies are doing nothing.

If a company is going to lie or skirt the law about their cookie use, why show the banner at all? It's almost worse to show a decline option that does nothing.

Then you can lobby to change the law because the users-electors are annoyed and it's not your company fault every website is doing it.

Re: No Cookie for You

#439

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…

Why do you think changing the implementation to the server side will comply with the letter of the law? Or perhaps I should ask which law. GDPR doesn't differentiate between the client side or server side, you're simply not allowed to keep information on users unless they've consented to for it to be kept or it is required for a legitimate functionality to which they have consented.

So I am not allowed to keep server logs without consent?

Re: No Cookie for You

#440
post #418

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…

Wait, Google isn't sharing your analytics data with any third parties.

Google usually is the third party, when people are talking about analytics. GitHub removed third party analytics, like Google.

And while Google keeps it's data horde on you to itself, it definitely sells access to you in numerous harmful ways.

Post reply on HN