Live data from Hacker News

Firefox rolls out Total Cookie Protection by default to all users

blog.mozilla.org

281–290 of 339 posts

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

#281
post #178
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…

The solution still seems to be to: 1. Use Firefox, block .js by default, and selectively allow. 2. Set browser to block cross-site cookies, and to purge all cookies when closing browser. 3. Avoid tabbed browsing, and restart browser after using a website. I've been doing this since about 2006. It's inconvenient, but gives some peace of mind.

How about just using the "Delete Cookies" -feature of the browser? And maybe there's a plugin that would make that one-click process?

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

#282
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…

Internet explorer used to ask the user before saving cookies. And the server had to declare what cookies would be used for in machine readable form (P3P) which the browser used to decide if it want to allow the cookie (google blatantly lied) And more recently DNT. A graveyard of failed attempts at improving privacy

FIrefox used to ask, then it would ask if you set the right preference, and then it stopped asking entirely. I was very disappointed in them.

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

#283

Earlier quoted context omitted.

It is possible to enable obstacles to fingerprinting. In Firefox, it is configuration entry privacy.resistFingerprinting Some details (the list is not exhaustive): > * Your timezone is reported to be UTC; * Not all fonts installed on your computer are available to webpages; * The browser window prefers to be set to a specific size; * Your browser reports a specific, common version number and operating system; * Your…

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.

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

#284
post #210
post #193

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?

Right, the consent window should have been a browser thing so that it is always the same and so that it follows the laws and cant involve dark patterns. By reading this message you agree with it.

The answer is similar to the DNT (do not track) debacle.

When you give users a clear, informed, singular choice that would be sticky across their entire web/app experience, the choice in itself essentially becomes obsolete. Since pretty much nobody opts-in.

You saw the effect with Apple's new "do you want to be tracked" permission, which has a disastrous impact on Facebook. Consider that this is still a per-app permission, imagine the impact when its a single permission across all apps.

As users we may say "good" and "this is what we want", but I don't think we can truly oversee what impact that would have.

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

#285

Earlier quoted context omitted.

If the contents of the cookie is a JSON array of recently viewed items, then the size is correlated to whether I've been actively viewing items recently. Adding random padding makes it harder to get a signal, but with a high enough sample size, it's still possible to get some information. If you always pad to a fixed size, then there's probably no useful information. At the moment, I think I have enough to do, but I'…

>If That's are really big word in that sentence. You have NO idea, like 0, what is stored in an encrypted cookie. To even think you do is just pure folly.

I do have ideas. I can strengthen them by reverse-engineering the behavior using my own account. I participate in follies regularly, so that's not a strong disincentive for me.

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

#286

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.

The question isn't whether the server logs are there. It's whether anyone looks at them instead of GA for browser information.

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

#287
post #145

I wonder if there's anyone from any advertising/ad-targeting companies on HN who can shed some light on if/how much this change may affect their "product". Asking this since I know friends working at companies that were DRASTICALLY affected by the Apple advertising changes in terms of user targetability (and hence revenue) and I'm wondering if this change will be similar.

I work in advertising. this change is nothing compared to what Apple did. Edit : It's better than ETP.

Better? For who? The trackers? Or the trackees?

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

#288

Is this better or worse than Safari's "Prevent cross-site tracking" feature? https://support.apple.com/guide/safari/prevent-cross-site-tr... It appears Safari is just blocking the cookies, while Firefox is isolating the cookies. I guess Safari has to keep track of who to block while Firefox just isolates everybody. Are there other benefits to the Firefox approach? Frankly, I have a hard time understanding why this Co…

There has been first party isolation from Tor Browser in Firefox for a while.

https://addons.mozilla.org/en-US/firefox/addon/first-party-i...

That addon has links with info and just twiddles an about:config setting. It can break things (for example some ways Paypal is used by websites, although other ways work fine). There has also been the ability to block third party cookies for a very long time, possibly as long as there have been cookies, but it can also break things. As I understand it Total Cookie Protection is similar to these but with some exceptions so that not much breaks that users would notice.

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

#289
post #190

Earlier quoted context omitted.

That’d certainly prevent most tracking, yeah. This new Firefox feature should make #2 and #3 unnecessary. I think this feature by Firefox is great, and privacy options are getting objectively better, if slowly. But the cynic in me guessing that server side tracking methods are going to start getting secretly better, if they haven’t already.

I'm not sure about #3. there's still sessions, localstorage, indexDB, etc

I didn't mention #4 of also purging all that other stuff when the browser closes.

Honestly, try it with me - it's not so bad. 1, 2, 3, everybody now!

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

#290

Earlier quoted context omitted.

> 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…

Why can't the browser can handle the login?

They tried https://en.m.wikipedia.org/wiki/Mozilla_Persona
Post reply on HN