Musk Buys Twitter: Platform Risk for Devs

Archive note: this is a backdated post, written years later while rebuilding this site. It’s dated to the moment it covers, but the hindsight is real.

After six months of will-he-won’t-he — an unsolicited offer, a public attempt to back out, a lawsuit compelling the deal — Elon Musk closed his $44 billion acquisition of Twitter on October 27, walked into HQ carrying a literal sink (“let that sink in”), and fired the executive team by sundown. The richest man alive now personally owns the world’s argument clearinghouse.

The takes write themselves and I’ll skip mine. What interests me is the structural event: overnight, every developer, business, journalist, and community that built on Twitter got a new landlord with publicly mercurial intentions. This is the cleanest case study in platform risk since Robinhood greyed out the buy button — and this time it’s the platform devs themselves built on.

The risk inventory

Count the parties exposed, in rough order of leverage:

API developers. Twitter’s third-party ecosystem — clients, bots, research tools, every “login with Twitter” button — exists at the API’s pleasure. Twitter has burned developers before (the v1.1 token-limit massacre of 2012 is a generational memory), and the new owner has both stated opinions about bots and an urgent need for revenue. If your product’s core loop includes a Twitter API call, your roadmap now includes a stranger’s mood.
Businesses whose audience lives there. Years of follower-building are an asset on Twitter’s books, not yours. The PH version of this lesson already ran once: the day Facebook disappeared took every page-based business with it for six hours. Ownership changes are slower outages with the same shape.
Communities and norms. Moderation policy is now, definitionally, whatever one person decides. Whether you expect improvement or catastrophe, the variance alone is the point — rules that can swing wildly are not rules, they’re weather.
The employees — but that’s a labor story unfolding on its own grim schedule, by all reports.

The defensive playbook

None of this is new advice, but acquisitions are when people finally take it:

Own your root presence. A domain you control, a site you publish on, an email list you can export. Social platforms are distribution, not home. (Posts like this one live at a URL no billionaire can buy on a whim — the entire argument for the personal website, vintage 2018 edition.)
Treat platform APIs as vendors, not infrastructure. Abstract the integration, monitor the deprecation notices, and have a written answer to “what if this API triples in price or dies Tuesday?” If the answer is “we die Wednesday,” that’s a finding.
Export regularly. Followers, content, archives — whatever the platform lets you take, take on a schedule. Data you can’t export is data you’re renting.
Watch the exits being built. Interest in federated alternatives — Mastodon and the broader ActivityPub world — has visibly spiked this week. Protocols-over-platforms is the structural fix: nobody can acquire RSS, which is precisely why this blog still has a feed.

The honest uncertainty

It’s day three. Maybe Twitter becomes better; maybe it becomes a smoking crater; the verified-checkmark plans being floated this week suggest we’ll find out at speed. I genuinely don’t know — and that’s the post. You shouldn’t have to know. An architecture where one acquisition can obsolete your product, audience, or community was always the vulnerability; the sink was just the reminder.

Renew your domain. Back up your follower list. And maybe dust off that blog.