- by maggietoo99, an hour agoRated 4 out of 5Feels safer and more controllable per site than blanket policies. Easier to maintain and more visible than whitelists and blacklists. The reason 4-star instead of 5-star is only that that the "no container" is not an automatic, isolated "Temporary container" (black underscore). Eliminates the need for trying to "manage" "allow" or "disallow" cookies, etc.., so that a website has all it needs to function correctly, but cannot "share" information with other websites. It is good to be able to let certain cookies (required for site preferences, etc.) to be white-listed - however, more help is needed to determine WHAT a cookie is for, so you know what to white-list.
- by Jeremy, a month agoRated 4 out of 5This is a great tool and I would love to see it somehow integrated into mozilla's multi account container feature. However, it is very complicated, reducing ease of use and understanding.
- by Firefox user 13007505, 2 months agoRated 4 out of 5What is temporary here, it doesn't delete containers just leaves a big row in the Multi-Account containers overview. Makes it all a big mess.
btw: Is there a way to delete multiple containers instead of the one by one method?
Reply the response:
Thank you stoically, very much appreciate that you took the time to reply.
The links are informative, hope that somebody will come up with a solution, then I will use your add-on again.
Developer responseposted 2 months agoThe temporary containers are deleted by this Add-on, however, Multi-Account Containers re-adds them because of Sync Feature, see https://github.com/mozilla/multi-account-containers/issues/1675 and https://github.com/stoically/temporary-containers/issues/371