- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Sep 2023 04:07:13 +0000
- To: public-geolocation@w3.org
> you [folks] are withholding this functionality in the name of privacy... I think this needs to be flipped: how can this be done without putting user's privacy at risk? It may not be possible to support this kind of functionality for regular browser tab style applications, but it may be possible to do something if the web application is "installed". There's some precedence nowadays for APIs that are exclusively exposed if and only if an application is installed (e.g., badging API, some push implementations). I'm not proposing that this is feasible or will be acceptable to various privacy and security teams, but just that we need to consider alternatives. At the same time, I would ask that folks don't propose solutions here (unless you are willing to sign Intellectual Property Rights commitments). If anything is going to happen it will likely happen through the WICG's incubation process. See [contributing new proposals](https://github.com/WICG/admin#contributing-new-proposals). -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/131#issuecomment-1704580608 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 September 2023 04:07:15 UTC