Firefox 85 cracks down on supercookies

Post by sanxiyn » Tue, Jan 26, 2021, 4:49 PM UTC

amenod wrote: post #107

Good job Mozilla! Do what Google never will - put users' privacy front and center. On a sidenote, I might now re-enable cache that I kept disabled (well - cleared on exit) because of supercookies. I don't care that much if a single page tracks me, but I _really_ don't want Google to track me across sites. If Firefox protected me against that.. they would have one very grateful user. :) EDIT: this also highlights why…

Post by BasicObject » Tue, Jan 26, 2021, 4:50 PM UTC

rational_indian wrote: post #15

ceejayoz wrote: post #7

Earlier quoted context omitted.

I haven't noticed it to be slower , but I'd accept slower for the privacy benefits.

I have noticed it to be slower, and with more broken websites. I still prefer it over chrome.

Post by chromaton » Tue, Jan 26, 2021, 4:50 PM UTC

Closi wrote: post #72

chromaton wrote: post #16

Is this really important given that browser fingerprinting can almost always identify a web browser?

Absolutely it’s important - Just because one hole is still open doesn’t mean another shouldn’t be closed. And FF and Safari should continue their work to close any fingerprinting opportunities Fingerprinting is becoming less effective over time - for example fingerprinting on iOS is pretty unsuccessful.

Post by kevin_thibedeau » Tue, Jan 26, 2021, 4:51 PM UTC

derefr wrote: post #42

iscrewyou wrote: post #5

Earlier quoted context omitted.

Google websites work better on chrome. Not sure if it’s because google is doing something nefarious or if Firefox is just not keeping up with google website technologies. So, I’ve trained my brain to use chrome as an app only for google websites. When I need to check gmail or YouTube or google calendar, I use chrome. Otherwise I’m on Firefox or safari. It’s worked pretty well. I found I was only really unhappy with F…

It’s the latter, but I would describe it less as Firefox not “keeping up”, and more as Google deploying pre-standard protocols (like SPDY) into Chrome first , before ever documenting the protocol; let alone trying to get it turned into a standard (like HTTP/2.) Chrome had SPDY support not just before any other web browser did, but before any open web server did—because Chrome had SPDY support before Google ever docum…

Post by biryani_chicken » Tue, Jan 26, 2021, 4:52 PM UTC

pradn wrote: post #101

warent wrote: post #83

Earlier quoted context omitted.

I run a network ad-block dns (pihole) and consistently 25-33% of all my network traffic is blocked as ads. It's much more than I ever imagined. Now I'm used to a different internet, when I'm using internet off the network it's like WTF is this?

Question about pihole: is it possible to turn off blocking for a website? Do you have to log into the pihole web interface to do that? I often go to websites where some crucial functionality is blocked by my adblocker (ublock origin), where I have to turn it off for that site.