Firefox container mode stops this. I can imagine a product that makes every tab an ephemeral container by default, and you had to explicitly opt-in to a container profile to share cookies, etc. cross-tab.
If you click Agree you agree to be tracked regardless of the method. So yes, cookies won't do much, but now you've agreed to any kind of tracking, even those that defeat private mode and/or script blockers (assuming there's one).
touch .local/share/applications/open-in-dispvm.desktop,
and put inside a command like this:
qvm-open-in-vm '@dispvm:fedora-37-dvm' %u
in accordance with this guide:
https://www.qubes-os.org/doc/how-to-use-disposables/#opening...
To make this browser default, you do this:
xdg-settings set default-web-browser open-in-dispvm.desktop
See also how to create .desktop files: https://askubuntu.com/questions/45885/how-do-i-set-a-custom-....
On Mac, you can for example create a simple App in AppleScript with the following code:
on open location the_url
do shell script "/path/script.sh" & quoted form of the_url
end open location
In script.sh, which receives the clicked url as the its first positional argument, you can then run any arbitrary logic that you require.
So this idea would work if the links you wanted to open were coming from another app. If they come from inside the browser, I would suggest writing an additional browser extension that replaces all http/https links in a page with an invented URI schema, like newschema://. Then the browser would pass those links to the OS for handling and then you would have full control over how to handle this new schema.
Hope this makes sense.
How?
- about:addons
- Temporary Containers > 3 dots > Preferences
- Isolation > Global settings tab
- Mouse Click settings
- Change behavior for Middle Mouse, Ctrl/Cmd-Mouse, or normal Left Mouse clicks
- Always = always open in new temp container
- Never = never start new temp container on click
- Different From Tab Domain/Subdomain = start a new temp container only when navigating to a different domain/subdomainWhen an update is applied between the first and second profile process, any new tab won't do anything in any of the instances. Firefox likely still doesn't detect this state.
Edit: That is, if you use Firefox with two or more profiles, and may start one profile later (after a new update was published).
It's an underrated feature, IMO. Profiles can be made very purpose-specific, and I like that there's not the possibility of leakage due to a site exploiting an add-on sharing data across containers, etc. I still like the mukti-containers feature, but I see it as less of an anonymity thing and more as a convenient way to be able to sign into multiple website accounts at once.