Hacker News new | past | comments | ask | show | jobs | submit login

As the original comment states, there's not magic sandbox solution. It's a hard problem. The average user should be able to grant or deny capabilities. For things like location it's easy but when you think about the botnet case, things get tricky. What ip ranges do you allow?



There's no way to fix the problem natively, either. Apple's "solution" to this issue is checking every app personally, which is a fallible and expensive approach. Apple will pretend they're taking the high road, but it doesn't take a genius to surmise they only care about that process because it's expensive.

No matter how you slice it, this is already a problem and literally no one blames Apple for it. It's not Apple's job to blacklist phone numbers that contain scam callers, it's not Apple's job to protect Safari users from content that harms them. The EU is very unlikely to approve any scheme where Apple is still a gatekeeping party.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: