Re:A comprehensive study of how fingerprintable users are
by octoberfranklin on Tuesday November 10, 2026 @05:32PM
(#50447245)
And cloudflare, akamai, and hcaptcha lock you out of 80% of the Web.
Re:A comprehensive study of how fingerprintable users are
by dt3ft on Tuesday November 10, 2026 @05:33PM
(#50447256)
Nope. YouTube, for example, works like a charm. Settings allow users to select a user agent or set a custom one.
Re:A comprehensive study of how fingerprintable users are
by aleksejs on Tuesday November 10, 2026 @05:41PM
(#50447332)
Given TFA, I have to assume you are bragging about being the most fingerprintable user on the Web.
Re:A comprehensive study of how fingerprintable users are
by dt3ft on Tuesday November 10, 2026 @05:55PM
(#50447468)
Correct, sticking out is not the best approach. The only protection users of any modern browser have (while still having usable APIs) is whitelisting which sites can request information like enumerating system fonts and serving every other site fake/random information, likely through addons. Say a fingerprinting mechanism wants to enumerate your system fonts, you look up your whitelist, and if it is not on it, browser serves it the most generic list (can be gathered from fingerprinting datasets like EFFs) or finetuning it until your score is as generic as possible. Essentially, blending in with the crowd. Having such whitelists would make browsing a bad visual experience, but hey, why not do what we can to make fingerprinting as difficult as it can be. I don't mind having this as a native feature which prompts the user as they browse, sample prompt: "this site would like to access the following information about your browser, will you allow it or serve it generic, the least fingerprintable set?".
Re:A comprehensive study of how fingerprintable users are
by eszed on Tuesday November 10, 2026 @06:40PM
(#50447890)
Are there add-ons which do this?
Re:A comprehensive study of how fingerprintable users are
by fn-mote on Tuesday November 10, 2026 @08:54PM
(#50448912)
> I don't mind having this as a native feature which prompts the user as they browse, sample prompt: "this site would like to access the following information about your browser, will you allow it or serve it generic, the least fingerprintable set?".
Once this feature becomes common, sites will fingerprint using the delay from the user to click the permission in the dialog.
Really. This whole field is the devil’s work.
Re:A comprehensive study of how fingerprintable users are
by cryptonector on Tuesday November 10, 2026 @11:35PM
(#50449792)
Basically we need something like NoScript that also covers 20-questions API identification.
Re:A comprehensive study of how fingerprintable users are
by herpdyderp on Tuesday November 10, 2026 @06:24PM
(#50447750)
I'm getting this too on main release Safari... because the test only handles Firefox.
Yup. Because I use my own browser. Built from scratch with exception of V8, Stylo html5ever, and a few other bits and bobs. A fresh new rendering engine in Rust and all. Not a fork of any existing engine. Native support for uBlock Origin filter lists and custom filters. It scores above ~20 in speedometer as of today and covers WPT about 89%. Will be publishing it soon as permissive open source.