- From: Uriahs Victor via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Oct 2022 04:00:43 +0000
- To: public-geolocation@w3.org
I really don't know why this > The sticking point is that background geolocation access changes a really fundamental property about how users think about privacy on the web. Today, when you close a tab (or switch to another app on mobile) a site can't keep running in the background indefinitely collecting information about you (like your location). > > When building APIs for native apps, platforms can depend on a store review process to catch malicious apps. When designing for the web we have to be a lot more cautious about how APIs are designed to keep the user in control because anybody can create a website and we know there are a lot of malicious actors out there. Some kind of notification like you suggest might be part of a solution. > > Given the potential privacy harms this isn't something the Working Group is currently putting effort into specifying. Thanks for the reply, the reasoning you gave raises a lot of possible other questions and can be debunked but I guess the main point is you guys are withholding this functionality in the name of privacy... -- GitHub Notification of comment by UVLabs Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/131#issuecomment-1275554161 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 October 2022 04:00:45 UTC