- From: Sun Shin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Mar 2023 16:55:06 +0000
- To: public-webrtc-logs@w3.org
> > its really important to not add FP surface > > @pes10k In your opinion, is exposing powerEfficientDecoder adding FP surface _in a context that already has MC's powerEfficient_? The difference between the two is so subtle that I would argue that hiding powerEfficientDecoder _in this context_ does not really improve the FP situation compared to exposing it. And if it does not, this pull request is approximately FP neutral. In which case we're hurting a real use case without improving the FP situtation. > > > Just to throw a straw proposal on the table though, why can't the cloud gaming folks just prompt the users? > > I'm open to the idea that other APIs prompt (if it makes sense for those APIs) and that getStats() piggybacks on the permissions of the current context, but getStats() should not prompt since this is a passive API being polled in the background to get quality metrics and not relating to a user action. There are 200+ metrics so the app could poll this API for any reason, so asking for HW permission as a result of someone wanting to know the bitrate of their data channel does not make sense. > > > we do not request any additional permissions other than what is necesasray for the streaming in general usecase > > @xingri Is it the case that the normal use case of no microphone has 0 prompts? Or is there any other prompt that we could piggyback on? @henbos There are two usecases for the "normal use" and "first use", when the "first use" use case, the Nvidia Cloud Game requests the clipboard and the microphone prompts but the decisions on the prompts do not impact the "normal use". And once the decision has chosen, there are no additional prompts for "the normal" use case. So in case of "normal" use case, it has 0 prompt.   -- GitHub Notification of comment by xingri Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/732#issuecomment-1450480050 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 March 2023 16:55:07 UTC