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 throwaway40324 on Monday November 04, 2019 @11:00PM (#21449481)
It's been a little while since I used this, but navigator.mediaDevices.enumerateDevices

will give you that list, allowing you to have a menu for a user to choose one and then the client code must use setSinkId to assign the chosen device id. https://developer.mozilla.org/en-US/docs

[ Parent | on HN ]
Re:Audio Fingerprinting using the AudioContext API by sriku on Monday November 04, 2019 @11:55PM (#21449736)
The IDs you get (both deviceID and groupID) are not user displayable. They're like random numbers. In normal browsing mode, you keep getting the same deviceIDs for the same domain, but random groupIDs for every refresh. You get different deviceIDs for different sites. In private browsing mode, you get both random every time.
[ Parent | on HN ]
Re:Audio Fingerprinting using the AudioContext API by throwaway40324 on Tuesday November 05, 2019 @12:09AM (#21449808)
Ah, I forgot that the device label is only returned when there is an active stream. And has zero support in Safari. https://developer.mozilla.org/en-US/docs/Web/API/MediaDevice...

I never knew the device ids were randomized like that, thanks for the info.

[ Parent | on HN ]