Live data from Hacker News

Firefox rolls out Total Cookie Protection by default to all users

blog.mozilla.org

291–300 of 339 posts

Re: Firefox rolls out Total Cookie Protection by default to all users

#291

Earlier quoted context omitted.

I’ve got this enabled - the only one that’s been more than a mild pain in the ass is the UTC timezone change. Always takes a minute to remember why a site is telling me my appointment is at 2:30 in the morning.

Is there a way to reset the timezone but have all the other protections? Timezone provides pretty low information relative to the pain it causes me when I show up to my meeting 5 hours later.

I have tried and tried to override this on a site-by-site basis

I tried setting:

privacy.resistFingerprinting.exemptedDomains to the domain

privacy.resistFingerprinting.testGranularityMask -> 4

I still get utc in slack

Re: Firefox rolls out Total Cookie Protection by default to all users

#292
post #148

Earlier quoted context omitted.

It's really weird that they claim there privacy work started in 2015. Netscape Navigator add cross site cookie blocking at some point, and firefox has always (?) had it. The innovation here seems to be that they further partition by the URL in the address bar. It's frustrating that browsers have been fighting and losing this war for 25 years. (Presumably they still don't block browser fingerprinting, so sites will ju…

It's not possible to block browser fingerprinting since it's a range of techniques and heuristics based on numerous features. There's no "turn off fingerprinting" button you can just press.

It's certainly possible to curtail fingerprinting.

Why is my browser reporting my resolution to the server? Why can't you just serve me HTML and let me render it how I damn well please?

Re: Firefox rolls out Total Cookie Protection by default to all users

#294
post #118

Earlier quoted context omitted.

> Why weren’t separate cookie jars the default in the first place? Tracking today is an interaction between cookies and pages, not really because cookies were designed to be shared between domains. Because of that, ads on web pages are a reason that information gets shared across sites. Any ad or other iFramed content that’s served on a site can get the domain name of where it’s be served from and then access the iFr…

> Total Cookie Protection is going to put cookies that only Facebook can see in a different jar for each separate site you visit, making it so that Facebook can’t read it’s own cookies across different sites. Won't this break some basic features like being logged in to Facebook (or similar services, e.g. Disqus) for the purpose of embedded comment sections on other sites? They don't use cookies only for tracking butt…

Yes. Hope so. What a bad idea that is.

Re: Firefox rolls out Total Cookie Protection by default to all users

#295
Ok, is this just a more complicated (and less private) version of the 3rd party cookie blocking that’s been in safari for more than 15 years?

If it is better - which seems surprising given it still seems to result in 3rd party cookies continuing to exist - how does it compare to safari’s domain partitioning from what seems like 5 years back, or the newer aayyyy iiiii tracker detecting stuff?

Re: Firefox rolls out Total Cookie Protection by default to all users

#296

Earlier quoted context omitted.

Yes, you can follow the meta-bug here to see the current issues we're working on resolving in a better way: https://bugzilla.mozilla.org/show_bug.cgi?id=1537702 Perhaps unsurprisingly, Microsoft logins are the most glaring exceptions right now (Teams, Logins, Office, Live), and we're working with MS to see if we can find an acceptable fix (or work-around while it's fixed). There are also exceptions for github.dev and…

What is the "better way" here? There is a legitimate use case for having login/identity stuff on a different domain - many of the largest companies in the world are doing this. How can this issue be solved without either confusing users through the requestStorageAccess API, or forcing everyone to use a single domain for everything?

No post body was provided.

Re: Firefox rolls out Total Cookie Protection by default to all users

#297
post #292

Earlier quoted context omitted.

It's not possible to block browser fingerprinting since it's a range of techniques and heuristics based on numerous features. There's no "turn off fingerprinting" button you can just press.

It's certainly possible to curtail fingerprinting. Why is my browser reporting my resolution to the server? Why can't you just serve me HTML and let me render it how I damn well please?

Sounds like a really unique, fingerprintable way to browse.

Re: Firefox rolls out Total Cookie Protection by default to all users

#298

I've had third party cookies blocked for ten years. Some sites don't work. I don't use those sites.

What has become very annoying is so many sites are using "third party cookies" for whatever asinine "single sign on" product they've been sold. The number of redirects my browser undergoes when I log into my health insurance portal is mind boggling.

Maybe I am getting this wrong, but I think the reason you're being redirected through so many sites is because they're not using third-party cookies. They have to redirect you through each domain so that they can all set their own first-party cookies.

Re: Firefox rolls out Total Cookie Protection by default to all users

#299
post #292

Earlier quoted context omitted.

It's not possible to block browser fingerprinting since it's a range of techniques and heuristics based on numerous features. There's no "turn off fingerprinting" button you can just press.

It's certainly possible to curtail fingerprinting. Why is my browser reporting my resolution to the server? Why can't you just serve me HTML and let me render it how I damn well please?

> Why is my browser reporting my resolution to the server

The browser doesn’t need to report anything by default. You can get a reasonable estimate with CSS + JavaScript (e.g. using media queries to modify some observable properties on the basis of the screen width and then report what those properties are via a call to fetch)

Re: Firefox rolls out Total Cookie Protection by default to all users

#300

Earlier quoted context omitted.

Given the number of Firefox users that block Google Analytics, I wouldn’t be convinced about a 2% figure.

You can block Google Analytics all you want. Unless you're spoofing your User-Agent, servers still know what browser you're using.

But GA, statcounter et al don’t use server logs. They use JavaScript.
Post reply on HN