Bigger question: why isn't Firefox and Tor Browser modifying the JavaScript repo... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		mystraline 5 months ago \| parent \| context \| favorite \| on: Web fingerprinting is worse than I thought (2023) Bigger question: why isn't Firefox and Tor Browser modifying the JavaScript reporting calls to lie? All machines would have 16 cores and 32GB ram, running windows 10, and 1 point-touch or mouse. And the resolution would also be fixed as reporting, and only on client would change. The user-agent should be acting on our behalf. So, why isn't it (Firefox, TBB) utterly lying and acting in our interest? We know why Chrome wouldn't. Tor also gave up this web fingerprinting fight without even really trying. Editing the JavaScript calls to consistently lie the same way was "too hard". https://m.youtube.com/watch?v=3wlNemFwbwE

rsync 5 months ago [–]

Going further: why does Firefox allow site operators to dictate common user interface restrictions?

Infantile developer behaviors like disabling paste in the password field? Or bona fide on page text that cannot be selected in the browser window?

There is no reason for Firefox to enable or honor these requests.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact