|
> – unusable profiles – in Chrome different profiles have different history and extensions, so for security purposes they are above Firefox's containers; I actually don't get the point of Containers at all, being useful only for logging into multiple AWS accounts, otherwise they have no privacy or security benefits; FF has those kinds of profiles too, if you want to you can start it once using the ProfileManager from the command line, (un-)check the box asking if you want to always default to the last profile used or instead always start FF in the ProfileManager UI from now on, so you can choose on each startup.
These profiles are completely separated as well, have their own histories, bookmarks, cookie jars, extensions etc. FF's Containers on the other hand are a less heavy-handed approach, by staying in the same profile, having the same bookmarks, extensions and history but fully separating the cookie jars, enabling you to have (just as an example) Facebook in its own little world, everything else outside that container and/or in their own specific containers, unable to cross-contaminate (to track you) with third-party cookies and the like. Basically, profiles and containers are entirely different levels of sandboxing. |
You don't need a Facebook container, at least since “Total Cookie Protection”. Which itself it's just a better way to “disable 3rd party cookies”, that doesn't break websites, although Firefox's isolation goes beyond just cookies.
https://blog.mozilla.org/en/products/firefox/firefox-rolls-o...
And Firefox isn't the only one that does it, although it may be the best. But Safari, Brave Browser and even Chrome have deployed similar protections. See for instance: https://brave.com/privacy-updates/7-ephemeral-storage/