Hacker Newsnew | past | comments | ask | show | jobs | submit | royfish's commentslogin

Right. What has changed about fingerprinting though is that since last year Google allows it in their ad products. And, unlike cookies, you can't just delete your fingerprint. The average internet user hasn't even heard about it, so we need to be vocal about it.


I get "Noisy Axolotl" on latest MacOS version and default protection. I can see Mullvad is disabling the WebGL render and randomizing canvas output. The difference probably comes from some low entropy signals that Mullvad doesn't mask, so it's not literally same identity for everyone.


I'm getting "Nosy Axolotl" on Linux.


I did want to add a counter and see how my script would perform in the wild! But that'd mean I have to store these fingerprints and that requires a bunch of formalities I don't want on my website.

Anyway, it's a simple script for the sake of demonstration. I'm sure you'll get a different hash on other browsers/devices.


"Cookies are a way to track you. Fingerprinting is a way to detect fraud. They are completely different."


I don't know what you are insinuating. If whatever you're doing if fraudulent - that's on you.

Cookies implement a persistence mechanic, so yes, it is a manner of tracking an existing session/identity.


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

Search: