(no title)
Fats
|
5 years ago
What I've been doing was to set up a browser profile (local) for each main context. If I have a set of work accounts (google, github, etc.), I have a 'work' profile for it. This isolates all cookies related to 'work' at once, as well as bookmarks, saved tabs, extensions, and settings. It's a total context switcher.
rozab|5 years ago
drdaeman|5 years ago
Like, allow some tracking & advertising for "shopping" container, but block it otherwise. I don't mind having a special self-curated image where my in-scope browsing is tracked and analyzed. Now, I just have a separate browser (Chrome) for this - because it's more straightforward and less error-prone.
Or a sandbox development & local resource management profile where nothing but localhost and LAN addresses are allowed. And then block such access for any other profile - for security reasons.
Or allow, let's say, Grammarly extension on a few selected websites (like HN), where all I write is public and I would benefit from machines aiding my writing without any privacy concerts, but don't give it any chance to see my private correspondence.
Unfortunately, that's not possible with containers, and profiles are quite cumbersome.
blibble|5 years ago
I use containers liberally also
aggronn|5 years ago
edit: Apparently this is bad info. I'll have to give it a try again.
satya71|5 years ago
utucuro|5 years ago
codethief|5 years ago
unknown|5 years ago
[deleted]