[Thread]: After Bill Gross' 2015 hostile takeover attempt, Twitter locked the API and limited third-party clients to 100K users until Dorsey's return
Twitter is important, but it's always been vulnerable as a company. When Twitter does something which upsets the community of users, it is often due to this vulnerability. Let me tell you a little known story about an earlier time a billionaire tried a hostile takeover of twitter
Context & Ripple Effects
@rabble's thread resurfaces a little-documented 2015 episode: after Bill Gross mounted a hostile takeover attempt, Twitter responded by locking down its API and capping third-party clients at 100K users each — restrictions that held until Jack Dorsey's return to leadership ended them. The thread lands amid a long arc of coverage about Twitter squeezing its developer ecosystem, from ending legacy API support used by apps like Tweetbot in 2018 to killing its native Mac app twice while starving third-party clients.
The through-line matters because the same vulnerability keeps surfacing: the 2020 hack fed critics who questioned Twitter's engineering and management, and Vanity Fair's account of the company since Dorsey's return catalogued growth stalls and churn. A founder-era defensive move against a billionaire raider reads differently now that platform control over API access has become Twitter's recurring lever.
First-order effects
- Third-party client developers are the named losers in the story: the 100K-user cap froze their growth for years, and the ecosystem never recovered the ground it lost before Dorsey lifted the restrictions.
- For Twitter itself, the lockdown was an anti-takeover defense — trading developer goodwill for control of the surface a raider could exploit.
Second-order effects
- The precedent hardened into policy: once the API was treated as a chokepoint during the Gross scare, later moves like the 2018 legacy-API shutdown could be framed as 'technical and business constraints' rather than reversals.
- Developers learned the platform relationship was conditional, pushing client innovation off-Twitter and leaving Twitter's own apps as the default experience by default of attrition.
Third-order effects
- If the pattern holds, API access functions as a governance tool: whoever controls the keys controls both raiders and rivals, making platform openness a board-level decision rather than a developer-relations one.
- The structural risk is that a company repeatedly described as vulnerable — engineering, management, financials — leans harder on access control as its moat, at the cost of the influential users earlier coverage warned it was ostracizing.
The trend: Twitter's history shows API access shifting from open infrastructure to a defensive and commercial lever, with each crisis — takeover scares, hacks, growth stalls — tightening the company's grip on its own edges.