Lanyrd.comHow we bootstrapped Lanyrd using Twitter’s social graph   Simon Willison @simonw
Lanyrd.com  Definitive database of professional events      and speakers
Lanyrd.com  Definitive database       Social event recommendation of professional events   Comprehensive speaker profiles   ...
Lanyrd.com             Demo
Lanyrd.comWhy does it work?•The right crowdsourcing incentives•Wiki-style shared ownership•The parts support the whole•Twi...
Lanyrd.comWhy Twitter?•It’s where the event discussion happens•Speakers promote their Twitter accounts•Follow beats Friend...
Lanyrd.comBootstrapping•Classic social software challenge•Our secret weapon: the speakers!•Twitter accounts are public ide...
Lanyrd.com        More demos
Lanyrd.com    Key Twitter APIs
Lanyrd.com    friends/ids.json   [43593, 19972629, 778518,   1249881, 70478255, 3829151,   350373, 12161, 13141, 751953,  ...
Lanyrd.com friendships/create
Lanyrd.com  users/search.json
Lanyrd.com    Under the hood
Lanyrd.com
Lanyrd.com  Secret weapon #1: Redis
Lanyrd.com   Secret weapon #2: Solr
Lanyrd.comRedis set intersection
Lanyrd.comCalendar•Pull user’s friends/ids.json•Cache for ten hours•Store in Redis•Solr search: attendees:(34722 OR 131231...
Lanyrd.com       Pros and cons
Lanyrd.comPros•One-click signup•Naturally viral•Instant personalisation•Pre-created profiles, ready to be claimed•APIs are ...
Lanyrd.comCons•One big, scary dependency•No namespace control•Hard to optimise, as no local graph copy•Some users follow/a...
Lanyrd.com    Permissions hell
Lanyrd.com               Tweet this: @lanyrd attending   #londonweb             lanyrd.com/adthp
Upcoming SlideShare
Loading in...5
×

How we bootstrapped Lanyrd using Twitter's social graph

3,106

Published on

A talk presented at the London Web meetup on 21st July 2011.

Published in: Technology, Business

How we bootstrapped Lanyrd using Twitter's social graph

  1. 1. Lanyrd.comHow we bootstrapped Lanyrd using Twitter’s social graph Simon Willison @simonw
  2. 2. Lanyrd.com Definitive database of professional events and speakers
  3. 3. Lanyrd.com Definitive database Social event recommendation of professional events Comprehensive speaker profiles and speakers Archive of slides, notes and video
  4. 4. Lanyrd.com Demo
  5. 5. Lanyrd.comWhy does it work?•The right crowdsourcing incentives•Wiki-style shared ownership•The parts support the whole•Twitter!
  6. 6. Lanyrd.comWhy Twitter?•It’s where the event discussion happens•Speakers promote their Twitter accounts•Follow beats Friend for recommendations•Culturally amenable to public profiles
  7. 7. Lanyrd.comBootstrapping•Classic social software challenge•Our secret weapon: the speakers!•Twitter accounts are public identifiers•(and speakers have lots of followers)•500 profiles before launching our beta
  8. 8. Lanyrd.com More demos
  9. 9. Lanyrd.com Key Twitter APIs
  10. 10. Lanyrd.com friends/ids.json [43593, 19972629, 778518, 1249881, 70478255, 3829151, 350373, 12161, 13141, 751953, 22785347, 2633711, 14835908, 143883, 14159138, 11963132, 14917418, 15732699, 756475, ...]
  11. 11. Lanyrd.com friendships/create
  12. 12. Lanyrd.com users/search.json
  13. 13. Lanyrd.com Under the hood
  14. 14. Lanyrd.com
  15. 15. Lanyrd.com Secret weapon #1: Redis
  16. 16. Lanyrd.com Secret weapon #2: Solr
  17. 17. Lanyrd.comRedis set intersection
  18. 18. Lanyrd.comCalendar•Pull user’s friends/ids.json•Cache for ten hours•Store in Redis•Solr search: attendees:(34722 OR 1312313 OR...
  19. 19. Lanyrd.com Pros and cons
  20. 20. Lanyrd.comPros•One-click signup•Naturally viral•Instant personalisation•Pre-created profiles, ready to be claimed•APIs are pleasant to work with
  21. 21. Lanyrd.comCons•One big, scary dependency•No namespace control•Hard to optimise, as no local graph copy•Some users follow/are-followed a LOT•OAuth permissions...
  22. 22. Lanyrd.com Permissions hell
  23. 23. Lanyrd.com Tweet this: @lanyrd attending #londonweb lanyrd.com/adthp
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×