A Conversation with Ryan Sarver
summary
Explains which APIs exist and why: REST for reading and writing, Search for keywords, real‑time streaming API and a streaming team of two, plus the tiny JavaScript Tweet button that installs with a single line of code and becomes one of the platform's most successful launches. Describes moving developers to OAuth for safer auth, deprecating old API versions to enable V2, the site rewritten mostly in JS so the site is a pure API consumer, and a media rollout with about 16 media partners.
AI-written summary · about
chapters (12)
- 0:00API fundamentals
- 1:06API types and audiences
- 2:10First-party clients changes
- 2:52OAuth authentication
- 3:33API deprecation balance
- 4:14Tweet button success
- 5:15New Twitter as API consumer
- 6:39Public APIs for Twitter
- 7:40Media embedding context
- 8:42Partnerships and oEmbed
- 9:23Media companies as partners
- 9:44API adoption challenges
related talks
20mBefore and after: Why did Sveriges Radio think we needed an open API
21mAPI's - a Part Of the Creative Pallet
43mAPIs Are the Backbone of Every Company
28mAsyncAPI Without the Technical Jargon
19mBeing the gentle giant: Supporting API users for the long haul
19mAPIs in the media industry: models and trends for 2019
26mAsk your Developer: the rise of the API company
22mRebuilding Twitter’s public API