3 ms·
> Much of this blame goes on Android and some on iOS/Apple. Which part of the blame goes on Apple?
by soziawa 9y ago
> Much of this blame goes on Android and some on iOS/Apple.
Which part of the blame goes on Apple?
- endymi0n 9y agoApple had zero permission management on the contact book, it was wide open. Especially FB and LinkedIn exploited that heavily and partly do to this day.
- jahnu 9y agoOh really? I didn't know that. Can you link me up with something about that? Thanks.
- drawkbox 9y agoMany apps grabbed contact lists. Path for instance even had an issue with the FTC due to it [1]. Apple implemented better permissions pretty quickly. I recall other apps doing the same up to 2013. [1] https://www.ftc.gov/news-events/press-releases/2013/02/path-social-networking-app-settles-ftc-charges-it-deceived https://www.ftc.gov/news-events/press-releases/2013/02/path-...
- stefanmm 9y agonot so true. "Users can grant or deny access to contact data on a per-app basis. Any call to CNContactStore will block the app while the user is being asked to grant or deny access. Note that the user is prompted only the first time access is requested; any subsequent CNContactStore calls use the existing permissions." https://developer.apple.com/documentation/contacts#1773385 https://developer.apple.com/documentation/contacts#1773385
- drawkbox 9y agoThey do today, back up to 2012-2013 they did not. Apps were also overly abusing it back then such as Path [1] and many others. > The operator of the Path social networking app has agreed to settle Federal Trade Commission charges that it deceived users by collecting personal information from their mobile device address books without their knowledge and consent. Android didn't really close/tighten permissions until 2014 with Android 4 Ice Cream. [1] https://www.ftc.gov/news-events/press-releases/2013/02/path-social-networking-app-settles-ftc-charges-it-deceived https://www.ftc.gov/news-events/press-releases/2013/02/path-...