Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ty ahmad taylor presents building an os for content-solving the interest graph problem

989 views

Published on

  • Be the first to comment

  • Be the first to like this

Ty ahmad taylor presents building an os for content-solving the interest graph problem

  1. 1. Building an OS for contentSolving the interest graph problemTy Ahmad-Taylor | @tyahma | 28 Sept 12
  2. 2. Right now Real-time v.Lack of PopularSpecificity Benefit of APIs What’s missing Operating systems
  3. 3. Operating systems
  4. 4. Computers Content User User Applications Devices Operating system Pages Drivers IA Hardware Content source
  5. 5. OS conventions1.OSes are meant to be a more or less transparent foundational layer2.They should make your life easier3.They are customizable, but not personalizable4.They also organize your information ‣ Folders ‣ Applications ‣ Search ‣ Recency
  6. 6. Right now Lack of Specificity BenefitReal-time v. Popular Presentational Paradox of APIs What’s missing Operating systems
  7. 7. Real-time
  8. 8. Popular
  9. 9. Determing Interestingness, Popularity or Hotness Nope. Nope. Yep.Single gross measure. Single gross measure. Multivariate. Causation? Correlation? Variable weighting is the secret sauce.
  10. 10. Real-time versus hot1.Users are going to complain either way.2.Twitter made its decision ‣ They have left the door open, slightly for others that want to pursue popularity ‣ Klout ain’t it3.Blending the two remains unexplored
  11. 11. Right now Real-timeLack of Specificity Benefit of APIs What’s missing Operating systems
  12. 12. Do you know who has the best interest graph information,but isn’t using it for content?
  13. 13. Specificity
  14. 14. Right now Real-timeLack of Specificity Benefit of APIs What’s missing Operating systems
  15. 15. If you don’t use APIs internally
  16. 16. Traditional APIs
  17. 17. RSS can be the plumbing
  18. 18. APIs as a development philosophy User Front-end clients RESTful API Heavy lifting
  19. 19. Real-time Lack of Specificity What goes on right now in content What’s missingBenefit Operatingof APIs systems
  20. 20. Traditional
  21. 21. Plucky upstarts
  22. 22. Plucky Traditional
  23. 23. People without kids in private school
  24. 24. Jamie xx fiend needs
  25. 25. The state of content today.1.Most producers are narrowly focused on their own content and narrowly approach their traditional business problem of reach and frequency2.Those that aren’t don’t think broadly enough about other’s content3.No one has solved the “real-time versus popular” conflict4.Almost everyone lacks specificity, or granularity.
  26. 26. Right now Real-timeLack of Specificity Benefit of APIs What’s missing and the opportunities Operating systems
  27. 27. Openness Your stuffOther people’s stuff Value to end-user
  28. 28. Specificity
  29. 29. Real-time versus Popular
  30. 30. Real-time versus Popular This is azure blue, not purple, for color-blind folks
  31. 31. Operating systems User User User Applications Devices PersonalizationOperating system Pages Distribution Drivers IA Classification Hardware Content source Content sources
  32. 32. The content OS business opportunity1.Taking a broad view of organizing content for users solves a customer problem of relevance.2.The interest graph has one-to-two success stories. There is room for plenty more.3.The link economy and the social economy are well-established, but unexploited for delivering customer value.4.Solve the OS problem for content.
  33. 33. People don’t care about publishers, they careabout quality and specificity. Solve this, please @tyahma

×