Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The GDPR Is a Cookie Monster

emarketer.com

Post reply on HN
Print view View original

21–30 of 97 posts

Re: The GDPR Is a Cookie Monster

#21

Post by jwineinger »

legitster wrote: post #14
paulie_a wrote: post #8

Earlier quoted context omitted.

I honestly don't get why so many sites are even paying attention to GDPR. If they don't have a presence in the EU, it is irrelevant.

Because GDPR includes provisions for handling US GDPR violators, a lot of security vendors were touting up the idea that if a European fills out a form on your site or gets cookied for any reason, you could be sued.

So they'd file suit in the EU and... what would happen? Some sort of judgment that would prevent a company from starting business in the EU at a later date?

Re: The GDPR Is a Cookie Monster

#22

Post by tpaschalis »

4ad wrote: post #6
iicc wrote: post #5

The "Factsheet" this is about (7 page pdf - https://reutersinstitute.politics.ox.ac.uk/sites/default/fil... ) >All results presented here reflect site activity prior to obtaining consent; the picture may change dramatically once the user provides the affirmative opt-in GDPR requires. So, meh.

Yep. If anything, things are worse now. You HAVE to give consent to do anything useful on the website (so blocking the notice won't work), and in the consent form it's usually very hard to turn tracking off, full of dark patterns. Not legal from the perspective of GDPR, sure, but it seems that everyone is doing it. /edit: downvoted for stating basic facts, amazing.

Well, this way you know what websites you should just avoid, because they're selling your data? The web is a large and open place, you don't need to give consent to anyone.

Re: The GDPR Is a Cookie Monster

#23

Post by jwineinger »

shagen wrote: post #11
paulie_a wrote: post #8

Earlier quoted context omitted.

I honestly don't get why so many sites are even paying attention to GDPR. If they don't have a presence in the EU, it is irrelevant.

It is not. If their customers are in the EU they have to to comply.

What authority would make them comply?

Re: The GDPR Is a Cookie Monster

#24

Post by Uw7yTcf36gTc »

dstroot wrote: post #18

Yeesh... 80 cookies on average for news sites! Down to 60... how many different ways do they need to track one person?

each ad network needs to track you separately. so most of those 60 cookies are not sending data to the news site, but rather to the ad network which bids to display the ad to you.

Re: The GDPR Is a Cookie Monster

#25

Post by pluma »

jwineinger wrote: post #21
legitster wrote: post #14

Earlier quoted context omitted.

Because GDPR includes provisions for handling US GDPR violators, a lot of security vendors were touting up the idea that if a European fills out a form on your site or gets cookied for any reason, you could be sued.

So they'd file suit in the EU and... what would happen? Some sort of judgment that would prevent a company from starting business in the EU at a later date?

I don't know. Why are EU companies paying attention to American laws, again?

Re: The GDPR Is a Cookie Monster

#26

Post by [deleted] »

jstanley wrote: post #15
4ad wrote: post #6

Earlier quoted context omitted.

Yep. If anything, things are worse now. You HAVE to give consent to do anything useful on the website (so blocking the notice won't work), and in the consent form it's usually very hard to turn tracking off, full of dark patterns. Not legal from the perspective of GDPR, sure, but it seems that everyone is doing it. /edit: downvoted for stating basic facts, amazing.

I just don't use sites that won't work until you give consent.

[deleted]

Re: The GDPR Is a Cookie Monster

#27

Post by 4ad »

jstanley wrote: post #15
4ad wrote: post #6

Earlier quoted context omitted.

Yep. If anything, things are worse now. You HAVE to give consent to do anything useful on the website (so blocking the notice won't work), and in the consent form it's usually very hard to turn tracking off, full of dark patterns. Not legal from the perspective of GDPR, sure, but it seems that everyone is doing it. /edit: downvoted for stating basic facts, amazing.

I just don't use sites that won't work until you give consent.

That's idealistic. In my country all the news sites, as well as the local commerce sites do it. Where should I get local news from?

Re: The GDPR Is a Cookie Monster

#28

Post by kodablah »

cyborgx7 wrote: post #7
4ad wrote: post #6

Earlier quoted context omitted.

Yep. If anything, things are worse now. You HAVE to give consent to do anything useful on the website (so blocking the notice won't work), and in the consent form it's usually very hard to turn tracking off, full of dark patterns. Not legal from the perspective of GDPR, sure, but it seems that everyone is doing it. /edit: downvoted for stating basic facts, amazing.

And I hope they will all get heavy fines for doing so. Let's see how well the EU will enforce the GDPR.

Don't we have a glimpse of (lack of) enforcement based on previous incarnations of laws like this? What about this time is special? And why are laws crafted without ample enforcement mechanisms? At the least that makes them toothless, at the most it gives a piece of legislation that can be pulled out and used only when someone wants a reason to punish a company.

Re: The GDPR Is a Cookie Monster

#29

Post by pluma »

Lio wrote: post #19
legitster wrote: post #17

Honestly, the upcoming ePrivacy regulation is much needed- the cookies opt-in/out needs to be handled at the browser level. The current setup is lose-lose for businesses and end users. As a site admin, I have no problem honoring your request to not be tracked. I just can't wait until I don't have to deal with the nightmare that is OneTrust anymore.

You mean like the "do not track" request header? https://en.wikipedia.org/wiki/Do_Not_Track It never ceases to amaze me the number of companies that "value" my privacy but still somehow ignore the do not track header.

Well, Microsoft kinda dropped the ball on that one by making it the default (although they later changed that).
Post reply on HN