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

Adding noise to images sounds like a really bad idea. It will mess with any Javascript code which performs processing on images. Try writing a photo editor in Javascript and watch your browser corrupt your images.


Like the articel says those features can be disabled on a per site basis.


You are able to toggle these specific named categories:

* Cookies

* Tracking Content

* Cryptominers

* Known Fingerprinters

* Suspected Fingerprinters

But there is no separate toggle for the feature that adds noise to the image, or indication of which toggle would affect that.


It's 'Suspected Fingerprinters' that controls the Fingerpritning Protection feature described in the blog post. But yes, naming and descriptions is hard and never seems to work.

But to disable it on a per-site basis, I would just disable ETP for the entire site. If it's a service or site you use frequently you probably trust them or otherwise have a login to them that makes trying to avoid fingerprinting illogical.




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

Search: