Firefox rolls out Total Cookie Protection by default to more users worldwide

Topic

New Reply

https://blog.mozilla.org/en/mozilla/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/

Firefox is rolling out Total Cookie Protection by default to more Firefox users worldwide, making Firefox the most private and secure major browser available across Windows, Mac, Linux and Android. Total Cookie Protection is Firefox’s strongest privacy protection to date, confining cookies to the site where they were created, thus preventing tracking companies from using these cookies to track your browsing from site to site…

Total Cookie Protection works by creating a separate “cookie jar” for each website you visit. Instead of allowing trackers to link up your behavior on multiple sites, they just get to see behavior on individual sites. Any time a website, or third-party content embedded in a website, deposits a cookie in your browser, that cookie is confined to the cookie jar assigned to only that website. No other websites can reach into the cookie jars that don’t belong to them and find out what the other websites’ cookies know about you — giving you freedom from invasive ads and reducing the amount of information companies gather about you. ..

https://www.ghacks.net/2023/04/13/all-firefox-users-are-now-protected-better-against-online-tracking/

4 users thanked author for this post.

SueW, hyppolyte, lmacri, NaNoNyMouse

Reply | Quote

Replies

How does the purpose of “Total Cookie Protection by default” differ from the purpose of the Firefox Multi-Account Container extension?

Sounds to me that the purpose is the same, but that with the FF M-A Container extension, one has to specify/manage the “cookie jars” (which show up as separate “containerized” tabs in the FF browser for each anticipated to-be-visited website), but that TCP does the “containerizing” automatically (and in the background) without any specification or management.

And that the drawback of the FF M-A Container extension is that if one does not specify a “cookie jar” for a to-be-visited website, it doesn’t get containerized, whereas the TCP containerizes every website visited by default and frees the user from having to do it (or forgetting to do it).

Any thoughts on this?

Reply | Quote

Did you check out?:
https://blog.mozilla.org/en/products/firefox/extensions-addons/how-firefoxs-total-cookie-protection-and-container-extensions-work-together/

 

Windows 10 22H2 desktops & laptops on Dell, HP, ASUS; No servers, no domain.

3 users thanked author for this post.

Lars220, lmacri, WCHS

Reply | Quote

windbg wrote:

Did you check out?:

Just what I needed. Thanks for the reference. It answers many of my questions, especially the section on multiple tabs accessing the same domain!

1 user thanked author for this post.

Lars220

Reply | Quote

Still no ‘Total Cookie Protection’ in Firefox 102.11.0esr (64-bit)

1 user thanked author for this post.

SueW

Reply | Quote