- From: Carlos Lopez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2023 12:27:11 +0000
- To: public-device-apis-log@w3.org
I had a use case listed before, but I just recently was asked to write a tracker for an airport shuttle and I'm delivering today, coincidentally. The concerns of privacy are basically none since it will eventually be given free to the public. All the mechanics of how it works are built and functional though requires the shuttle driver to constantly keep the device awake with the screen on. And I've had to stress not to get OLED devices. I'm pretty sure all user agents interested in implementing this API already have mechanics in their platform to high visibility notifications. I know because I used to write GPS tracking systems in native Android and iOS 9 years ago. And before that, we used custom HAM radio equipment. It's all Web Apps now. When we do WebRTC, I know iOS gives (maybe not anymore) a pretty high visibility of a microphone in use, changing the status bar completely red. I think they use blue for notifications. Android does persistent notifications that can't be hidden. Also, Safari does restrict certain APIs to Added to Home Screen (PWA). They do this for Push Notifications. I don't mind if we need to jump through hoops to get background geolocation. This eliminates the ability of random, unrecognized sites being able to just track users. Still, levels of restrictions are something that can be tweaked later. I think iOS 17 is now better equipped to separate permissions on a per-app basis instead of just assigning all Home Screen Apps the same permissions as Safari. -- GitHub Notification of comment by clshortfuse Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/22#issuecomment-1699070927 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 August 2023 12:27:13 UTC