←back to thread

Apple declined to implement 16 Web APIs in Safari due to privacy concerns

(www.zdnet.com)
428 points coronadisaster | 1 comments | 29 Jun 20 10:16 UTC | HN request time: 0s | source
Show context
phkahler ◴[29 Jun 20 13:32 UTC] No.23677378[source]▶
Those APIs should not exist. Web site creators need to stop acting like they are entitled to access whatever they want on someone's computer.

I dont care about your unique SaS usecase, these are invasive. Make a native app if that's what you need.

replies(3): >>23677439 #>>23677650 #>>23679378 #
azangru ◴[29 Jun 20 13:58 UTC] No.23677650[source]▶
Why is accessing this via a native app better than accessing it via web browser?
replies(4): >>23677681 #>>23678522 #>>23678723 #>>23680258 #
evgen ◴[29 Jun 20 14:02 UTC] No.23677681[source]▶
I am less likely to accidentally give you permission over my computer to do shady shit if I am forced to install an app vs happen to click the wrong link on my browser.

The difference is intent. By installing Chrome I do not intend on giving up every last bit of privacy and control over my computer, they just want to trick me into doing so by stuffing functionality into web APIs that should never have been web APIs in the first place.

replies(3): >>23679204 #>>23679457 #>>23689582 #
1. bagacrap ◴[30 Jun 20 13:05 UTC] No.23689582[source]▶
A native app, once installed, basically owns you. With a web app you have to explicitly grant permission for each and every API (of the kinds listed in TFA at least). Are you in the habit of accidentally clicking "accept" in a series of permission prompts? Even if the answer is yes, it's ok, as it's very easy to revoke the permissions in your browser.

There's no way you can argue that a single "grant all permissions" step is more privacy friendly than fine grained permissions.