Explain the Concern

Posted by Matt Birchler
— 1 min read

Is WebKit Sabotaging the Future of the Open Web?

Why can’t the WebKit developer energy be spent on building these great new APIs and connect them with user empowering privacy tools. A great example of what I mean is website location tracking. If a website wants access you your location (for say driving directions) you can grant it access. I don’t understand why a similar approach could not be applied for things like Web Bluetooth access or Proximity sensor access.

I think the miss here is a communication one, primarily. I sympathize with Mike's point about being baffled by some things on the list of "privacy unfriendly" browser features shall not be implemented, all while things like your exact location are allowed and hidden behind an access warning. I don't think there is a clear answer as to what makes a feature "secure" or not from their perspective, and that's the miss. If there was something we could point to and see why the battery status API is worse than location access, then it would feel like a decision made on more solid ground.