In the meantime, I am very happy with the unofficial "Google Container" addon [1], which is just a copy of the Facebook container that works its magic on Google domains instead.
Give it a try. It doesn't interfere with the official Facebook container addon.
[1] https://addons.mozilla.org/en-US/firefox/addon/contain-amazo...
[2] https://addons.mozilla.org/en-US/firefox/addon/microsoft-con...
That is not what I asserted.
I asserted I don't care about it. I don't believe Netflix tracks me outside of .netflix.com and I don't believe Apple tracks me outside of .apple.com (and the other domains ofc). If they do, you have to convince me it is harming my interests (ie. my privacy or freedom of choice).
I know Google tracks me, I know Facebook tracks me. Their profit model is surrounded by this tracking. I know Amazon and Microsoft track me. Their profit model partly relies on tracking.
There's Invidation addon to avoid Twitter/YouTube and redirect to Nitter/Invidious, and there's some addons to avoid CDNs such as Cloudflare / Amazon/ Akamai. There's also an addon to remove garbage in URLs such as AMP (I mean, wtf?).
If you want to avoid these completely, plus GAFAM, your internet (browsing) experience isn't annoying; it is broken.
I avoid Uber/Airbnb/Pinterest already (niches I don't care about) and Yandex/Baidu is not meant for my demographics.
Invidition is just a wrapper. Doesn't solve the larger problem which is what's happening on the server. Last time I tried it YouTube was completely broken because Google changed a tiny little thing.
Twitch is Amazon.
I'm aware of wrapper usage. I just use youtube-dl from CLI whenever I see a YouTube linked referenced which should interest me.
What I want is for every web page to run in its own container by default. Zero configuration.
If it wants to access anything outside of its allowed domain hiearchy (like call an external API), I'd like the browser to ask for permission on its behalf. "Github.com would like to share data with Microsoft.com. Allow/Deny?"
There could be some kind of trust standard so that Github.com can prove that they are the same legal entity as Microsoft.com and is therefore authorized to share information without asking. Or perhaps something simpler that is DNS-based, like with email.
When I want to stay logged into anything I self-manage and create a named container. (This requires micromanaging but is at least opt-in.)
But the default of separate temp containers is great.
But just consider the automatic way a regular user clicks at any prompt that gets in their way out of habit...
I am guilty of this sometimes, even though I try to be mindful and always try to opt-out of tracking cookies, etc.
I think the system you're proposing has to have some sort of smart way to whitelist, either by granting temporary whitelisting with varying granularity (e.g. for this session, for 1 hour, forever ... Etc).
I think Privacy Badger (the add-on) has partially solved this (learning through counting how many times a tracker's domain appears on other sites), maybe this could applied in reverse: automatically whitelist after N approvals.
What do you think?
Sadly most sites use a lot of third party javascript, css etc so it will be a clunkier experience than you are hoping for.
edit: sounds like another addon idea: find the minimal set of 3rd parties needed to render a website.
uMatrix tries to do this already with some third party scripts, but it’s a moving target.
Google intercepts clicks and redirects them through a Google Domain to track clickthru. If you're in Gmail and hover over a link it will show the actual destination but onclick your browser opens a mail.google.com URL that redirects to the destination URL.
https://addons.mozilla.org/en-US/firefox/addon/skip-redirect...
This one handles the other situation, tracking parameters added to the URL that are intentionally passed to the target site:
That redirect always bugged me.
EDIT: I just noticed on the install page "This is not a Recommended Extension. Make sure you trust it before installing.Learn more" which is annoying.
I don't know how you'd enforce it at the browser level because obviously there are tons of legit uses for modifying a link on click... but it should be enforced somehow.
Now I have to find a provider that doesn't leak in the dumbest of ways.
In the former scenario you'd basically get 2 new tabs, in the later you'd have a tab represent two different containers based on where you navigate in history.
Either way it sounds unsavory.
I use this in combination with "normal" containers and it works a treat
There is some annoying UI lag when opening a new tab though, as it takes a fraction of a second to swap from default to a new temporary container.
https://github.com/mozfreddyb/webext-firstpartyisolation
It sometimes (rarely) breaks payment processors but otherwise works fine
I wouldn't recommend it for family or friends, but I'm happy with the trade off
I had the same problem so I made a small extension that does that:
https://addons.mozilla.org/de/firefox/addon/container-outgoi...
The Conex extension https://github.com/kesselborn/conex goes beyond by (optionally) prompting you for which container you want. The best part of this extension is that it lets you hide tabs that aren't in the same container, effectively giving you tab groups based on container. Once you get used to it, you won't want to go back to having 80 tabs displayed at once.
In addition
My problem with that is that, even if I do this, it doesn't remember it for foo.abc.com, and when I'm in the container, links to def.com won't open outside the container.
All urls that are not "pinned" to a container open in a temporary container.
You can right-click links and open them in a "New Container Tab" (including "No Container").
Edit: You can also right-click on the tabs and select "Reopen in Container"
!*.google.com , Google
!* , No ContainerSo whether it's more correct to be referring to the built-in functionality (including some of the UI elements), or the add-on, depends on exactly what you're talking about. And it's hard to distinguish.
The site linked to is not assigned to any container. It opens in the old container, while it should open in the default container.
The idea of having a link clicked inside a container and expect it to go to a different container as a default setting, seems to contradict web standars. Now, if you've explicitly assigned the clicked domain to a different container, then yes, it should go to its container (which is how it works, to me at least).
But I'm not aware of any "web standard" codifying container behaviour.
What does that have to do with containers, or better, why do you believe what many users want is forbidden by "web standards"?
But if I click a Google link, it already goes to a different container (the Google one), because I've told it to.
> Now, if you've explicitly assigned the clicked domain to a different container, then yes, it should go to its container
I am trying to assign "all non-google.com links" to open in the default container.
"I disapprove of what you say, but I will defend to the death your right to say it". All companies should have the same access to the technology in user's browser. Favoring Google by Chrome seems no different than blocking Facebook by Firefox. It's the same behavior, just a difference in opinions.
edit: to clarify, I am in agreement with the parent comment, the above is just about Facebook container being a feature
Singling out facebook and google would absolutely be correct actions, and making it more obvious to users how to do that is a net good.
The two biggest issues are that I can't give the container a list of domains beforehand and say "everything under google.com should open here". I have to go to each Google subdomain and set it to "always open in this container" with three or four clicks. The other major issue is that there's no way to have links outside those domains open outside the container, so whenever I click a link on Gmail that goes to Github, Github opens in the Google container and I always have to copy/paste the address to a new tab.
Fixing those two annoyances would make the built-in containers feature amazing. Maybe I should file a feature request.
EDIT: I have filed a feature request: https://bugzilla.mozilla.org/show_bug.cgi?id=1621276