I have a handy little script called `chrome-new` which I use whenever I want to browse one of those few sites that struggles with Firefox. It just starts a clean Chromium with a throw-away profile, then deletes it when I close the browser.
Not sure - I have never used that flag! I like the idea of managing the profile dir myself, because then I know nothing will leak. For example, HSTS state persists across incognito, allowing fingerprinting. I don't know if --guest handles that differently (probably?) but this way, I can be sure.
Comments
I have a handy little script called `chrome-new` which I use whenever I want to browse one of those few sites that struggles with Firefox. It just starts a clean Chromium with a throw-away profile, then deletes it when I close the browser.
Is there an advantage over just --guest?
Not sure - I have never used that flag! I like the idea of managing the profile dir myself, because then I know nothing will leak. For example, HSTS state persists across incognito, allowing fingerprinting. I don't know if --guest handles that differently (probably?) but this way, I can be sure.