Re:Online tracking: A 1-million-site measurement and analysis
by englehardt on Thursday May 19, 2016 @09:31AM
(#11730023)
Yes, no sound is recorded. Access to the user's mic isn't possible without a permission. If there are sections of the website or paper that seem to imply that, let me know and we'll clarify.
[ Parent
| on HN ]
Re:Online tracking: A 1-million-site measurement and analysis
by Brakenshire on Thursday May 19, 2016 @11:02AM
(#11730755)
It seems strange that access to the audio stack isn't also behind the permission.
Re:Online tracking: A 1-million-site measurement and analysis
by crispyambulance on Thursday May 19, 2016 @11:43AM
(#11731052)
It does, and also as someone who has never heard of AudioContext before, I can't fathom why it would be necessary for a web application to generate an audio data stream that isn't output to speakers _AND_ _THEN_ analyze the result.
What is the typical use case for AudioContext?
The capabilities of AudioContext used in audio fingerprinting seem like they're beyond what is really necessary?
Re:Online tracking: A 1-million-site measurement and analysis
by chatmasta on Thursday May 19, 2016 @01:19PM
(#11731807)
AudioContext is actually pretty cool. As far as I know, only Firefox supports it at the moment. But it allows you to work with audio streams in raw byteform, which means you can do advanced audio processing in client side javascript.
Re:Online tracking: A 1-million-site measurement and analysis
by vox_mollis on Thursday May 19, 2016 @11:36AM
(#11730990)
Presumably, an application would need to enumerate audio capabilities before even offering the option.
Re:Online tracking: A 1-million-site measurement and analysis
by hackuser on Thursday May 19, 2016 @01:58PM
(#11732177)
The front page [1] doesn't say either way, and I wondered the same thing when I read it. A few words or a link to an explanation would be helpful.
[1] https://webtransparency.cs.princeton.edu/webcensus/index.htm...
Re:Online tracking: A 1-million-site measurement and analysis
by englehardt on Thursday May 19, 2016 @02:16PM
(#11732350)
Thanks, I've added a clarification.