Live data from Hacker News

No Cookie for You

github.blog

491–500 of 634 posts

Re: No Cookie for You

#491
They still have tracking javascript though:

uBlock Origin has prevented the following page from loading:

https://stats.wp.com/e-202051.js

Because of the following filter:

||stats.wp.com^

Found in: Peter Lowe’s Ad and tracking server list • MVPS HOSTS • Dan Pollock’s hosts file • EasyPrivacy

Re: No Cookie for You

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

There is a lot of wiggle room in "provide the service requested"

> There is a lot of wiggle room in "provide the service requested"

There is, but it is so in any law, because laws can't be specified as precisely as computer code, and an attempt to do so would make them so rigid as to be unenforceable, and hence ignored. But it seems that companies aren't even trying to use this wiggle room, just ignoring it or plastering the damned cookie banners, so I think that it's a good thing for future privacy-oriented laws—when given even the most generous possible leeway, businesses would still rather track their users than attempt to colour within the lines.

Re: No Cookie for You

#493

Earlier quoted context omitted.

That's correct. Using cookies for the user session is fine and does not require consent as long as you really are just using them for the user session. The moment you use them for analytics, you have to request consent for analytics, even if they are primarily for maintaining the user session.

> The moment you use them for analytics Not even then - there are plenty of analytics you can do without a cookie banner, as long as they don't identify the user . Conversely, anything you do other than your obvious business requirements (e.g. if you buy something physical I need some address or identity to verify at pickup) requires consent whether or not it's analytics . (Not a lawyer, not legal advice, jesus just…

There needs to be the same kind if active consent whether it’s “required” or not.

The difference is if you can deny access for those opting out or not.

Re: No Cookie for You

#494
post #443

Earlier quoted context omitted.

No pricing page, and jesus, not even a menu. They want us to sign in before they'll show us pricing? fuck right off with that bullshit.

The pricing page [1] is linked further down, and from the sitemap at the bottom of the page. You have a point they should have made it more obvious though. https://usefathom.com/pricing

Thanks.

Looks like they're only targeting large websites. I've never build a 100k/month traffic website, just lots of (maybe 300+) mom and pop websites.

Wish there was a $12/yr plan for websites that are lucky to get 500 visits a month.

Re: No Cookie for You

#495

They still have tracking javascript though: uBlock Origin has prevented the following page from loading: https://stats.wp.com/e-202051.js Because of the following filter: ||stats.wp.com^ Found in: Peter Lowe’s Ad and tracking server list • MVPS HOSTS • Dan Pollock’s hosts file • EasyPrivacy

That is on github.blog, not on github.com. I was really surprised for a while thinking they use wordpress on github.com

Re: No Cookie for You

#496
post #101
post #47

Great! Even before, rejecting tracking on GitHub was just one click away, same number of clicks as accepting it. I also like the fact that all users get equal privacy rights!

Which is actually mandated by GDPR, but that doesn’t seem to end the endless click required to block cookies on certain websites.

It's definitely not mandated by GDPR. Look how annoying Facebook, Google and countless news sites' cookie banners are. I don't know GDPR, but I'm sure their lawyers do.

Re: No Cookie for You

#497
One of my favorite things about GitHub making this announcement is that GitHub's corporate overlord Microsoft requires us, as a vendor, to put a cookie banner on our websites even though for a while we literally had no cookies at all.

Re: No Cookie for You

#498
post #495

They still have tracking javascript though: uBlock Origin has prevented the following page from loading: https://stats.wp.com/e-202051.js Because of the following filter: ||stats.wp.com^ Found in: Peter Lowe’s Ad and tracking server list • MVPS HOSTS • Dan Pollock’s hosts file • EasyPrivacy

That is on github.blog, not on github.com. I was really surprised for a while thinking they use wordpress on github.com

Oh sorry yes you are right.

I think if they want to claim that they did this because they care about privacy it might be a little hypocritical to have trackers on the blog post where they're bragging about it.

It also looks like there are still several items on github.com that are beacons / stats tracking (and as such are blocked by privacy / ad blocking tools such as uBlock Origin):

https://api.github.com/_private/browser/stats (beacon)

https://collector.githubapp.com

Re: No Cookie for You

#499
post #495

Earlier quoted context omitted.

That is on github.blog, not on github.com. I was really surprised for a while thinking they use wordpress on github.com

Oh sorry yes you are right. I think if they want to claim that they did this because they care about privacy it might be a little hypocritical to have trackers on the blog post where they're bragging about it. It also looks like there are still several items on github.com that are beacons / stats tracking (and as such are blocked by privacy / ad blocking tools such as uBlock Origin): https://api.github.com/_private/b…

The collector.githubapp.com is pretty transparent. It includes basic information like the current page, user agent, referrer, and time zone. All of this could be done via server logs, so it's not like it's that creepy like fingerprinting.

Re: No Cookie for You

#500
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…

>"EU is forcing you to put cookie banners, these are nothing but annoyance" rhetoric

I came to the conclusion myself. I personally see no real need for laws like GDPR and see humanity dealing with cookie banners every day and lost ability for websites to be profitable as pure negatives.

Post reply on HN