Temporary containers in automatic mode would make cookie autodelete and multi-account containers redundant.
Yeah, it does, maybe not with MAC since you could need it to keep your cookies, though.
I also recommend Redirect AMP to HTML and CSS Exfil Protection, and in my opinion Privacy Redirect is also redundant, I prefer something like Violent Monkey for that since at least you could add more scripts or stuff.
I do use Redirect AMP to HTML, but I didn’t initially think of it as a privacy extension. Thinking about it more, it would keep you off of Google’s AMP CDN, which is a privacy win. I’ll add it to the post.
Cookie Autodelete helps when you have a long-lived temporary container, usually from shift-clicking links to open in a new tab, which ends up inheriting the same container.
good point, that has bugged me a bit actually as I usually pin a search tab and it autoopen results in a new tab of same container. I just looked for a feature request to make this optional but only found the opposite ( https://github.com/stoically/temporary-containers/issues/245) maybe I’ll request that feature though it looks like many people are using Containerize now.
Is it possible to have full screen on start on Firefox with resist fingerprinting enabled ? My resolution is very common so I don’t worry about it…
deleted by creator
That and their linked Firefox Configuration Guide for Privacy Freaks and Performance Buffs!!! and
I’ve been using arkenfox user.js for a while but the broken ux from strict enforcement is a bit rough for those with expectations of being able to browse normally. I keep a more open profile for visiting must work sites.
