Why Open?
summary
Argues that APIs break company borders, turning organizations from closed organisms into interoperating assemblages where control shifts and emergent behavior matters. Uses Twitter as a concrete case: API rule changes push away third‑party clients, provoke a two‑week open microblogging reimplementation that gains users briefly then collapses, and teach the market to avoid sharecropping. Recommends embracing openness, using rate limit for technical scaling but not as a business lock‑in tactic.
AI-written summary · about
chapters (4)
related talks
31mHow Open is Your API Future?
05mOpen Source and Inner Source for APIs
43mAre Open APIs Enough to Prevent Lock-in?
46mIt Was Never About Innovation
53mKeynote - Embracing Openness as a Competitive Advantage
11mThe Future of Open Ecosystem Programs: Bridging Communities, Innovation, and Collaboration
44mTranslating Open Source Value to the Cloud
28mThe New API Stack