3 ms·
Tl;dr wow, just wow. So we have three fingerprint mechanisms: One I had not even heard of or frankly suspected, but it explains a lot about why many designers
by lifeisstillgood 12y ago
Tl;dr wow, just wow.
So we have three fingerprint mechanisms:
One I had not even heard of or frankly suspected, but it explains a lot about why many designers who strive for pixel perfection are constantly frustrated. The original paper is fascinating (cseweb.ucsd.edu/~hovav/dist/canvas.pdf) but one simple takeaway - testing 300 different user systems (Mechanical Turk - quite clever) a simple sentence in Arial rendered 50 different ways! So by combining different renderings (like sentences, drawing a line on a canvas element) they find that user systems - hardware, drivers etc, give off different results unique enough to tag you.
I would be interested in their results on iPhones (in fact any one interested in a quick experiment here in HN?)
And cookies - the synching cookies where fucking trackers collaborate and share / copy each other's ids, and ever cookies where they store a cookie in JavaScript/cookie and anywhere else and keep respawning.
Little fuckers
I propose two solutions:
Cookies should be limited to no more than 128bits - enough to store one randomly generated UUID. Screw the backward compatibility.
And we should be able to only allow signed hashed JavaScript to run on our machines. For example I want to only allow say bootstrap and some overlay and a config or data file. No one gets to run unsigned js on my machine?
Have I just reinvented Microsoft code signing?
But boy I am in a bad mood