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]▶

>>23677378 #

Why is accessing this via a native app better than accessing it via web browser?

replies(4): >>23677681 #>>23678522 #>>23678723 #>>23680258 #

1. joeblau ◴[29 Jun 20 18:00 UTC] No.23680258[source]▶

>>23677650 #

I wouldn't have any problems giving these APIs access via the web, but one challenge with the websites is that I'm never 100% sure that when I "retract" a permission or say "stop tracking me" that it's done. I think that if access to these API's were wrapped in some sort of Privacy API that superseded each website's privacy and data collection polices I would be more comfortable with this. These changes just seem like something Google threw over the wall to get things working with Chrome and every other browser developer said "no thanks".

↑