Live data from Hacker News

GitHub is adding web cookies for enterprise users

github.com

61–70 of 86 posts

Re: GitHub is adding web cookies for enterprise users

#61
post #47
post #21

Earlier quoted context omitted.

There are no laws in Australia requiring cookie banners, and yet I get hit with them constantly. So the law is clearly not the reason for these annoying banners.

The EU laws require the banners to be shown to all EU citizens regardless of the country they're in, right? I think the only way to be absolutely safe is to show cookie banners everywhere.

No it doesn't. It stipulates that the site operators need informed consent to track you using cookies. So what they do is nag you with dark patterns to obtain it, creating an annoying experience.

Re: GitHub is adding web cookies for enterprise users

#62
post #32

Earlier quoted context omitted.

They almost feel like a passive-aggressive thing at this point. There's no reason a cookie banner needs to be a modal dialog that blacks out the rest of the web page.

It's a way for them to protest about having to place a banner at all.

AFAIK GDPR requires that consent can be removed as easily as it was granted - where's the modal pop-up on every screen allowing me to revoke my prior consent and have their advertising partners delete any gathered data?

Re: GitHub is adding web cookies for enterprise users

#63

Earlier quoted context omitted.

> There's a browser extension that The problem with browser extensions is... you have to trust them.

That's a valid concern. This extension is open source [1], if you were to want to see what's happening under the hood. [1] https://github.com/cavi-au/Consent-O-Matic

Thanks for the recommendation! I am indeed sketched out by most extensions that require the all-hosts permission but this one does seem pretty legit so I'll give it a shot.

Re: GitHub is adding web cookies for enterprise users

#64

I don't understand why people care about cookies. The stupid cookie banners are an actual nuisance.

They almost feel like a passive-aggressive thing at this point. There's no reason a cookie banner needs to be a modal dialog that blacks out the rest of the web page.

It’s like prop 65 posters warning about carcinogens in California. If people insist you warn them about something they are doing, you get around it by forcing everyone to do it for everything so people start ignoring them.

Re: GitHub is adding web cookies for enterprise users

#65
post #17
post #8

People seem outraged about the marketing cookies. Genuine question: Why?

> marketing cookies Do you think ads have gotten better or worse over time? I think it's unequivocally worse now than it was then. There's a point where you're fed up with seeing the same ads for products you don't want or need.

Do you think cancer has gotten better or worse over time? Because that's what ads are, rhe cancer of any media they touch.

Re: GitHub is adding web cookies for enterprise users

#66
post #39

Earlier quoted context omitted.

Payment gateway integrations might be one of the few legitimate non-advertising use cases I can think of for 3rd party cookies. What makes you say they don't need them?

Do you mean that if you reject the cookie then the transaction will fail?

I worked for a payment gateway years ago, when safari rolled out their initial blocking of third party cookies back in 2013 it broke some of our transaction flows yes.

There are a bunch of different kinds of payment gateway integrations, with various tradeoffs.

However a common pattern, at least at the time, was to use an iframe with the payment form in it.

Our form was multi page, and used cookie based sessions to track state between pages, so when they started being blocked, the payment form stopped working for safari users. The solution we chose at the time was to put the session id into the URL, but that has it's own security issues. There are other ways to address that particular issue that don't involve cookies, but would have required a significant rewrite of the system.

Some potentially legitimate ongoing use cases for 3rd party cookies, would be remembering payment details, and one click checkout across various sites that use the same payment gateway.

Re: GitHub is adding web cookies for enterprise users

#67

Earlier quoted context omitted.

They almost feel like a passive-aggressive thing at this point. There's no reason a cookie banner needs to be a modal dialog that blacks out the rest of the web page.

It’s like prop 65 posters warning about carcinogens in California. If people insist you warn them about something they are doing, you get around it by forcing everyone to do it for everything so people start ignoring them.

>If people insist you warn them about something they are doing, you get around it by forcing everyone to do it for everything so people start ignoring them.

Who does "you" refer to in this sentence? A random business that doesn't like the warnings? How can that random business force everyone to do it for everything?

Re: GitHub is adding web cookies for enterprise users

#68

I don't understand why people care about cookies. The stupid cookie banners are an actual nuisance.

Yep, this is why we can't have nice things. Nice things sometimes sound nice initially but they have major design flaws and made by people who don't know much about things. But these people have monopoly of coercion on you so you can't really do anything about it.

> “The legislative department is everywhere extending the sphere of its activity, and drawing all power into its impetuous vortex.” -Madison, Federalist No. 48

HN is still in a love affair with GDPR.

Nice things need to be thoroughly thought out.

Re: GitHub is adding web cookies for enterprise users

#69

Earlier quoted context omitted.

Makes a lot of sense. Paying customers are far better ad targets than deadbeats.

Fair enough. I guess I'll just have to ublock

At this point, it is hard to say how well integrated they are. If the blocking is not straightforward.

Re: GitHub is adding web cookies for enterprise users

#70
post #16

Earlier quoted context omitted.

Only consent is needed for cookies that aren't strictly necessary. https://gdpr.eu/cookies/ If a site is asking for consent, they're either idiots who don't understand what the law requires of them or they intend on tracking their users.

How do I grant universal consent to be tracked so that I can browse the web in peace? The law failed to consider this and made the browsing experience considerably worse for those of us who couldn't care less about being tracked. Not to mention teaching users who are not tech-savvy to blindly click "I Accept" and "I Agree" without thinking about it which is an absolute disaster since such users cannot distinguish bet…

My guess is that the original intent of the legislation wasn't to force users to click about 20 buttons in order to opt-out (IANAL but this seems to run directly counter to the mandate that it must be as easy to withdraw consent as it is to give it?). I agree that the current experience sucks, although unlike you I'd prefer not to be tracked. That being said, the EU has shown that it continues to iterate legislatively on issues around privacy - see the recent Digital Markets Act, for example. I guess my point is that legislation doesn't always get it right the first time, but I'd much rather see an evolutionary approach to fixing a problem than simply throwing up our hands.
Post reply on HN