The author was blocked from accessing a work website due to issues with Cloudflare’s browser integrity checks. Despite having credentials to prove his identity, an attempt to bypass the checks by disabling fingerprinting in Firefox resulted in Cloudflare blocking all access. He could still access the site on Chrome, showing the block was based on his browser configuration. This left the author unable to complete important work tasks and questioning how much control individuals really have over authentication in an increasingly centralized web ecosystem dependent on remote attestation. It highlights the need for transparency and user agency in how identity verification is implemented online.
I don’t think that’s what happened to the author. Cloudflare generally doesn’t leave you on that page if it detects a suspicious browser. Plus, how is cloudflare supposed to use your corporate VPN and your certificate to verify your identity? They don’t have an omnipotent view of all corporate VPNs that exist. The check that cloudflare does on that page is pretty javascript heavy and I assume it was just temporarily broken in Firefox. Which is an issue in itsself, but it’s not the massive deal that the author makes out.