Live data from Hacker News

Where did all the “reject” buttons come from?

noyb.eu

31–40 of 127 posts

Re: Where did all the “reject” buttons come from?

#31

I've set my browser to delete cookies at close. You can accept all cookies without problem, and after lunch everything is forgotten. A few websites that I go to often get special treatment (Hacker News!), because I'm to lazy to press ok each time.

That would mean they get deleted every few months when an OS update forces me to reboot only. Why would I ever close my browser?

Re: Where did all the “reject” buttons come from?

#32
post #14

I've set my browser to delete cookies at close. You can accept all cookies without problem, and after lunch everything is forgotten. A few websites that I go to often get special treatment (Hacker News!), because I'm to lazy to press ok each time.

That's not the same. This forces you to close the browser regularly and they can still track you while your browsing session. Your approach doesn't say no, it's a yes with expiration date.

In the case of server side fingerprinting (used by any vendor offering cross device linking), it's likely not even providing the time limit people using this strategy believe it does

Re: Where did all the “reject” buttons come from?

#33
post #12

Earlier quoted context omitted.

Because otherwise a business would be violating a law if they serve European customers?

The post you’re replying to mentions many reasons why that law is ill considered.

It might be but it’s still the law?

Re: Where did all the “reject” buttons come from?

#34
post #15
post #4

The EU cookie legislation was a mistake made by tech-illiterate bureaucrats that ruined the Web to a large degree. It's something that could've been built in to the browser. I have a hard time understanding why one would dedicate their time to this.

You are confusing the law with the intentionally bad implementation. And it was implemented in the browser as Do Not Track but websites ignored it https://en.m.wikipedia.org/wiki/Do_Not_Track

No he isn't. The law is precisely what allows the intentionally bad implementations. Anyone could have foreseen this. Hell we already knew this would happen based on the earlier cookie laws.

The EU should have mandated an interaction-free solution like Do Not Track. They could have.

Re: Where did all the “reject” buttons come from?

#35
post #10

Just remove cookie banners unless you’re using an ad network (this includes keeping them if you’re using google products). Users want to use your website rather than look it through a porthole, understand that websites remember you, and cookie banners are killing the web in favour of closed app stores.

Analytics also require consent. There are some non-mainstream solution that promise that no consent is required, but you better make sure with a lawyer. Sadly, every marketing person and their dog insist on having analytics. Even more sadly, every product person is not capable on putting their foot down against an obviously bad cookie banner UX.

Fathom Analytics is quite fool proof. No cookies (hence no consent) required, completely anonymized data that still identifies unique visitors and provided valuable analytics.

Re: Where did all the “reject” buttons come from?

#36
post #4

The EU cookie legislation was a mistake made by tech-illiterate bureaucrats that ruined the Web to a large degree. It's something that could've been built in to the browser. I have a hard time understanding why one would dedicate their time to this.

> It's something that could've been built in to the browser.

It was; nobody cared (due to lack of any legislation/enforcement); it died. https://en.wikipedia.org/wiki/P3P

Re: Where did all the “reject” buttons come from?

#37

The button is more prominent, yes. And it's still useless. Most tracking now comes from the "legitimate interest" purposes that you need to actively object to, which is buried in a tertiary hidden panel or not available at all, or even forces you to object to several dozens of trackers one by one.

What are these 'legitimate interest' things, and is it even possible to object to them, legally speaking? I have never seen these I believe, unless you mean 'analytics cookies' and 'functional cookies', which I never saw hidden. I did presume that a 'reject all' included rejecting these cookies, if not it would be great to know.

Re: Where did all the “reject” buttons come from?

#38
post #15

Earlier quoted context omitted.

You are confusing the law with the intentionally bad implementation. And it was implemented in the browser as Do Not Track but websites ignored it https://en.m.wikipedia.org/wiki/Do_Not_Track

No he isn't. The law is precisely what allows the intentionally bad implementations. Anyone could have foreseen this. Hell we already knew this would happen based on the earlier cookie laws. The EU should have mandated an interaction-free solution like Do Not Track. They could have.

There is an interaction-free solution; it's called 'do not track' (as in, not tracking users). The EU don't mandate it, since that would probably be considered over-reach: if Web sites want to break their UI and annoy their users, they're free to do so.

Consent for personal data is implied when performing services for a user (e.g. logging in, shopping carts, remembering high-scores, etc.).

Interactions are only needed when consent is not implied; i.e. when the personal data is not performing a service for a user; i.e. when the user is the product, not the customer.

Re: Where did all the “reject” buttons come from?

#39
post #12

Earlier quoted context omitted.

Because otherwise a business would be violating a law if they serve European customers?

The post you’re replying to mentions many reasons why that law is ill considered.

I don't see any reasons in that post as to why the law is ill conceived.

Re: Where did all the “reject” buttons come from?

#40

I wish cookie settings were part of the browser (e.g. I want to reject all marketing cookies but not essential ones), have a way in JS/HTTP to indicate the type of the cookie, and never see those cookie popups again.

Many of these cookies settings can be 'unset' by browser-settings. The HTTP server can set cookies all it wants, but if your browser throws them away between sessions, they can't be used to track you between sessions. (They still can aid tracking you within sessions, to what degree that is bad depends on the specific definition of 'sessions').

Firefox has a pretty decent system for this I believe. They also try to go against alternatives like 'local-storage' and a whole slew of other attempts at fingerprinting / creating super-cookies.

Post reply on HN