- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Sat, 25 Jun 2022 19:29:46 +0000
- To: public-webrtc-logs@w3.org
> CropTarget UUIDs are lightweight and offer apparent user benefits. My point is that you can get all the user benefit without the risks by keeping it as an opaque token. The UUID is still opaque if it observes [these guidelines](https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1165788089). I believe the crux of your concern is not opaqueness, but rather transmissibility to remote servers. I believe transmissibility to be desirable, because it allows cross-origin collaboration that would easily hook up to existing infrastructure. You have brought up a possible [abuse scenario](https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1165437485). I don't personally see it as credible, but we can have different opinions, that's fine. I have [shown](https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1166239345) that technically, the same concern exists already; however, now you believe my scenario is not credible. (That's also fine.) How do we resolve this? Do you have a suggestion for determining which concerns are credible and which are not? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1166348786 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 25 June 2022 19:29:47 UTC