- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jan 2024 16:01:36 +0000
- To: public-webrtc@w3.org
youennf has just created a new issue for https://github.com/w3c/webrtc-pc: == Should media capabilities influence what is exposed in what is exposed in WebRTC offers and answers == WebRTC implementations currently tend to expose the whole list of codecs that are available. On contrary media capabilities is telling whether a particular codec is supported. For some codecs, like VP8, VP9 and H264, it might be fine in terms of privacy since most UAs support them. For newer codecs though, it is an actual issue. Maybe what WebRTC exposes in terms of codecs should be based on what MC already exposed to the web page, in addition to the base offering that has no privacy issues. This could apply to offers as well as receiver/sender getCapabilities. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 January 2024 16:01:39 UTC