Open means it works with everything else: Chris Riley on what openness requires
Before Chris Riley and I got to the FTC, he told me where his thinking on interoperability comes from. He spent years at Mozilla, an open source organization that champions net neutrality, open standards and open code, and openness became the value he built his career in tech policy around. So I asked him what open actually means, since the word gets used for almost anything.
In the context of interoperability it means the idea that you can just sit down and build something and that it will work, and then it will work with the rest of the ecosystem where it needs to, and that there won't be gatekeepers, whether they're network operators, platform operators, operating system vendors or others, who will put artificial roadblocks in the way of your ability as a new entrant into this market to do something cool and have success with it.
Turning that principle into engineering is hard, he said. Turning it into competition law is harder.
The cheapest kind of interoperability is a standard. Email and the internet protocol are relatively fixed, everybody agrees to use them, and the cost of switching or competing is about as low as it can technically be. But not everything needs a standard, and most of the internet in 2020 does not run on one. It runs on large platforms, Facebook, YouTube, Twitter, that publish APIs offering a one-way kind of interoperability. You can use some other service to get your data off the platform, or put data onto it.
His favorite example is TweetDeck, which he still uses. It started as independent software that let you read and write your Twitter feed and work with the people you follow in a far more powerful way than Twitter's own site. That is APIs at work when they are done right, he said, and a glimpse of what the internet could be if platforms offered more of them and third parties could build on top. The heady, open-ended possibility of combining services and innovating downstream from them is what made the internet magical in the first place.
TweetDeck also shows the catch. Twitter bought it in 2011, and the next year it capped how many users any third-party Twitter client could have. A standard belongs to nobody. An API belongs to the platform that publishes it, and it can be narrowed whenever the platform's interests change.
Chris does not think the market will fix that on its own. The incentive is to run the whole vertical stack of software, services and applications. That has real benefits: one company running every piece can deliver a consistent, polished experience. But the company also wants to keep you there, using all of its services, tied together. He has criticized Facebook in particular for recreating a walled garden on the modern internet. I said it sounded like AOL. He agreed, with echoes of the era before the open internet.
So he thinks the law has to change, which sent him back to antitrust textbooks he had not opened since law school fifteen years ago. American case law was built to understand pre-internet markets and supply chains, and fitting interoperability into it is a square peg in a round hole.
That is the part I keep returning to. A standard nobody owns is the strongest form of openness and the hardest to get. An API is the form we actually have, and it is openness on the platform's terms. Most of the policy fight ahead is about whether those terms can be held to a standard by someone other than the platform. Chris's answer to who that someone should be was the other half of our conversation: an FTC with engineers who can read an API.
From Lincoln Shorts, the interview series I hosted for Lincoln Network, recorded 30 September 2020.
