Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I recently made the transition back to Firefox too, like a lot of other folks in here it seems. Containers makes working with all my AWS much easier, and the containers isolating Facebook are great.

One problem though, that I can't solve, is that every once in a while I want to log in with Facebook, like for AirBnB. But I can't, because the cookie only lives in the Facebook container, but I can't add AirBnB as a hostname to the Facebook container.

Has anyone solved this?

Edit: I just solved this. You have to disable the built in Facebook Container extension and then it works as expected.



If you use the Multi-Account Containers extension, you can set AirBnB to always open in the "Facebook" container so it'd have access to your Facebook cookies.


I do use that extension, but it specifically blocks you from adding new domains to the Facebook container, which is built into Firefox. I can't figure out how to turn off that built in one and use the multi-account one instead.


> I can't figure out how to turn off that built in one

I don't see the facebook container to be built-in. I have only the multi-account container extension installed, and I can make any website to open by default in the container I have created for facebook.

I think, you will have to uninstall/disable the facebook-container extension, and just have the multi-account container extension enabled.

FB container - https://addons.mozilla.org/en-US/firefox/addon/facebook-cont...

Multi-account container - https://addons.mozilla.org/en-US/firefox/addon/multi-account...


Would you happen to know how safe and separate the containers are?

Like, if I had a specific container used for Banking sites, would it be relatively safe from other containers?

Currently, I use Firefox for casual browsing and Chrome for email and financial related sites. But it would be nice to just use Firefox for both. I'm just worried it would be less safe.


Is there a way to configure Firefox so that a single-use container gets created when certain sites get visited, and discarded when they're closed?

I don't want to delete cookies by default (since I don't like to lose my shopping cart due to accidentally closing a tab in a shop I haven't used before), but I certainly would like to be able to ban sites that use cookies in a user-hostile manner from storing cookies permanently.

It would be even better if Mozilla used the voluntary telemetry + manual user feedback to decide which sites benefit from cookies (e.g. web shops), and applied this to everything else (e.g. news sites).


> I don't want to delete cookies by default

IIUC you want a container to be isolated to a single website, you have to create a container for that website, open the site in that container, and then click the multi-account container tab in the toolbar, and select to option to open this website in that container by default. From then on whenever you open the website, it gets opened in that container by default.


From what I understand, every container has their own cookies and local storage, so it's like using a separate browser for every website.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: