Updated Aug. 28, 2024. Take back your privacy Firefox is rolling out Total Cookie Protection by default to more Firefox users worldwide, making Firefox the
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.
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.
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.
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.
Updated Aug. 28, 2024
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.
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.
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.
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:
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.
That’s today!