- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Nov 2024 11:52:16 +0000
- To: public-webrtc-logs@w3.org
> I would go with mandating the behaviour, otherwise there is no real point for a spec. The authors of [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119) seem to have had a different opinion, and that appears to be the industry standard atm. Specifically, I am thinking we could use "SHOULD" here. > > If the user reloads the the video conferencing application, the capturing app should get new IDs. Otherwise, we'd be exposing which tabs/windows are still there, which needlessly goes beyond the current MVP. > > What are we trying to protect? Thinking out loud: - If I am in a video call and I share the same tab/window twice in a row during the call, it might be reasonable that the Web application knows it's the same tab. - If I share the same tab/window the next day, this becomes a bit less expected. - The more days pass - the more unexpected it becomes. Is it a problem? I am not sure. But do we want to engage a lengthy privacy review of something no Web developer has asked for yet? I worry it might not be good use of anyone's time. If we start small and it's proven useful, we could consider extensions later. > Device IDs should be hashed per origins yes, just like cameras and microphones. Great, we're in agremenet here. And likely this already yields the result I was after for the previous point? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/308#issuecomment-2456967921 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 November 2024 11:52:17 UTC