←back to thread

332 points vegasbrianc | 8 comments | | HN request time: 1.055s | source | bottom
Show context
ryandrake ◴[] No.42142148[source]
People blame the cookie banners themselves or the legislation that "made them necessary" but somehow never seem to blame the web companies for doing the naughty things on their websites that make them subject to the law.

The "cookie banner problem" exists because it's primarily end users that are shouldering the burden of them, and not the companies. For the company, it's a one time JIRA ticket for a junior software engineer to code up a banner. For everyone else, it's thousands of wasted seconds per year. Make the law hit companies where it hurts: their balance sheets.

replies(11): >>42142202 #>>42142212 #>>42142251 #>>42142326 #>>42142345 #>>42142452 #>>42142625 #>>42143095 #>>42143203 #>>42144003 #>>42144503 #
legitster ◴[] No.42142202[source]
> never seem to blame the web companies for doing the naughty things on their websites

Part of the problem is that the law didn't seek to distinguish between tame first-party cookies and the really naughty third-party cookies so the burden is equal regardless of how malicious the service is.

> For the company, it's a one time JIRA ticket for a junior software engineer to code up a banner.

This is actually not true. There's a lot more that goes into a cookie banner than you might realize, and there's now an industry dominated by a small handful of players (Osano vs OneTrust)

replies(7): >>42142217 #>>42142245 #>>42142273 #>>42142291 #>>42142347 #>>42142352 #>>42150500 #
ffsm8 ◴[] No.42142245[source]
It did though? You don't need a banner for actually legitimate use (session Cookie, settings, etc)

The things they're calling legitimate use just isn't, which is why they need banners.

replies(2): >>42142265 #>>42142396 #
1. legitster ◴[] No.42142396[source]
The elephant in the room is that almost no one wants to host website without at least some sort of website analytics service, which does not fall under legitimate use. So that's why even a small blog is going to have a cookie banner.

There are some analytics companies out there that advertise cookieless analytics, but they are either a) too simple for enterprise or b) a much, much worse privacy and compliance risk.

replies(3): >>42142801 #>>42144795 #>>42146454 #
2. ffsm8 ◴[] No.42142801[source]
Even this can be done without a banner, as long as these analytics do not contain any way to link them to individuals/specific users

It's admittedly sound advice to create a banner for such a usecase however, as sanitizing all user data from these events is hard to guarantee, and you'd have to do just that to keep it legal

replies(1): >>42146295 #
3. Earw0rm ◴[] No.42144795[source]
The other elephant is that while everyone has analytics, only one in five companies pays someone with an actual clue how to interpret them to look at them regularly, and only one in five of those companies has a decision making structure that allows them to act meaningfully in response to insights gained.
4. XCSme ◴[] No.42146295[source]
I think it's impossible to be 100% legal.

Many times, the user IP, which is considered PII, is stored in various servers/routers log that you have no access to...

replies(2): >>42148595 #>>42148724 #
5. account42 ◴[] No.42146454[source]
Well, too bad.

When it comes to processing other people's data you don't get to do whatever you want.

Maybe try running a website without analytics before throwing a tantrum.

replies(1): >>42148424 #
6. ryandrake ◴[] No.42148424[source]
Yea, companies are so used to laissez faire that when they're finally told "too bad, so sad" they throw a tantrum, sue, cry, and eventually comply as maliciously as the possibly can, to show the world how upset they are that they can't simply do whatever they want.
7. ◴[] No.42148595{3}[source]
8. ffsm8 ◴[] No.42148724{3}[source]
Lots of misinformation on the internet wrt this, and I am not a lawyer either.

It's especially tragic because Google serves you countless factually incorrect articles if you search for gdpr, which doesn't help with this endless amount of confusion.

You might be interested to know that an IP address isn't actually PII, because that's a concept of California privacy regulation and they don't care about them

https://techgdpr.com/blog/difference-between-pii-and-persona...

It's a different story for gdprs personal data however. Because there are individuals with static IPs - which makes it possible to link these IP addresses to individuals. If you could only omit these, you could technically use ipadresses however you want too. But I admit that that's kinda unrealistic ( • ‿ • )