Hacker News Reader

Comment by dt3ft | Hacker News Reader

> Your browser is not comparable to the dataset, so we have avoided showing you inaccurate results.

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.

View on HN

And cloudflare, akamai, and hcaptcha lock you out of 80% of the Web.

Nope. YouTube, for example, works like a charm. Settings allow users to select a user agent (chrome, edge, firefox, safari) or set a custom one.

YouTube isn’t really known for their bot protection afaik. You’re able to get through the Cloudflare interstitial and fully solve/submit hCaltchas? They run actual JS fingerprinting which is where I think something like this would show

better said youtube does not block most bots on purpose, they do work after to cleanup botted engagement after the fact

I'm getting this too on main release Safari... because the test only handles Firefox.

Given TFA, I have to assume you are bragging about being the most fingerprintable user on the Web.

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?".

> 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 to detect that the user was offered and clicked a permission in a dialog.

Really. This whole field is the devil’s work.

Basically we need something like NoScript that also covers 20-questions API identification.

Are there add-ons which do this?

I get this on privacy-focused FF forks, then a lecture about the version.

For what it's worth, this test also can't get legitimate header info.

Reply on news.ycombinator.com