Open Noah-Huppert opened 6 years ago
I tried to get a promotion code today that required liking a page on Facebook. I ended up having to disable and reenable the extension to do so. :/ I had been looking for a way to opt the promotion app's domain into my Facebook container, or open the tab inside that container.
@ocdtrekkie To get around these kinds of issues I ended up installing the Multi Account Containers and Switch Containers addons.
The Multi Account Containers addon gives you an option in the right click context menu named "Open Link In New Container Tab". Using this menu you can choose to open a link in the Facebook container that the Contain Facebook extension (this repo) creates.
This addon also lets you pin custom domains into specific containers. So if you would like another domain to always open in the Facebook container you can right click and select "Firefox Multi Account Containers > Always Open In This Container".
The Switch Containers addon give you a similar menu to switch a tab you have already loaded into another container. So if you are on a website and then realize it needs your Facebook credentials you can quickly switch the tab over to the Facebook container and continue as usual.
These features can also be used outside of the context of Facebook. For instance I also have a "GitHub", "Work", and "Google" container.
I would also recommend the Temporary Containers addon. This addon creates a new container for every tab you open. So when browsing websites which you have not pinned to a specific container (Using the Multi Account Containers Addon) you can remain relatively tracker-cookie-less.
@Noah-Huppert I will try these out, thanks!
@Noah-Huppert your suggestion sounds good, but I don't think it works the same way, i.e. it doesn't contain facebook: when you access a link from facebook, it will be opened in the same container so FB can track you.
I would also find it useful to configure the domain list.
Although I have Multi Account Containers, I also use Facebook Container because it's proactive:
1 contains when navigating into known Facebook domains 2 leaves container when navigating out to non-Facebook domains, even unknown ones 3 contains new domains as they become known (via add-on update) 4 deletes Facebook cookies from other containers on install and when you restart the browser
(Ideally, Multi-AC would be extended to be as proactive as Facebook Container is for any domain(s).)
Several tickets have been opened asking to to add domains which are part of the Facebook platform.
Instead of creating a new release for each domain, what if a user option was added to customize domains which should share a container.
Additionally some sort of global list (Similar to ad blocker domain lists) could be used to release these new domains.
This would also enhance the experience when using
privacy.firstparty.isolate=true
. As users could choose to share cookies between some sites.