News for hackers. Stuff that matters.

A comment on Audio Fingerprinting using the AudioContext API. Parent comment

Re:Audio Fingerprinting using the AudioContext API by Mirioron on Sunday November 03, 2019 @07:54PM (#21438010)
>For example, you can't determine whether the user has 3 audio devices connected and prompt them to select one for output.

Frankly, this really should be handled by the browser. JavaScript really shouldn't have any business messing with that.

[ Parent | on HN ]
Re:Audio Fingerprinting using the AudioContext API by zaroth on Sunday November 03, 2019 @08:56PM (#21438331)
I have no problem with sites being able to do this, after I’ve given them permission to access the audio stack in the first place, and limited to first-party scripts on the page.
[ Parent | on HN ]
Re:Audio Fingerprinting using the AudioContext API by sriku on Sunday November 03, 2019 @08:49PM (#21438301)
That's reasonable for just output selection. So shouldnt be able to send audio to all the devices? .. and different audio streams? .. which is all commonplace in the desktop world.
[ Parent | on HN ]
Re:Audio Fingerprinting using the AudioContext API by Mirioron on Monday November 04, 2019 @02:26AM (#21439597)
Sure, but the browser should handle that logic. Even if the website prompts a user to select an audio device it should be handled on the browser's side without feedback to the website.
[ Parent | on HN ]