Earlier quoted context omitted.
They should enforce that Do Not Track is honored. Its the easiest way, and websites dont need silly cookie consent dialogs if set.
DNT is ~useless because it's opt-out, whereas "auxiliary", non-essential tracking is opt-in under GDPR. Websites don't need cookie consent dialogs if they only use cookies to do things that don't need to be consented to, like providing the service they are offering. Look at Apple's website, they don't have any.
Web fingerprinting is worse than I thought
271–280 of 524 posts
Re: Web fingerprinting is worse than I thought
#272Re: Web fingerprinting is worse than I thought
#273Earlier quoted context omitted.
Except that disabling JavaScript is an anomaly all on its own. The dozens of users running without JavaScript might not be individually fingerprint able but it's still a small enough cohort that I don't know how much I'd lean on that. Figure in the user agent string and it's probably unique enough a subgroup to sell ads to.
More common than you think https://amiunique.org/fpnojs
Re: Web fingerprinting is worse than I thought
#274Re: Web fingerprinting is worse than I thought
#275What is the use case for these fingerprints when adhering to the GDPR? You can't store them in a DB and use them to target your returning anonymous visitor with products relevant to their last visit. You can't send them to a third party ad service to get more relevant ads. Isn't the whole point of the fingerprint to maintain an pseudonym for your users over some time window? But that requires storing them which would…
To prevent spam. If someone is spamming your site how do you tell if a request is coming from a legitimate user or if it is coming from the spammer. Fingerprints are how you can tell the two apart.
Re: Web fingerprinting is worse than I thought
#276Re: Web fingerprinting is worse than I thought
#277Earlier quoted context omitted.
Sure fonts and text is hard. But none of that is needed for basic surfing of the web.
Either there is a complete and total consensus on every aspect of rendering or there are differences in how is rendered.
Re: Web fingerprinting is worse than I thought
#278Earlier quoted context omitted.
And the tweet is correct, unfortunately: https://www.jefftk.com/test/webmidi Looks like Chrome is trying to change this, and is slow as usual: https://groups.google.com/a/chromium.org/g/blink-api-owners-...
> is slow as usual: It's funny because for anything Chrome deems beneficial to Google they are anything but slow, including shipping APIs that no other browser agreed on.
Re: Web fingerprinting is worse than I thought
#279And it probably understates the problem these days, missing some of the more recent techniques.
Re: Web fingerprinting is worse than I thought
#280What is the use case for these fingerprints when adhering to the GDPR? You can't store them in a DB and use them to target your returning anonymous visitor with products relevant to their last visit. You can't send them to a third party ad service to get more relevant ads. Isn't the whole point of the fingerprint to maintain an pseudonym for your users over some time window? But that requires storing them which would…
To prevent spam. If someone is spamming your site how do you tell if a request is coming from a legitimate user or if it is coming from the spammer. Fingerprints are how you can tell the two apart.