multi-account-containers

There are a bunch of challenges with regard to what you allow a container to access. Here's one issue: https://github.com/mozilla/multi-account-containers/issues/4....

MAC Containers developer here. This treatment is done by default in the Facebook Container add-on. It's more of a question of how to handle the setting on a per domain/Container in the UI. Follow along for the root domain issue here: https://github.com/mozilla/multi-account-containers/issues/1...

Make sure to disable container sync when using this combination. It's easy to accumulate hundreds of temporary containers which somehow hoses your Firefox profile on Mozilla's sync server (and can also produce gigabytes of logs in your local profile directory). It seems it's currently impossible to recover your profile once you reach "Maximum bytes per object exceeded" - the remote end won't even let you delete the offending data. [1] https://github.com/stoically/temporary-containers/issues/371 [2] https://github.com/mozilla/multi-account-containers/issues/1...

I didn't see multi-account containers mentioned: https://github.com/mozilla/multi-account-containers#readme That one changed my life. It allows me to log into different AWS accounts at the same time. Also different Gmail accounts at once (like my kids' email and mine). Also it gives you a massive boost in privacy since cookies don't follow you around since they are restricted to one container. Combined with Container Tabs Sidebar: https://github.com/maciekmm/container-tabs-sidebar You get the tree style tabs with automatic organization by container.

Note: we have an update coming that includes a "Limit to Designated Sites" feature in the base Multi-Account Containers extension: https://github.com/mozilla/multi-account-containers/pull/165...

https://github.com/mozilla/multi-account-containers/pull/161... was just merged earlier today that introduces the sync function.

M-A-C dev here ... We're actually pretty deep into the work of adding sync to M-A-C. https://github.com/mozilla/multi-account-containers/pull/161... Predictably, synchronizing data is complicated, so it's taking a while and we're trying to do it in a way that doesn't destroy any existing data. So we'll be doing some heavy internal testing on it before we release it. But it's definitely coming.

I love this and use it daily but am sad that they don’t sync between machines (and the discussion over at https://github.com/mozilla/multi-account-containers/issues/3... is a bit disenhartening)

I love this feature... on one machine at a time. Without a built-in sync feature, I continue to use the simplest form of cookie management: Private Windows. I know there's been some discussion on sync: https://github.com/mozilla/multi-account-containers/issues/3.... As of Dec 2019, it looks like some traction will be coming to syncing just Containers and Site Assignments (which I believe would perfectly suffice most basic needs). If anyone really wanted to keep an eye on sync, I'm guessing these features will be committed to their syncserver, when available: https://github.com/mozilla-services/syncserver.

This a really useful extension for working with multiple cloud service accounts (e.g. AWS assumes a global session, GCP theoretically supports multiple logins but it's in the usual Google NOQA zone where many things break) but there's a really important limitation to know about: the container configuration isn't synchronized with your account. This means that if anything reset your Firefox profile (like that bug they had last year) or if you use multiple computers, you'll be spending a lot of time duplicating the configuration: See https://github.com/mozilla/multi-account-containers/issues/3...

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...)

(3 months ago) https://github.com/mozilla/multi-account-containers/issues/3... > With #1537, our next release starts to address container-bookmark integration & UX. As @MichaelTunnell points out, it does not solve ALL of the container-bookmark UX requests in this issue, or in #854 #1142 and #1443. > Container-bookmark UX is a big project, and some of the solutions will require changes in Firefox itself. Any changes here could introduce tricky bugs both in technical integration and in UX flows.