Firefox

18056 readers

120 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

437

Firefox rolls out Total Cookie Protection by default to all desktop users worldwide | It is Firefox’s strongest privacy protection to date, confining cookies to the site where they were created (blog.mozilla.org)

submitted 4 months ago by ForgottenFlux@lemmy.world to c/firefox@lemmy.ml

24 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] everett@lemmy.ml 22 points 4 months ago* (last edited 4 months ago) (1 children)

That's great, but what's the update? The Lemmy cross-posts from two years ago have the same title.

update: I read the post and the last paragraph talks about the full blocking of third-party cookies as a thing that's "starting in 2024" (future tense). So my best guess is it's that, but whatever the August 28th update was could have cleared all this up.

[–] LWD@lemm.ee 2 points 3 months ago (1 children)

So the update is, Firefox now blocks all third party cookies by default?

That's great and new news... I just wish this post reflected that, so I wouldn't have to dig through comments to figure out what changed between 2022 and today.

I was confused enough when they initially announced Total Cookie Protection in 2021 and then re-announced it as rolled out to all users in 2022.

[–] everett@lemmy.ml 2 points 3 months ago (1 children)

I think that's what it is, except my use of the term "block" was mostly wrong. This seems to accept them but keep them isolated, defeating their effectiveness as a way to track users across sites.

[–] LWD@lemm.ee 2 points 3 months ago

I don't think it's anyone's fault for being confused or misinterpreting what's in the article, because even Mozilla calls it blocking:

And starting in 2024, all our users can look forward to Firefox blocking even more third party cookies.

The linked page is even more confusing, because it provides a link back to this page for clarification about which third party cookies are being blocked.