Live data from Hacker News

Multi-Account Containers

support.mozilla.org

181–190 of 254 posts

Re: Multi-Account Containers

#181
post #129

Why don't we have complete main domain isolation as an option? It would work like containers, but they would be automatically created for each domain you visit. Go visit youtube.com and anything loaded from that page is in the same container. You'd have to log into each google property as the sites would be separated from one another, and there would probably be a need to merge these containers if say www.example.com…

Sounds like you are suggesting First-Party Isolation (FPI) which you can enable in Firefox. Don't know what the state of it is, seems to be off by default, or depending on the tracking protection setting.

Re: Multi-Account Containers

#182

I've been using this since it was new. I'm very frustrated to say the UI/UX hasn't seen any significant update. Containers are still synced separately, so any fresh install of Firefox will have the tutorial UX and the default 4 containers, even after syncing. Also, address bar completion is still monolithic, making it very easy to accidentally open a site in an undesired container. That can be worked around by adding…

Mozilla is on Googles drip. You can't expect this feature seeing much love it's against the donors intents.

And that drip is just as important for google to avoid an insanely huge monopoly lawsuit, so this is just the usual shitting on certain open-source projects without any reason.

Re: Multi-Account Containers

#183

Earlier quoted context omitted.

Yes, and the flow is as I described. 1. Install Firefox. 2. Log in to fresh Firefox instance. 3. Let browser-wide sync happen. 4. Sync installs multi-account containers addon. 5. Four empty default containers are created. New user welcome flow is active. 6. Sign in to multi-account containers addon. Wait for container sync to do its thing. 7. Containers sync invisibly in the background. - Default containers that you…

Also....for me. At one point a janked up Firefox instlal on 8.1 created something like 100+ duplicates of some of my containers, specifically ones names TEst and Test2. So each time i setup a new browser and sync then, i have to go through and manually delete all the duplicates. They dont re-appear once deleted and changes still sync (ie: if i add a URL rule to always open in x container) but holy crap is it annoying…

There is a json file with the containers, I also had a similar problem (temporary containers extension “leaked” containers and they got synced) but after having found that file (I believe it was containers.json or something similar) and manually removing from that all the bad elements I managed to get those out from syncing it to new instances.

Re: Multi-Account Containers

#184

I've been using this since it was new. I'm very frustrated to say the UI/UX hasn't seen any significant update. Containers are still synced separately, so any fresh install of Firefox will have the tutorial UX and the default 4 containers, even after syncing. Also, address bar completion is still monolithic, making it very easy to accidentally open a site in an undesired container. That can be worked around by adding…

Fortunately there are some cool extensions that do improve that logic. My favourite uses a new container for every AWS SSO login, so I can have multiple AWS accounts and/or roles on the go at the same time.

https://addons.mozilla.org/en-US/firefox/addon/aws-sso-conta...

But completely agree, this should be a capability. It's like how Google Chrome profiles don't have the "open in another profile" menu option until you have two profiles already opened.

Re: Multi-Account Containers

#185
Containers are fantastic! Must have when developing/testing webapps with different user accounts, using a few containers.

Miles better than juggling with other browsers or incognito mode.

Re: Multi-Account Containers

#188
post #182

Earlier quoted context omitted.

Mozilla is on Googles drip. You can't expect this feature seeing much love it's against the donors intents.

And that drip is just as important for google to avoid an insanely huge monopoly lawsuit, so this is just the usual shitting on certain open-source projects without any reason.

How true is that these days? I see it mentioned a lot. Google doesn’t have to keep them afloat just to avoid some hypothetical anti monopoly issues.
Post reply on HN