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
I think about this a lot, both in IT and civil infrastructure. It looks so trivial to “fix” from the outside. In fact, it is incredibly draining to do the entirely crushing work of real policy changes internally. It’s harder than drafting a blank page of how the world should be.
I’m at a sort of career crisis point. In my job before, three people could contain the entire complexity of a nation-wide company’s IT infrastructure in their head.
Once you move above that mark, it becomes exponentially, far and away beyond anything I dreamed, more difficult.
And I look at candidates and know-everything’s who think it’s all so easy. Or, people who think we could burn it down with no losses and start over.
God I wish I lived in that world of triviality. In moments, I find myself regretting leaving that place of self-directed autonomy.
For ten years I knew I could build something and see results that same day. Now I’m adjusting to building something in my mind in one day, and it taking a year to do the due-diligence and edge cases and documentation and familiarization and roll-out.
That’s the hard work. It’s not technical. It’s not becoming a rockstar to peers.
These people look at me and just see another self-important idiot in Security who thinks they understand the system others live. Who thinks “bad” designs were made for no reason.
Who wasn’t there.
The tragedy of revolutionaries is they design a utopia by a river but discover the impure city they razed was on stilts for a reason.
— SwiftOnSecurity (@SwiftOnSecurity) June 19, 2016
I’m at a sort of career crisis point. In my job before, three people could contain the entire complexity of a nation-wide company’s IT infrastructure in their head.
Once you move above that mark, it becomes exponentially, far and away beyond anything I dreamed, more difficult.
And I look at candidates and know-everything’s who think it’s all so easy. Or, people who think we could burn it down with no losses and start over.
God I wish I lived in that world of triviality. In moments, I find myself regretting leaving that place of self-directed autonomy.
For ten years I knew I could build something and see results that same day. Now I’m adjusting to building something in my mind in one day, and it taking a year to do the due-diligence and edge cases and documentation and familiarization and roll-out.
That’s the hard work. It’s not technical. It’s not becoming a rockstar to peers.
These people look at me and just see another self-important idiot in Security who thinks they understand the system others live. Who thinks “bad” designs were made for no reason.
Who wasn’t there.