Hacker News Reader

Hacker News

Comment by thomastjeffery | Hacker News Reader

Parent Full thread

thomastjeffery

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 deleted before (in the instance you are syncing from) still exist in this fresh instance.

- New user welcome UX is still active.

View on HN

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.

This happened to me many, many times. Luckily I'm able to track down containers.json and remove them that way.

It also would never sync to my laptop for some reason?

The overall bad syncing experience was the main reason I stopped using them.

ya know.....it never occured to me to really track down the json file. Even though i totally know firefox really loves making use of them. Even had a sanitize script at one point that would kill any session on my work computer nightly and scrub my history without logging me out of sync account at a previous job.

I dont setup a new machine all that often that I care too much. I figured it was a misconfigured cloud DB point, that at best I could get Mozilla to clean up and let me re-sync, but even then didnt bother to open a ticket.

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.

Also, the order of the containers isn't synced properly. When you have a few containers, it's helpful to have container configured in the same order on every device you use.

Reply on news.ycombinator.com