← Back to Posts

They pulled up the ladder: Cory Doctorow on competitive compatibility

Sean Roberts•August 21, 2020•3 min read

This is the first interview in a series I am starting at Lincoln Network. Three weeks ago the heads of Amazon, Apple, Google and Facebook spent five hours in front of the House antitrust subcommittee, and most of what has been written since is about breaking companies up. Cory Doctorow, special advisor to the Electronic Frontier Foundation, has spent the last year arguing for something more surgical, and I wanted it on the record before the fall gets loud. He calls it competitive compatibility. He used to call it adversarial interoperability, which is more accurate and harder to say.

The argument begins with history rather than law. Every big technology company got big by plugging into something that already existed without asking. When Apple feared being locked out of the office market, it did not beg Microsoft for a better Mac Office; it reverse engineered the file formats and shipped iWork. Microsoft grew on compatibility with IBM's PCs. Google started as a program that pretended to be a web browser, visited every page in the world and kept a copy. And then, in Cory's phrase, every one of them pulled up the ladder behind them. The thicket that would stop the next company doing the same thing is made of software patents, copyright, exotic claims like Oracle's that an API itself is copyrightable, and the anti-circumvention rule in the DMCA. Some of it was built by legislators and some of it was fashioned out of ambiguous law by companies with very deep pockets.

His proposal is a defense, not a mandate. He sketched three ways to get it. A statute: notwithstanding any other law, you may add a feature to an existing product without the manufacturer's permission, provided you break no other law and are acting on behalf of a real user rather than for your own gain. Procurement: the government simply refuses to buy software from anyone who will not promise to lay down those legal weapons against interoperators. Or a consent decree, where a company found to have behaved monopolistically makes it up partly by giving up the right to sue people who connect to it. The common thread is that judges would be asked an interesting question, did you do something otherwise lawful for a legitimate user, instead of the dull procedural one, did you infringe a patent.

I asked about network effects, which is where the break-up argument usually starts: once everyone is on Facebook, nobody can leave. Cory's answer was the MySpace story. When Facebook was small it wrote bots that logged into MySpace on behalf of its users, fetched their waiting messages and let them reply from Facebook. The walled garden became, as he put it, a corral the newcomer could raid. Network effects are real, but computers are general-purpose machines, and in tech the effect can be turned against the incumbent by anyone allowed to interoperate.

Since APIs are the fashionable remedy at the moment, I asked where they fit. His view was that an API is a floor, not a ceiling. The ACCESS Act idea, take the interfaces Facebook already uses between its own apps and open them to competitors, is sensible because those interfaces were built to ease interoperability rather than confound it. But a company forced to expose an API has every incentive to move the important parts of its product out of the API's reach until the remedy means nothing. A defense is the hedge. If the API stops touching what you need, you can hire engineers and go get it another way, and the company can hire engineers to stop you, but it cannot ask a court to stop you. Let the technologists do battle, he said, and keep the court out of it. He thinks that prospect alone would stay Facebook's hand, since a narrow managed API it understands is a smaller thorn than rivals scraping in the dark.

The best part was personal. Cory's grandmother was a Soviet refugee who left Leningrad and did not see or speak to her family for fifteen years, and plenty of people who could have left stayed because the price was that high. He moved from the United Kingdom to Los Angeles five years ago, calls his in-laws in Wales every weekend, and brought the appliances he liked, with transformers. Low switching costs did not make him leave; they made the choice less momentous, so the people who stay really want to stay and the people who go can go. That is what he wants for users of a platform: to leave the parts they hate without surrendering the parts they like.

Oracle's claim about APIs reaches the Supreme Court in October, so some of this will be decided whether or not Congress acts. I have spent a decade in open source, where interoperability is the whole point, and this is the first framing of the big tech problem I have heard that starts from how the industry actually grew. Watch the conversation above, and let me know what you think.

From Lincoln Shorts, the interview series I hosted for Lincoln Network, recorded 21 August 2020.

Share this post