1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition
BREAKING: @CommonsCMS @DamianCollins just released previously sealed #Six4Three @Facebook documents:
1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition
Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.
https://t.co/PwiRIL3v9x
However, docs show lead of privacy program was actively working to evade user consent https://t.co/mcXhDnSg2i
Huh, Yul Kwon (head Facebook 'privacy sherpa') was supposed to be making sure new features were privacy compliant, not making sure Android users weren't notified Facebook was getting more information off their phones https://t.co/KubqX6OMo5 https://t.co/ooEmSdwvve
— Kashmir Hill (@kashhill) December 5, 2018
@Facebook statements re: Android SMS and Call Log History
1) internal discussion Feb 4 2015
2) public 'clarifying' statement Mar 25 2018
@Facebook's director of platform offered to 'unblock @Tinder's monetization possibilities' if @Tinder permitted use of 'Moments' trademark:
https://t.co/VkJGD4hp5E
Q: Are there any contracts or other steps besides whitelisting to launch a feature using the APls?
A: You don't need to worry about any contracts for the api. This is a product we are testing and will be rolling out slowly.
(NEKO is an acronym used to describe mobile app-install ads)
It most clearly lays out the strategy of the company with regards to platform API and user data:
Developers provide:
FB provides: access to platform (userdata/friends)
https://t.co/0oh1dGIDvd (ht @EuanDBriggs)
More from Tech
You May Also Like
The entire discussion around Facebook’s disclosures of what happened in 2016 is very frustrating. No exec stopped any investigations, but there were a lot of heated discussions about what to publish and when.
In the spring and summer of 2016, as reported by the Times, activity we traced to GRU was reported to the FBI. This was the standard model of interaction companies used for nation-state attacks against likely US targeted.
In the Spring of 2017, after a deep dive into the Fake News phenomena, the security team wanted to publish an update that covered what we had learned. At this point, we didn’t have any advertising content or the big IRA cluster, but we did know about the GRU model.
This report when through dozens of edits as different equities were represented. I did not have any meetings with Sheryl on the paper, but I can’t speak to whether she was in the loop with my higher-ups.
In the end, the difficult question of attribution was settled by us pointing to the DNI report instead of saying Russia or GRU directly. In my pre-briefs with members of Congress, I made it clear that we believed this action was GRU.
The story doesn\u2019t say you were told not to... it says you did so without approval and they tried to obfuscate what you found. Is that true?
— Sarah Frier (@sarahfrier) November 15, 2018
In the spring and summer of 2016, as reported by the Times, activity we traced to GRU was reported to the FBI. This was the standard model of interaction companies used for nation-state attacks against likely US targeted.
In the Spring of 2017, after a deep dive into the Fake News phenomena, the security team wanted to publish an update that covered what we had learned. At this point, we didn’t have any advertising content or the big IRA cluster, but we did know about the GRU model.
This report when through dozens of edits as different equities were represented. I did not have any meetings with Sheryl on the paper, but I can’t speak to whether she was in the loop with my higher-ups.
In the end, the difficult question of attribution was settled by us pointing to the DNI report instead of saying Russia or GRU directly. In my pre-briefs with members of Congress, I made it clear that we believed this action was GRU.
