> So I naturally tried to access the same page in Google Chrome to see if I’d still be blocked. Thankfully, I wasn’t.

> But of course I wasn’t because Chrome doesn’t have the same privacy- and security-enhancing designs

Maybe I’m missing something but it seems the conflation was by the article author, not me?

No. And there’s still the central issue of the author really hand-waving the specifics of their accusations about Chrome. It really seems to come down to “Google bad”.

To be clear, I don’t even use Chrome, in part because “Google bad”. This just isn’t intellectually honest.

seems like the author mentioned that in FireFox disabling "privacy.resistFingerprinting" worked. So looks like Chrome by default is allowing the server to collect Fingerprinting. If cloud flare is using that, then it is a big red flag.

Of course they are. Thats the whole point of the 'Integrity Check'. Besides, almost every website you visit collects your fingerprint nowadays.

The opposite. enabling the flag fixed the issue although it broke other sites.

  > Eventually, I found some suggestions that if you’re using Firefox you can disable the privacy.resistFingerprinting option in the about:config page. But that was already listed as false for me when I got stuck, so I switched the value to true just to see if that would do anything.

  > And that worked!