4 ms·
Hmm, there are features that one literally can't provide without state (cookies). I think the real problem here is that the technical feature of cookies provid
by jrochkind1 8y ago
Hmm, there are features that one literally can't provide without state (cookies).
I think the real problem here is that the technical feature of cookies providing browser state is a poor proxy for what EU/DPA _really_ wants to regulate, which is privacy-related tracking.
There are tons of sites I've written which use cookies, but have no ads and perform no user-tracking whatsoever, not even Google Analytics. It is true that cookies are the _easiest_ (if not the only) way to do the other; but making "cookies" the thing that gets effectively "regulated"... I realize this isn't necessarily the intent of the regulations, but I'm suggesting it's part of what results in the situation troy mentions. There are very few sites that don't use cookies; there are or at least could be more sites that don't track you in a privacy-compromising way, to train the user that this is the same thing is just too much noise for the user to actually make any discernments.
- nashashmi 8y agoWhat features? Is local data storage a possible substitute?
- mort96 8y agoMost discussion about the EU cookie directive doesn't mention it, but not all cookies require consent. From https://privacypolicies.com/blog/eu-cookie-law/#some-cookies-dont-need-consent https://privacypolicies.com/blog/eu-cookie-law/#some-cookies...: "This shall not prevent any technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service." Of course, no website will ever tell you "Hey, we're using cookies to track you"; it's in most companies' (both legal consulting companies' and website owners') best interest to keep people ignorant. Consulting companies want website owners to be scared and buy legal consulting services, and website owners want people to think that the pop-ups are a result of stupid EU legislation and not because they are actually being tracked.
- jrochkind1 8y ago" in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service." If I need to get explicit opt-in for "So, remembering your shopping cart when you come back requires cookies, that okay with you?" I'm not sure how much better that would be. It's still gonna be information overload "false positives". But I think that is what the regulations actually intend. "We need cookies to give you: Shopping cart; search history; login to your account; whatever -- opt in or out to each one, you can still use the site just without those features if you go out." A) That is actually fairly expensive to implement. B) I think it _still_ wouldn't accomplish the goals, it's still _way too much information_. Nobody cares whether or not you use cookies to implement a shopping cart. They care about things related to "tracking", especially aggregated tracking, and profiling. C) But you are exactly right that no company is ever going to tell you what you _really_ care about. Unless regulations make them maybe. These regulations were trying. Not there yet.
- mort96 8y agoI'm fairly sure I agree with out that the law wouldn't achieve its purpose even if it was implemented "correctly", and it certainly doesn't achieve its purpose with how it's implemented by websites today. I considered adding a short sentence about that, but ended up not doing it. I'm just tired of the vast amount of misinformation out there, and people discussing as if the directive applies to all cookies and only to cookies. I'm not entirely sure if a user account at an online store would require consent; in my view, cookies would be "strictly necessary" to provide the user experience a user expects which includes being able to create an account to save their shopping cart and view their order history, while using cookies to show tailored product suggestions wouldn't be. However, IANAL and I haven't even read through the text of the directive. In any case, the vast majority of the times I see the cookie notice are times where there are exactly zero reason to use cookies (or other methods of persistent storage) other than tracking, such as blog posts and news articles. Every single one of those websites would be able to get rid of their annoying pop-ups if they just spied on their users a bit less.
- deleted 8y ago
- goto11 8y agoI'm not totally sure what you are arguing, but if you don't use the cookies for tracking, then you don't need to warn or inform the user. And if you use some other kind of tracking beside cookies, you still need to warn.
- Veen 8y agoYes, there is a lot of nonsense talked about this. The GDPR makes it clear that sites don’t have to ask for permisssion to place session cookies and other cookies that are essential to the functioning of the site.
- deleted 8y ago[deleted]
- mr_toad 8y agoClose to 100% of the cookies I see in the wild are not to provide state. There’s only a handful that need them for logging in. Most sites I visit I don’t want to interact with, I just want to read.
- wolco 8y agoAny site requiring a login will most likely use one.
- yjftsjthsd-h 8y agoYes: One. Not 20-50, including cookies for ads, user tracking, and whatever else they're doing this week.
- T-hawk 8y agoTracking is state. It's just that the state is used for advertisers' benefit rather than yours.
- cameronh90 8y ago"Hmm, there are features that one literally can't provide without state (cookies)." Silent cookies aren't completely banned by the GDPR/cookie laws, only cookies that aren't necessary to provide the service requested by the user. That's sort of vague, but I think mostly obvious what is intended there. It's pretty easy to operate within the spirit and letter of the law: Shopping baskets, load balancer cookies and login tokens are fine (provided you only use them for those purposes!), third party advertising tracking cookies are absolutely not (without consent). More info here: https://ico.org.uk/for-organisations/guide-to-pecr/cookies-and-similar-technologies/#consent https://ico.org.uk/for-organisations/guide-to-pecr/cookies-a... Lawyers have told me that you do not even need consent for Google Analytics, unless you enable the data collection for advertising features. It appears to me that there's intentional bad faith misunderstanding from some, regarding both the cookie law and GDPR, in order to try and paint it as unworkable.
- jrochkind1 8y agoMeanwhile, even though the _only_ user-tracking we do where I work is Google Analytics (no advertising features) (and you say your lawyers say you don't need consent for that) -- the official word on high where I work is all our websites need the stupid "i consent to cookies" banner if we use cookies. So, yeah, it's a mess. These "extra" warnings are contributing to user fatigue, I agree with troy hunt that users are just gonna ignore them all. I also understand why a small organization can say "Well, I don't really understand if we need it or not, the lowest risk thing to do is just to supply it." And there's no law _preventing_ you from supplying an unnecessary pointless cookie warning banner...
- deleted 8y ago[deleted]
- FridgeSeal 8y agoThat’s more the fault of the higher ups for not understanding the law correctly, which really, is on them because the EU went to quite a bit of length to make the document readable and if execs/managers aren’t smart enough to know the difference between necessary and tracking cookies on their own site, then that’s really their own fault.
- tripzilch 8y ago> Hmm, there are features that one literally can't provide without state (cookies). The biggest lie in most cookie warning popups is that you need to accept them for the site to function. It is often not true. Those are session cookies and you don't need to warn users about them, they're just allowed. I didn't know this, and neither do any of the cookie warnings mention this. So like many people I thought the cookie law was the stupidest thing ever because like you say, you gotta have state. But the session cookies used to make a site hold state, those aren't considered tracking. When I learned about this little fact, it changed my opinion about the cookie law considerably.
- franga2000 8y agoI went through a similar thing which resulted in me removing cookie warnings from all but one of the websites I manage, yet I still believe that the law is stupid. It's like outlawing guns to solve your murder problem without considering all the other murder weapons all while keeping the act of murder itself legal. As far as I understand it, the GDPR does everything and more than the cookie law was supposed to, so IMO it's about time we put that disaster behind us.
- ATsch 8y agoThe directive containing the cookie law (ePrivacy) was indeed being revised in 2017. I haven't heard much about it since though. It Essentially enshrined the Do Not Track header into law and also expanded the rules for privacy etc of sms to internet messeging services. I wonder how much of the information in this thread is about the original directive and how much is about the new one.
- gowld 8y agoThat's not quite right. On the web, your approximate unique ID is your browser fingerprint. That can be used to join your activity to other activity. Your session cookie is your activity for your browsing session (or for users who never quit their browser, your entire computer uptime). Think about it -- a cookie is information the web server gives to you; it's essentially a bookmark to your current position in the app. The server already knows where you were -- it saw you there!; it just doesn't know that you want to go back there on your next HTTP request. Tracking data is data you give to the web server. Cookies are only one primitive to enable tracking. Cookies can be replicated by URL query parameters, subject to size constraints.
- rjf72 8y agoI'd distinguish between first and third party cookies. Is there any legitimate and reasonably necessary purpose for third party cookies? And similarly is there any undesirably exploitative use of first party cookies? As I am not a web developer, these are not rhetorical questions.
- samat 8y agoIf only we had a browser API which would identify user preference on tracking! Oh wait https://en.m.wikipedia.org/wiki/Do_Not_Track https://en.m.wikipedia.org/wiki/Do_Not_Track
- dmitriid 8y agoOh wait. It's now used for fingerprinting and tracking, and Safari is removing it: https://developer.apple.com/documentation/safari_release_notes/safari_12_1_beta_3_release_notes https://developer.apple.com/documentation/safari_release_not... --- quote --- Removed support for the expired Do Not Track standard to prevent potential use as a fingerprinting variable. --- end quote ---
- rmc 8y agoThere are many legal reasons for processing personal data. Consent is one, and that's what all this is about. "Legitimate reasons" is another. You can process personal data (use cookies) under that reason, and you don't need to ask for consent.