Medium acquires Superfeedr, maker of an API for generating and pushing RSS feeds
The web is very different from what it was 8 years ago. We've said it several times: publishing and consuming content are new frontiers for most of the web giants like Facebook, Google or Apple.
Context & Ripple Effects
Medium has been assembling its own publishing stack piece by piece: an October 2015 release added a publishing API and custom domains, and April's Medium for Publishers brought branding tools that pulled over a dozen independent sites like The Awl onto the platform.
Superfeedr fills the distribution gap in that stack — its API generates and pushes RSS feeds, the pipe that carries Medium-hosted content out to readers and aggregators. The deal lands amid the debate over whether Facebook hosting news commodifies publishers; owning the feed layer is Medium's answer to keeping distribution in-house.
First-order effects
- Superfeedr's feed-generation API becomes Medium infrastructure, so publishers who migrated under Medium for Publishers get RSS distribution handled by the platform rather than stitching it together themselves.
- Medium's engineering team absorbs Superfeedr's feed-pushing capability directly, extending the platform surface opened by the 2015 publishing API.
Second-order effects
- Rival platforms courting publishers — Facebook among them, per the argument that hosted news doesn't commodify great content — now face a competitor that bundles creation, branding, and outbound syndication in one contract.
- Other specialist feed and embedding vendors become obvious acquisition targets or partners for platforms racing to own the same plumbing; Medium's later purchase of Embedly confirms exactly that pattern.
Third-order effects
- If the absorption pattern holds — Superfeedr, then Embedly — independent content-infrastructure APIs get consolidated into a handful of large platforms, raising the bar for publishers who want open-web distribution without allying with one.
- Control of the feed layer positions Medium to keep readers inside its ecosystem, consistent with the reading-list feature later found in its app code — platform ownership of both ingestion and consumption of web content.
The trend: Content platforms are buying up the specialist APIs that move and embed web content, converting open-web plumbing into proprietary platform infrastructure.