Live data from Hacker News

Firefox Multi-Account Containers

addons.mozilla.org

71–80 of 160 posts

Re: Firefox Multi-Account Containers

#71
I love MACs.

A couple of caveats, though:

* If you disable Multi-Account Containers at ANY TIME, all of your configuration will be gone. So, don't ever disable it. Or just be prepared.

* They don't sync with Firefox Sync.

* I use Alfred and in some of my workflows, when I have URLs that are designed to always open in a particular container, FF just won't open the URL. /shrug

* Always opening URLs depends on the URL. This works great for apps which give you account-specific URLs (e.g. Harvest, Jira, other services...) but doesn't work at all for stuff like Gmail or Drive. I wish there was a way to get FF to ask you how you want to open a URL like that.

Re: Firefox Multi-Account Containers

#72

I made a fork of this that gives you some additional control over how links are treated - specifically, you can set it up different rules for what container to open a page in depending on what container it was opened from: https://addons.mozilla.org/en-US/firefox/addon/containers-wi... The rationale is that you rarely want pages that you open from random Facebook posts or Reddit submissions, or pages that you arrive…

Conex (https://addons.mozilla.org/en-US/firefox/addon/conex/) has an option that allows the user to select container for incoming links

Re: Firefox Multi-Account Containers

#73
post #22
post #21

This was long time ago. It does compartmentalize the browsing info but the history is still accessible with other containers. For example, a Shopping container should have its own history. ( https://github.com/mozilla/multi-account-containers/issues/4... )

If I wanted to completely separate things like this I would use multiple different profiles. The advantage of the extension is that your history, settings, etc remains constant across the containers.

Profiles are unfortunately much more cumbersome to use than in Chrome.

The UX that container tabs have - being able to use them in the same Windows as other tabs, with accessible open-in options from the tab bar and from various context menus; creating new containers as easily as specifying a name and no more - is the UX that I wish Firefox had for their profiles.

Re: Firefox Multi-Account Containers

#74

These are pretty good, but the Chrome implementation is better. Specific complaints: - can't tie a bookmark to a container. - too many clicks to open a new tab in a container (in Chrome the whole window stays tied to the container, not just the tab) - bookmarks and history aren't container-scoped.

The use case for containers is totally different from the use case for profiles. The whole point of this feature is that you can have all of the cookies and persistent storage of a tab or set of tabs sandboxed, without affecting your actual browser history or bookmarks.

If you want that, use profiles.

>too many clicks to open a new tab in a container

The configuration for this is really simple. There's even extensions like "temporary container tab" that will give you a fresh container with one click.

Re: Firefox Multi-Account Containers

#75

These are pretty good, but the Chrome implementation is better. Specific complaints: - can't tie a bookmark to a container. - too many clicks to open a new tab in a container (in Chrome the whole window stays tied to the container, not just the tab) - bookmarks and history aren't container-scoped.

Also, it's annoying and a bit scary (for bugs) that this is an extension rather than being built into the browser.

It is built into the browser. The extension is just the UI to access it.

Re: Firefox Multi-Account Containers

#76

These are pretty good, but the Chrome implementation is better. Specific complaints: - can't tie a bookmark to a container. - too many clicks to open a new tab in a container (in Chrome the whole window stays tied to the container, not just the tab) - bookmarks and history aren't container-scoped.

Also, it's annoying and a bit scary (for bugs) that this is an extension rather than being built into the browser.

It's an extension written by Mozilla that is using APIs built into the browser. The extension is just a bit of UI to make the feature accessible.

Re: Firefox Multi-Account Containers

#77

I made a fork of this that gives you some additional control over how links are treated - specifically, you can set it up different rules for what container to open a page in depending on what container it was opened from: https://addons.mozilla.org/en-US/firefox/addon/containers-wi... The rationale is that you rarely want pages that you open from random Facebook posts or Reddit submissions, or pages that you arrive…

I use Temporary Containers (https://addons.mozilla.org/en-US/firefox/addon/temporary-con...) to do this. You can customize how you want links handled when they target different domains. It takes some getting used to as there are a handful of options to understand/customize. Plus you can have customizations where you're replacing the current container with a new one which kills off your back button history. Just need to be aware of the quirks. It's definitely still in the realm of power-user UX.

Re: Firefox Multi-Account Containers

#80
The biggest drawback with Multi-Account containers is that they don't sync with the Firefox Sync. I have an elaborate and carefully crafted set of containers. I even have one for TheGuradian where I am allowing ads but the moment a new machine is added to the workflow all is lost.
Post reply on HN