,
5 tweets,
2 min read
Read on Twitter
@alexstamos This is tricky to do from a purely technical standpoint because apps will just take everything currently hitting 3rd party endpoints and start proxying it through their own domain, causing more opacity and likely new classes of security vulnerability.
@alexstamos Apple has been trying to push something like this in the W3C for web apps, where composing apps from multiple sources (like CDNs) a is fundamental part of the platform and analysis-in-advance isn't possible.
@alexstamos I and others have asked Apple to prove the viability of this concept on their own platform first, where they do set policy and can do analysis, but they so far have refused.
@alexstamos I think it says something about priorities and when privacy matters to Apple that they are willing to impose absolutely massive breakage on an open platform from which they get little revenue - the web - but not on their own platform where they can set all the rules.
@alexstamos Given that these SDKs power developer monetization strategies that evade the Apple tax, you'd think they would be happy to block more. That they don't suggests they know it would decimate the app store and make iPhones more expensive and ultimately less useful to consumers.
