201–210 of 339 posts
Does this obviate the need for [Facebook Container]( https://addons.mozilla.org/en-US/firefox/addon/facebook-cont... )?
Total Cookie Protection is about isolating third party cookies/web storage, without breaking as much of the web as simply blocking third party cookies does.
It would be nice to allow users to create "trusted tuples" to list small groups of domains that are allowed to share their cookies. For instance: Zendesk, Asana, Jira, etc. But have each tuple listed still be isolated from the other, only domains listed together in a single list could share a cookie container.
> small groups of domains that are allowed to share their cookies Could you explain how this could be beneficial to the user?
Earlier quoted context omitted.
Firefox has a sub 8% market share, so I doubt this will make a drastic change to how they operate.
Surprised it's even that high, I tried to switch to Firefox the other month for privacy but gave up because it crashed on me it-least once a day. Edit: thanks for the downvotes, I would have preferred if it worked but it didn't. I tried basic troubleshooting, disabling extensions etc. but didn't find it usable on macOs Monterey, think it doesn't play well with youtube.
Earlier quoted context omitted.
Probably that is the use-case for the official multi-account containers plugin.
I tend to agree, but as someone who uses this plugin a LOT, I have some complaints. If I decide I want, say, an Azure Portal container then I cannot have login.microsoftonline.com assigned to a different container -and- configured to automatically open in that container. If I do that, I need to have a combined Azure + Office 365 + anything-I-need-to-authenticate-to-Azure-AD-for container. It’s a good solution but wit…
Maybe another way to think of it is like a one-to-many join. A domain would not "belong" to a single container, but have tags to associate with 1+ containers.
Earlier quoted context omitted.
> small groups of domains that are allowed to share their cookies Could you explain how this could be beneficial to the user?
for non-dark pattern use cases where it is beneficial from a usability standpoint to share cookies across domains
Privacy wins aside, can anyone please help educate if third party single sign ons will still continue to work?
One is that the login service can request access from the user using a new web API (requestStorageAccess). Another is heuristics which apply when the user interacts with the page in a way which implies a login might be taking place.
In these cases, specific third parties can be granted access to allow the login. There are some more details here: https://developer.mozilla.org/en-US/docs/Web/Privacy/Storage...
Earlier quoted context omitted.
> small groups of domains that are allowed to share their cookies Could you explain how this could be beneficial to the user?
for non-dark pattern use cases where it is beneficial from a usability standpoint to share cookies across domains
Cool. Just a heads' up that I had to disable it on Zendesk and Asana so they could talk to each other - you might experience similar issues.
When will the browsers take care of handling the cookie options for all the sites, so I can declare my preferences once and everyone stops putting up a popup? Surely this is already in the works?
By reading this message you agree with it.