I can imagine that having several typical configs and switching between them at random would help blend in.
You have to be careful with that too. An anti-anti-fingerprinting implementation can record the values and compare them across visits to see whether they stay the same. If they change every few months that's reasonable (eg. changing hardware), but if they change every day or every week there's most certainly spoofing involved.
Maybe an explicit sign of spoofing is even better, it sends a message in a gentle way.
Unspoofing on the server side, if at all possible, would likely be too expensive for whatever gain it might bring.
I feel like going there and telling them to stop following me around.
gl.getParameter = () => "test"
but that's easily detectable. If you run gl.getParameter.toString()
You get back "() => "test""
whereas the original function you get back "function getParameter() { [native code] }"
In general, don't try to fix fingerprinting via content scripts[2]. It's very much detectable. Your best bet is a browser that handles it natively.[1] https://developer.mozilla.org/en-US/docs/Web/API/WEBGL_debug...
[2] https://palant.info/2020/12/10/how-anti-fingerprinting-exten...
await navigator.storage.estimate() -> gl.getParameter.toString.toString()
<- "() => 'function getParameter() { [native code] }'"
Not to mention the iframe trick mentioned in palant's article. gl.getParameter.toString() = () => 'function getParameter() { [native code] }'
gl.getParameter.toString()
"function getParameter() { [native code] }"
gl.getParameter.toString().toString()
"function getParameter() { [native code] }"
gl.getParameter.toString().toString().toString()
"function getParameter() { [native code] }"
iframes, worker, sharedworker, serviceWorker are all covered. Good luck timing the difference. gl.getParameter.toString().toString()
what the comment you're replying to is trying to tell you to run is: gl.getParameter.toString.toString()
Call toString on the toString fuction, not on its result.