- From: Michael Hyun via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2024 17:29:57 +0000
- To: public-webrtc-logs@w3.org
I guess my main concern was that the handle can be spoofed - what's stopping someone from re-setting the capture handle, with some other handle config? If not, then this would support our use case, although the only downside then would be browser support - as this seems to only be a chrome feature. We are also considering the stenographic approach - where we ask the captured side to embed a QR code. On the capturing side, we'd process the captured side's mediastream and run it through a video processor in order to decode the QR code. This would give us more browser support - was wondering what your thoughts were on that. Thanks! -- GitHub Notification of comment by michhyun1 Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/73#issuecomment-1934614035 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 February 2024 17:30:03 UTC