@ariadne anti-fingerprinting feels like a pyrrhic victory to the extent it can be achieved

sure, random webpages probably don't need to know how many cores you have (and thoughtful design could keep this available to those few which maybe do). but the thing that made me conclude this is Accept-Language:, a feature that is intentionally made worse for bilingual users in service of reducing fingerprintability. i think i'd rather have that than a (in practice) false promise about privacy

@whitequark @ariadne At some point we need to start legislating these things instead of trying to patch over them with technology.

Like, there is zero legitimate reason for fingerprinting to uniquely identify individual users at scale. It should simply be illegal. This does not preclude stuff like identifying bots. Ad stuff should just use cookies where allowed.

@ariadne @lina i ship an FPGA toolchain in the browser. it can* use multithreading. it needs to know how many threads to run to not contend on resources uselessly

* currently not built in that configuration for a variety of reasons that is not specifically tied to the web

@sabrina @iyashikei_kris @mcc @whitequark @ariadne I think CSS is getting there but although it can do most things people would want these days, some things would have to be upgraded from "horrible hack" to first class support. Like this stuff:

https://www.codegenes.net/blog/show-hide-div-on-click-with-css/

Basic toggleable UI elements should not require hacks like fake check boxes.