Basically creates a fake VM like environment for each site.
ArchRecord@lemm.ee 3 weeks ago
For those who don’t care to read the full article:
This basically just confines any cookies generated on a page, to just that page.
So, instead of a cookie from, say, Facebook, being stored on site A, then requested for tracking purposes on site B, each individual site would be sent its own separate Facebook cookie, that only gets used on that site, preventing it from tracking you anywhere outside of the specific site you got it from in the first place.
unexposedhazard@discuss.tchncs.de 3 weeks ago
extremeboredom@lemmy.world 3 weeks ago
For those who don’t care to read the full article
Or even the whole title, really
LiamMayfair@lemmy.sdf.org 3 weeks ago
Isn’t this basically Firefox’s version of the third party cookie block that Chrome rolled out a few months ago? Or am I missing something here?
I mean, it’s good news either way but I just want to know if this is somehow different or better.
jollyrogue@lemmy.ml 3 weeks ago
Sites are much more contained now. Is much more like a profile per site.
CileTheSane@lemmy.ca 3 weeks ago
I don’t know why this wasn’t the case long ago.
Quill7513@slrpnk.net 3 weeks ago
It increases implementation complexity of the browser and loses people who fund Firefox and contribute code $$$
FiniteBanjo@lemmy.today 3 weeks ago
Disabling cross site cookie is already a thing for decades…
sugar_in_your_tea@sh.itjust.works 3 weeks ago
Do Not Track has never really done anything, it just asks websites politely to not track you. There’s no legal or technical limitation here.
FiniteBanjo@lemmy.today 3 weeks ago
I still much rather have it than not. It also lead to the spiritual successor GPC which does actually have regulatory requirements under the CCPA.
sugar_in_your_tea@sh.itjust.works 3 weeks ago
Fair. However, it also provides websites with additional information to fingerprint you, so that’s a thing too.
ArchRecord@lemm.ee 3 weeks ago
Disabling cross site cookies and allowing them to exist while siloed within the specific sites that need them are two different things.
Previous methods of disabling cross site cookies would often break functionality, or prevent a site from using their own analytics software that they contracted out from a third party.
FiniteBanjo@lemmy.today 3 weeks ago
Thank you for your explanation, tbat greatly clears up my confusion.
TBH, if a person’s concern is being tracked by, for example, Facebook; then this just lets Facebook continue tracking them without directly allowing Facebook’s anaylitics customers to track them to another site directly (but indirectly that information can still be provided). But I guess for all the people giving FB and Google those proviledges better to have this than not.
peopleproblems@lemmy.world 3 weeks ago
Hahahahaha so it doesn’t break anything that still relies on cookies, but neuters the ability to share them.
That’s awesome
ripcord@lemmy.world 3 weeks ago
Honestly, I thought that’s how it already worked.
ArchRecord@lemm.ee 3 weeks ago
Total Cookie Protection was already a feature, (introduced on Feb 23st 2021) but it was only for people using Firefox’s Enhanced Tracking Protection (ETP) on strict mode.
They had a less powerful third-party cookie blocking feature for users that didn’t have ETP on strict mode, that blocked third party cookies on specific block lists. (i.e. known tracking companies)
This just expanded that original functionality, by making it happen on any domain, and have it be the default for all users, rather than an opt-in feature of Enhanced Tracking Protection.
ripcord@lemmy.world 3 weeks ago
That’s not what I was thinking of, which was even more fundamental. But that’s good info (and another way to cover stuff in the article).
Telorand@reddthat.com 3 weeks ago
They’ve been doing this with container tabs, so this must be the successor to that idea (I’m going to assume they’ll still have container tabs).
jollyrogue@lemmy.ml 3 weeks ago
Container tabs are still a thing in FF. This is based on that work, if I remember correctly.
snaggen@programming.dev 3 weeks ago
Container tabs are still useful, as they let you use multiple Cookie jars for the same site. So, it is very easy to have multiple accounts on s site.
FiniteBanjo@lemmy.today 3 weeks ago
Unless that cookie was somehow important for you to use both sites.
Buddahriffic@lemmy.world 3 weeks ago
From my experience, blocking 3rd party cookies in general doesn’t seem to make any difference for site functionality anyways. Though I never log into sites with a Google or FB account other than Google or FB sites (and rarely at all for the latter).
werefreeatlast@lemmy.world 3 weeks ago
I would love to see an icon of a neutered cookie please 🥺😄.