161–170 of 446 posts
Earlier quoted context omitted.
Indeed, I'm getting increasingly skeptical that a technical solution is sufficient to fighting surveillance capitalism. Looking forward to see some serious GDPR fines.
Agreed. I'm hoping to see more analogous stateside laws like California's CCPA as well.
Earlier quoted context omitted.
Multi-Account Containers with Containerize is an unbeatable combo. Until Chrome gets something like this (I doubt it), I'm never leaving Firefox because of it.
What does Containerize gain you over Multi-account containers? Is the pattern matching more robust?
In my experience that had better support for per-eTLD temporary containers, so that each site can have its own, and the data can be discarded relatively soon. I also have more permanent containers for things that I want to be able to persist (e.g. work uses SSO so I need to link multiple sites together to log in).
When I used it I found the management in Multi-Account Containers to be onerous (I don't believe it could do automatic containers based on eTLD).
if they were a serious threat, im sure facebook would just _easily_ murder them.
If you haven’t in a while, go check out “Settings for websites” on Safari desktop and mobile. It’s some pretty sane and reasonable stuff.
I use Firefox multi-account containers[1] extensively, it's honestly the primary reason I use Firefox these days. The big win for me is that I _hate_ having to use the Google account switcher, so I basically set up a container for each Gmail account (work, personal, old email, etc). The nice bonus feature is you can have certain sites default to containers. I had a paid YouTube account for a while, for example, so ha…
Damn I also hate the Google accounts mayhem. I will look into those containers. Right now I manually type ?authuser=1 into my URLs to have Google Docs open in the right account, but this breaks when I restart the browser and the page reloads with the wrong account... Why Google removes this parameter from URLs after loading is beyond me.
Earlier quoted context omitted.
Do not use Temporary Containers. This extension to Multi-Account Containers looks great at first -- its Automatic mode spins up a new container each time you open a new tab, then switches that tab to an existing container, should one be associated with the TLD you visit. The problem is that Temporary Containers does not delete these temporary containers. They accumulate in the MAC containers list. There is no way to…
"Delete no longer needed temporary containers 15 minutes after the last tab in it closes" is a default setting. This is not an issue I've experienced in the 3+ months I've been using this extension. Are you sure you didn't accidentally change it?
Earlier quoted context omitted.
It does. `firefox -no-remote -P `
There's also a firefox-bin. Anyone know what the difference between firefox and firefox-bin is nowadays? I believe that in the far past firefox-bin was the firefox binary, and firefox was a shell script that would do things like notice you already have a firefox-bin instance open and signal it to open a new window rather than launching a new firefox-bin instance. But nowadays, firefox and firefox-bin seem almost the…
I use Firefox multi-account containers[1] extensively, it's honestly the primary reason I use Firefox these days. The big win for me is that I _hate_ having to use the Google account switcher, so I basically set up a container for each Gmail account (work, personal, old email, etc). The nice bonus feature is you can have certain sites default to containers. I had a paid YouTube account for a while, for example, so ha…
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.