6 ms·
Preparing for the end of third-party cookies
- ivanjermakov 3y agoWill this make annoying cookie banners go away?
- 7734128 3y agoWe'll probably either be forced to agree to be tracked by Google's systems or forced to sign in to every page. There's no chance that anything positive will ever happen with the web again, it has gotten worse at every step for more than a decade. Especially when Google has any involvement with it.
- parineum 3y agoAll the things that led to getting rid of flash player have been pretty great. CSS is pretty incredible compared to what it used to be. JavaScript is still a train wreck but web assembly holds some promise there. WebGL is also pretty great.
- fyokdrigd 3y agoand all that still didn't give you the creative web that flash allowed.
- dangus 3y agoI’m confused at where we jump to the conclusion that we’ll be forced to sign in to Google’s systems or sign in to every page. How specifically does that come about?
- GenerocUsername 3y agoHi. I work in web and was on the analytics team for a major Canadian based retailer. The death of cookies is absolutely a corporate level driver for the push to authenticate. Trackers being unable to stash long ttl cookies is being replaced by reliable ways to reidentify people... such as logging in.
- amf12 3y agoBut you can still store trackers right? Just not cross reference the tracking cookie with the cookie from other domains.
- eslaught 3y agoI can see this if you go from site X to site Y where you're logged in on both X and Y, and you can correlate (say) the email. But if you're logged into Y (the store) but not X some random referrer, how do you attribute the conversion?
- ilammy 3y agoYou will be kindly asked to log in with Google everywhere, for your convenience and security.
- underdeserver 3y agoI don't think so - those would be first-party cookies.
- jeroenhd 3y agoMost cookies in those popups are third-party cookies, at least for websites with giant lists of third party cookies that require Consent-O-Matic to properly disable. Website relying on first-party cookies are usually rather unobtrusive,
- youngtaff 3y agoThey’re for cookies that are set in the first party context i.e. a third-party script sets a cookie on the first part origin Safari stopped supporting third-party origins setting cookies on themselves many years ago
- underdeserver 3y agoI meant that most sites have first-party cookies (whether or not they have third-party cookies) and you'll still need the banner for those.
- 0x073 3y agoNo
- wilde 3y agoNope. Those are permanently part of the internet now, even if the reason for their existence goes away.
- jefftk 3y agoNo. Cookie banners cover any use of client size storage. That includes things like shopping carts and personalization (purely first party), analytics ("first party"), and ads (usually "third party"). Part of what's confusing here is that "first party" and "third party" are being used in a technical sense to mean which domain the cookies are set on. If on an example.com page JS from example.net causes a cookie to be set on example.com that's "first party", while if the cookie is set on any other domain that's "third party".
- Nextgrid 3y agoShopping carts (and other purely-functional, essential purposes) do not require a consent popup.
- jefftk 3y agoShopping carts require cookies if they go beyond what is "strictly necessary to provide a service explicitly requested by the user". This is quite a high bar, and most shopping cart implementations do not meet it. For example, if you put something in your cart on Monday but then don't purchase, it is not strictly necessary that it still be in your cart should you return on Tuesday to complete your purchase, so holding it overnight requires consent. I wrote more about this in https://www.jefftk.com/p/why-so-many-cookie-banners https://www.jefftk.com/p/why-so-many-cookie-banners and the relevant guidelines are section 2.3 of https://ec.europa.eu/justice/article-29/documentation/opinion-recommendation/files/2012/wp194_en.pdf https://ec.europa.eu/justice/article-29/documentation/opinio...
- janosd 3y agoNo. The cookie banners have nothing to do with cookies per se, they are a consent / information popup required if companies want to store and use personal data beyond what's required to serve you with the website content (GDPR) or they want to store non-essential identifiers on your device (ePrivacy directive). In other words, you are seeing these because marketing departments need BS metrics that measure nothing and are based on some personal data. The internet can happily exist without them as proven by Github[1]. [1] https://github.blog/2020-12-17-no-cookie-for-you/ https://github.blog/2020-12-17-no-cookie-for-you/
- Sytten 3y agoThis will break so many things, that's not even funny. I can already hear customers complain their bank doesn't work on chrome. Maybe this will drive Firefox adoption? (Let me dream please)
- infotogivenm 3y agoI believe third-party cookies have been blocked on Safari and FF by default for many years
- cpeterso 3y agoSafari blocks third-party cookies by default and introduced a new Storage Access SPI so third-party sites that do need cookies can request explicit user permission. This is all part of Safari’s Intelligent Tracking Protection. Firefox doesn’t block third-party cookies by default because that can break sites that haven’t been updated to use the Storage Access API. Instead Firefox’s Enhanced Tracking Protection blocks cookies from a blocklist of known trackers and all other third-party cookies (e.g. new trackers or legitimate use cases) are isolated using Total Cookie Protection (which has the inconvenient acronym TCP). Total Cookie Protection uses double-keyed cookie jars, so cookies from analytics.example included in an example.com page are placed in a separate cookie jar from analytics.example cookies included in an example.org page. This allows both sites to use the same third-party analytics service, but the analytics service sees different cookies for each site and can’t link the cookies to one user’s browsing behavior. https://blog.mozilla.org/en/products/firefox/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/ https://blog.mozilla.org/en/products/firefox/firefox-rolls-o...
- adithyassekhar 3y agoI'd like to be part of the meeting that decided cookie jar was an appropriate name.
- BertoldVdb 3y agoIt only covers third party cookies, not cookies in general. They aren't used that much except for ad tracking. For the few other use cases that exist the offered workarounds are pretty good and more secure than a general wide cookie.
- SkyMarshal 3y agoThe article lists numerous alternatives to replace functionality that 3rd party cookies currently provide. But is there anything that prevents third-party analytics and similar services from creating libraries or services that are deployed under their clients' domain, and then transmit the collected data from client site to third-party service's own database? For example, instead of an embed link like: https://allurdataarebelongtous.xyz/collectitall https://allurdataarebelongtous.xyz/collectitall collecting visitor data on: https://myhometownnewspaper.com/ https://myhometownnewspaper.com/ It's replaced by: https://myhometownnewspaper.com/allurdataarebelongtous/collectitall https://myhometownnewspaper.com/allurdataarebelongtous/colle... Is that possibility going away too, or is it still a loophole? I ask b/c if it remains, it may be easier to implement than some of the alternatives, and it may become more difficult for browser plugins like uMatrix, NoScript, etc. to identify and block these services, especially if they allow the client to customize or obfuscate the embed link.
- infotogivenm 3y agoThe point of killing third party cookies is to prevent a tracking identifier cookie that uniquely identifies your browser from being reused across different sites. So you can of course host your own scripts and run them on your own origin, lets call it site1.com. But when your site1.com includes a third party iframe to e.g. googleanalytics.com, and that frame sets a cookie on itself, the cookie is now silently dropped. Then when site2.com later includes the googleanalytics.com frame, the frame cannot immediately link the two browsers. There are other ways to “link” browsers across origins, like browser fingerprinting or in many cases just IP, but they are not usually guaranteed to be 100% reliable. Blocking third party cookies is standard obvious privacy functionality, but google has held out because it affects their bottom line. So IIUIC they had to wait until they implemented something that protects their bottom line (the chrome-only “privacy sandbox”).
- google234123 3y agoWhat do you mean, anti trust people immediately went after Google for removing 3rd party cookies. Can't win...
- 3y ago
- lol_catz 3y ago[flagged]
- LordShredda 3y agoSo is google singlehandedly choosing which technologies get implemented and deprecated? What if my website depends on third party cookies to function? Aren't they an IETF standard and so I can expect them to be supported? I get that third party cookies are just used for tracking nowadays, but shouldn't there be a less monopolistic way of doing so?
- dangus 3y agoI think it’s pretty well established that third-party cookies are a bad idea. They’ve been turned off by default on Firefox and probably most other browsers for a while now. I can’t see when I would recommend turning them on for any user. Just because something is standard doesn’t mean it never gets deprecated.
- xg15 3y ago> So is google singlehandedly choosing which technologies get implemented and deprecated? With Chrome's global market share at 60% (not even including other Chomium-based browsers), basically yes.
- chatmasta 3y agoIn this instance, Google is actually the last browser to deprecate third-party cookies. Apple and Mozilla disabled them in their browsers over two years ago.
- paulryanrogers 3y agoIIRC, Firefox still enables them by default, albeit with some isolation added not long ago.
- viraptor 3y ago> What if my website depends on third party cookies to function? You have alternatives. Login, oauth tokens, other site-specific API keys, ... > Aren't they an IETF standard I don't think they are required to work the way tracking worked (across sites).
- mediumsmart 3y ago“We Are Preparing To Think About Contemplating Preliminary Work On Plans To Develop A Schedule For Replacing third party cookies with chocolate chips cookies” yawn
- Animats 3y agoWell, for Chrome users. I've had third party cookies turned off in Firefox for over a decade now. So have many Firefox users.
- deleted 3y ago[deleted]
- Voultapher 3y agoSomeone I know that uses Chrome has had them turned off for years and they say it has been mostly fine. The conflict of interest is obvious for Google though.
- zlg_codes 3y agoI have nothing to prepare for, I don't build things that betray trust, Google.
- mooreds 3y agoSome federated identity protocols, including SAML, depend on third party cookies. I've been watching the Federated Identity W3C community group work through some of the issues for a couple of years. You all might be interested in checking out their GH repo: https://github.com/fedidcg/FedCM https://github.com/fedidcg/FedCM