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
A common misunderstanding about Agile and “Big Design Up Front”:
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
I\u2019d recommend that the devs participate directly in the research.
— Jared Spool (@jmspool) November 18, 2018
If the devs go into the first sprint with a thorough understanding of the user\u2019s problems, they are far more likely to solve it well.
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.