- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Oct 2018 22:00:01 +0000
- To: public-webrtc-logs@w3.org
Prompting has a cost. First, one needs the right message to convey all the implication to the user. When sharing camera and/or microphone, the user is somehow understanding that some privacy is getting lost. The message you suggested might not enable the user to understand the implications of their choice. Second, the more you prompt, the more the prompts become meaningless as users will start clicking without caring about the choice. As of the use cases you are mentioning above, I believe data channel use cases might be the most impacted by not exposing host candidates or exposing through mDNS only. For audio/video cases, if one of the user is giving access to camera/mic/screen, the other user does not need to provide host candidates. If a user is a native app (remote device access, drones...), it could be its own STUN server and the native app will probably provide its host candidates. For use-cases that are synthetic audio/video, it might be cheaper to send the parameters to regenerate audio/video on the other side, which then goes back to data channel only. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2012#issuecomment-432001667 using your GitHub account
Received on Monday, 22 October 2018 22:00:02 UTC