If you’re building something and you lift up a rock and find a lot of weird solutions to a problem you’d never really thought through crawling under it, what would you do?
1) Ban them immediately, no matter how necessary to parents, as the risk of tracking/stalking of all iPhone users is unacceptable
2) Build a safer solution that can’t be harnessed for tracking/stalking, and then ban all solutions that can be used for tracking/stalking
Seems like they chose the latter. It’s easy to construct a case for why it is technically inappropriate to allow third-party apps in this space, that I personally boil down primarily to “a frequently-abused chance for corporate entities to monetize the user data of minors”.
Apple took years to implement content filtering, and did so in a way that prohibits applications from knowing whether their filters are ever exercised, as otherwise Facebook and other malicious entities would long ago have added a filter for ^(.*)$ to transmit every request to third-party servers. Is their refusal to permit otherwise anti-competitive, security-forward, or both?
Apple, if I understand correctly, prohibits third-party keyboards in certain password-type dialogs on iOS because keyboard apps are allowed to send network requests. (They are allowed to do so because e.g. GIF search.) Is this prohibition anti-competitive, security-forward, or both?
We as a community need to become a lot more careful with use of the phrase “anti-competitive”, as many industry-standard security practices that we would demand of any product we build and use are then labeled “anti-competitive” solely when they interfere with us doing anything we like, or when they’re done by an organization that doesn’t share its internal discussions with us when making decisions on our behalf.
Is it appropriate to stifle the competition for my personal data, even if that is, in a literalistic interpretation, anti-competitive?
I sure hope so.