Some additional thoughts. It feels like APIs like the upcoming marker detection API will be important for doing things in a privacy preserving fashion. While I understand that raw camera access will allow developers to do lots of things there need to be appropriate drawbacks and warnings because once you spin up this access you're really giving the web site everything. I'm thinking especially of the cases where an application is designed to perform a certain function (e.g. you're at a restaurant and you scan a QR code to bring you to a web app that allows you to draw funny ears or hats on people's faces) that requires facial recognition and therefore raw camera, but then uses that same facial recognition data for a secondary use contrary to the user's expectations (e.g. correlating that info with other facial recognition info to build up a list of people who were with you at the table for sale to 3rd parties). Beyond permissions, it really feels to me like there needs to be some additional drawbacks for use of this API that would encourage developers to use the privacy-preserving WebXR AR APIs instead unless the really need Raw Camera access. Have you considered this approach in the working group? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/652#issuecomment-915113636
Received on Wednesday, 8 September 2021 10:24:32 UTC