https://groups.google.com/a/chromium.org/g/chromium-dev/c/IZ...
In response to asking about supporting multiple profiles between different tabs.
>Extraordinarily difficult. I would expect person-years of effort for this, as the link between profile and window is deeply ingrained throughout the code.
Chrome doesn't support containers because it would take a big investment that no one is currently willing to make. Google doesn't want to spend millions of dollars and deprioritize more important work for a niche feature that not that many people benefit from.
I'll go with incompetence over conspiracy.
You're done. Build while fresh.
P.S.: Microsoft is actively rigging its software, lastly VS-Code just for these things, but it's another can of worms I have no desire to open again.
"... Chrome is built on foundational but really wide C++ APIs, such as the //content/public layer. We examined what it would mean for us to build Rust components against these types of APIs. At a high level what we found was that because C++ and Rust play by different rules, things can go sideways very easily.
For example, Rust guarantees temporal memory safety with static analysis that relies on two inputs: lifetimes (inferred or explicitly written) and exclusive mutability. The latter is incompatible with how the majority of Chromium’s C++ is written. We hold redundant mutable pointers throughout the system, and pointers that provide multiple paths to reach mutable pointers. ..."
[1] https://security.googleblog.com/2023/01/supporting-use-of-ru...
I sometimes wonder whether Google was strategically preempting this paradigm when they mainstreamed ephemeral sessions under the framing of sneaky mode.
If you don't want cookies, you can turn them off for all sites (with exceptions) or for some sites.
Cookies aren’t inherently bad. If a second party asks me to hold on to something while I’m actively engaged with it, that’s typically fine. At the end of the day, though, I’m deciding what to take home.
I'd like that too, how can you do that?
I've been using Firefox containers for a while. When I open a new tab it opens in the default non-container which carries it's own storage cesspit.
For me the shortcut is alt C.
I just opened a new tab normally, with no shortcut, and it automatically created a fresh temp container "tmp2". I logged into HN and replied to this comment. I will close the tab now, and in 5 minutes, due to another Temp Containers setting, everything in the temp container will be wiped.
The whole silly "No Container" business goes away entirely.
See https://github.com/stoically/temporary-containers/wiki/Autom...
For me, it's the best setup I've found in terms of cookie/session management. By default, I do want every new tab I open to come with a clean slate of no cookies, local storage, SQLite, or whatever other storage/tracking mechanisms are invented. If I need to open up a Google service, I simply open a new tab in my Google container. Combined with a good password manager to quickly login to lower security accounts, it is a marginal increase in work managing sessions, with the benefit of not tracking all your cookies and history around everywhere you go. The features aren't perfect since it's not a workflow optimized for consumer simplicity, but it works for me.