News for hackers. Stuff that matters.
Re:Audio Fingerprinting using the AudioContext API by MisterTea on Sunday November 03, 2019 @06:47PM (#21437618)
And then the site totally fails. I'm no fan of JS either but the amount of sites that use JS is now close to 100%. So you either stay paranoid and the web breaks or you eat the shit sandwich. Pure lunacy.
Re:Audio Fingerprinting using the AudioContext API by jacquesm on Sunday November 03, 2019 @07:50PM (#21437982)
> And then the site totally fails.

That's ok. Then I have the option to weigh whether the risk is worth it or rather not. 9 out of 10 times it is not, in rare cases I will allow the js to execute.

Re:Audio Fingerprinting using the AudioContext API by waste_monk on Sunday November 03, 2019 @11:31PM (#21439064)
Not viable for the majority of users.

How do you explain to one of these "I'm not good with computers haha" types what a CDN is and why Taboola CDN shouldn't be allowed but Akamai should be otherwise things Won't Work Right. Even if they're capable of learning [1] why should they care, when all these security measures actively make their life harder?

Blocking audio and other fingerprintable surfaces by default, with a "click here to enable audio / video" and a "remember my choice on this site in future" is the only way it can possibly work, because 99% of users will only ever go for the laziest option. We need to have protections for them that work regardless of (or in spite of) their skill level.

[1] https://www.nngroup.com/articles/computer-skill-levels/

Re:Audio Fingerprinting using the AudioContext API by gpderetta on Monday November 04, 2019 @06:52AM (#21440786)
Possibly curated, subscribable whitelists?