←back to thread

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

(www.zdnet.com)
428 points coronadisaster | 2 comments | 29 Jun 20 10:16 UTC | HN request time: 0.082s | 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 #
danaris ◴[29 Jun 20 15:55 UTC] No.23678723[source]▶
Creating these APIs doesn't just grant access to them to well-thought-out PWAs with a clear use case.

It grants access to every shady malware ad that wants to siphon your data and that of everyone around you.

replies(3): >>23679168 #>>23679432 #>>23679693 #
mercer ◴[29 Jun 20 17:21 UTC] No.23679693[source]▶
To what degree is this true for App store apps too though? What with the Facebook (sign-in) SDK and all? Honest question.
replies(1): >>23683288 #
1. phkahler ◴[29 Jun 20 21:24 UTC] No.23683288[source]▶
With app store apps I am told what permissions they need and I usually opt to not install them, but it's hard to get by without a web browser these days.
replies(1): >>23731263 #
2. mercer ◴[04 Jul 20 09:46 UTC] No.23731263[source]▶
That's a good point.