API Evangelist Conversations

Kin Lane

Mapping the technical details of API operations to the human conversation.

  1. Sep 1

    API Evangelist Conversation with Lukasz Gornicki on What the Linux Foundation Actually Gave AsyncAPI, Why a Sponsor Walked Away Because of It, and Open Source Europe as a Home for a Specification

    Lukasz Gornicki spent years as executive director of AsyncAPI, which means he has already run the experiment everyone else is still theorizing about — what a foundation actually does for a specification once the announcement is over. He is now part-time, and hoping to go full-time, at Open Source Europe, a Belgian association built as a European alternative to the US-based Open Source Collective. I brought him the question I have been carrying since I forked Spectral: where should a rule-set specification live. What I got back was not a recommendation, it was a set of distinctions. The Linux Foundation gave AsyncAPI intellectual property and trademark protection and very little else — protection that turns out to mean a free letter from a lawyer, after which you need a litigation budget you do not have. It funds no engineering work, which is why Open Source Collective had to exist alongside it. And one sponsor declined to renew specifically because AsyncAPI was part of the Linux Foundation. Lukasz walks the other options too — why Apache is the only foundation that will actually enforce a governance model on you, and the price it charges in your project's name; why Eclipse left the US for Canada; and what Open Source Europe can and cannot do today. Underneath all of it is the question he says has to come first, and that nobody in this conversation has answered yet: ask the people who would fund this what they actually care about, because open governance needs no foundation at all. Correction, added after recording: in this conversation I say the German government reached out and that Germany is committed. That overstates it — Germany has made no commitment. The Netherlands is the only government with a published, documented dependency on this format, in the developer.overheid.nl post of 31 July 2026. Conversations with Italy are ongoing and nothing is committed there either.

  2. Aug 27

    API Evangelist Conversation with Danny Preussler on Reopening the SoundCloud API, the Agent That Scraped Its Way to a Token, and Writing Documentation for Machines

    Danny Preussler is an engineer on the API team at SoundCloud in Berlin, and he came up entirely on the client side — BlackBerry apps, then Android, then eBay, Groupon, and Viacom before landing at SoundCloud seven years ago. This is a conversation about one of the great API origin stories and one of the great API closures. SoundCloud shipped a public API in 2008, one year after the company started, and literally built its own product on the same API everyone else could use — the Android lead got hired because he wrote a better SoundCloud app on the public API than SoundCloud had. Then the major label content arrived, the scrapers and downloaders arrived, a hundred thousand new apps registered in 2016 alone, and in 2017 the program closed for what was supposed to be a temporary pause. Danny walks through the soft reopening of the last two years, the Tyk gateway that made it possible to reopen at all, and the moment that changed everything: they handed an agent the task of creating a SoundCloud app, it could not find a token, so it scraped the website for one and quietly rewired itself from the public API to the internal API. We also get into why deprecated endpoints started spiking after five years of silence, why their ticket volume went up because of a stale doc page, and where Danny lands on MCP when he turns the questions back on me.

About

Mapping the technical details of API operations to the human conversation.