- From: Brad Isbell via GitHub <sysbot+gh@w3.org>
- Date: Sun, 22 Nov 2020 04:00:24 +0000
- To: public-webrtc-logs@w3.org
Thanks @jan-ivar. While I haven't encountered a device labeled with its serial number or network name, I don't doubt that these cases exist, and I understand the concern. However, it is clear that users expect web-based applications to identify their media devices in the same way that other applications do, which is in-conflict with sanitizing device labels. Here is a common example. My system has multiple sound devices, and I have configured some of them with custom labels. `Main` would have originally been named `DVS Transmit 1-2`, and `Monitor` would have been named `DVS Transmit 3-4`. (The "original" labels I'm referring to here come from the driver and its accompanying software.)   It's important to note that in these cases, the only distinguishing factor is this device label. It's standard built-in capability to rename these devices. All other audio applications I know of are capable of using these devices by their configured names. Users expect to see audio devices labeled the same across all applications, whether they are web-based or native. Sanitized/modified labels are damaging to usability. > I don't think users would expect browsers to leak personally identifiable information like their full name in a camera/microphone API, even behind permission. I disagree. If I have labeled an input, "Brad's Isbell's Microphone", and want to use it with a web application, I expect that web application to be able to display, "Brad Isbell's Microphone". This is just an anecdote though... I don't want to assume what other users may want, which is the key point: This decision should be left to the user, and not predetermined by a specification. -- GitHub Notification of comment by bradisbell Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/747#issuecomment-731694998 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 22 November 2020 04:00:27 UTC