Total Cookie Protection is a major anti-tracking advance in Firefox that confines cookies to the site where they were created.


My understanding is that this is inferior to temporary containers. Still good that user base whose cookies are separated is growing.


This is an entirely different thing, temporary containers are kind of “private tabs,” total cookie protection is for people who don’t want to get logged out when they close the browser or tab but still want to be protected against third party cookies (without breaking things that depend on them like being logged in on a Microsoft account).


Albeit they function differently, I think the use of containers with temp containers is the way to go. You whitelist the sites you want conserve login and cookies, and blacklist the rest in individual temporary containers. It’s been working for me so far with a few services like Google login not working properly, being in an endless loop of authentication.


There’s a problem with that. Third party cookies used for tracking aren’t being deleted in your whitelisted sites, there are three and a half solutions for that. You can use permanent containers for each whitelisted website to keep them isolated, you let the new total cookie protection do its job (and hope the heuristics don’t accidentally allow tracking cookies too), (half solution) you block third party cookies and risk being stuck in an authentication loop or (best in my opinion) use uBlock Origin which should block most (if not all) of the tracking websites you’ll encounter.


google privacy sandbox will replace 3rd party cookies but they will colect more data with less effort QQ fu** google


Good news. As far as I understand, I can finally disable privacy.firstparty.isolate and disable the Facebook/Google container extensions, right? As long as I’m ok with Firefox’s heuristics that give the green light for partitioned storage access to the third parties I interact with, I don’t see how these extensions (and privacy.firstparty.isolate) would still be of any use with this new state partitioning management


Mmm… I don’t think so… firstparty.isolate do a lot of things. Actually with temporary container correctly configured you can think about turn it off, but IMHO it’s better to follow arkenfox user.js configurations. Actually, you can make your question on his github


So I went through this issue on arkenfox’s github that links to this bugzilla ticket. Judging from these two discussions, as far as I’ve been able to understand, it looks like dFPI does actually the same job of standard FPI, with some relaxed rules that trigger on interaction. So if you’re okay with the heuristics, you get the same level of partitioning from the two. Maybe I’m overseeing something


why would you remove firstparty.isolate? What if it remains enabled? Does something break?


I had some issues with cross-site logins and forms/videos not loading and sometimes it’s annoying. But I’ve never experienced really big issues because of FPI


deleted by creator

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

  • Posting a link to a website containing tracking is undesirable, if contents of the website are behind a paywall maybe copy them into the post
  • Don’t promote closed source software
  • Try to keep things on topic
  • If you have a question, please try searching for previous discussions, maybe it has already been answered
  • Be nice :)

Related communities

  • 0 users online
  • 35 users / day
  • 69 users / week
  • 148 users / month
  • 341 users / 6 months
  • 1997 subscribers
  • 967 Posts
  • Discussion
  • Modlog