zlacker

[parent] [thread] 6 comments
1. lolind+(OP)[view] [source] 2023-05-26 01:10:42
Yep. Specifically, the temporary containers keep me there for web dev stuff. People will always recommend profiles in chrome, but that can't replace a single hotkey to spawn a temporary throwaway container.
replies(1): >>adastr+zu
2. adastr+zu[view] [source] 2023-05-26 05:45:01
>>lolind+(OP)
How is that different from private browsing?
replies(1): >>lolind+Av
◧◩
3. lolind+Av[view] [source] [discussion] 2023-05-26 05:53:51
>>adastr+zu
I can have 3+ different temporary containers open at once, each with a distinct set of cookies, whereas private browsing gives me only one extra cookie jar.

It's massively helpful for testing interactions between users.

replies(2): >>adastr+mx >>skykoo+nF7
◧◩◪
4. adastr+mx[view] [source] [discussion] 2023-05-26 06:10:18
>>lolind+Av
At least on my chromium variant each private window (not tab: window) gets its own isolated environment.

I frequently use this to log into websites with different user accounts for testing purposes.

replies(1): >>lolind+Yz
◧◩◪◨
5. lolind+Yz[view] [source] [discussion] 2023-05-26 06:37:34
>>adastr+mx
Good to know, I'll take a look!
replies(1): >>adastr+Cw1
◧◩◪◨⬒
6. adastr+Cw1[view] [source] [discussion] 2023-05-26 14:12:01
>>lolind+Yz
To be a little more explicit, I think you need to spawn a private window from a non-private window to get a new environment. If you do it from another private window it uses the same sandbox.
◧◩◪
7. skykoo+nF7[view] [source] [discussion] 2023-05-28 21:36:55
>>lolind+Av
And unlike private browsing windows, they persist across browser restarts until all their tabs are closed.
[go to top]