← Back to Posts

Antitrust needs engineers who can read an API: Chris Riley on the FTC

Sean Roberts•September 30, 2020•4 min read

I tried to get Section 230 out of the way first. Every conversation about reining in big tech this year seems to end up there, and a week ago the Justice Department sent Congress its own draft rewrite of the law. I think it is a rabbit hole. The question I care about is whether a new business can start, grow and compete next to the biggest platforms. Chris Riley, formerly of Mozilla's public policy team, has written about how an agency like the FTC could be adapted to watch over exactly that, so I asked him where he would start.

He agreed with me only up to a point. The law has not caught up with the technology, but the mismatch runs deeper than speed. For years the platforms said technology was neutral, that they just built the thing and the users were responsible for what happened on it. That, he said, was kind of bunk. By 2020 the platforms accept that they carry some responsibility. The hard question is how to encourage it without writing rules that push the big companies to do the right thing and squash every small company at the same time. The potential for abuse, including against free speech, is real, and the laws we have were written for other eras: Section 230 for the age of Prodigy, antitrust for the oil and steel trusts and the old AT&T.

I asked whether the real problem is that Congress has stopped legislating and leaves agencies to do the heavy lifting. He thinks some of that is unavoidable, since even the best legislature would struggle to keep up, but he pointed to the ACCESS Act, introduced last year by Senators Warner, Hawley and Blumenthal, as the right kind of principle. And he does not want to throw out antitrust.

The principles of antitrust law are very sound, right? The principles of encouraging market entry, of not necessarily punishing big for the sake of being big, but really trying to identify the anti-competitive acts, really putting the emphasis on consumers and on consumer welfare. I think those principles are still fine.

The FTC, in his view, is a great agency with a good competition bureau. What it needs is more guidance and a great deal more in the way of resources, because the work is case by case and technical. APIs are his favorite illustration. A platform publishes an interface, ostensibly to let other software work with it. How do you know whether it strikes the right balance in practice? Whether the security and privacy limits on it are necessary or go too far? Whether it is calibrated to prevent another Cambridge Analytica, which happened because Facebook's original Graph API was, as he put it, frankly not well designed and gave out too much?

The only way to imagine this working out well in practice in my mind is to have an agency like the FTC with a bunch of computer scientists on staff and with a really open, properly protected dialogue with Facebook and with future companies to understand the API, to understand the business reasons for why the API was designed the way it does.

The FTC has moved in this direction. Last year its competition bureau turned a technology task force into a permanent Technology Enforcement Division, built around attorneys who know technology markets. Riley is asking for something different in kind: engineers reading the interfaces themselves, in an ongoing conversation with the company rather than a lawsuit. He admitted that model is hard and not well tested. He suggested lessons from financial regulation, where supervisors work hands-on with banks, and from the United Kingdom's open banking program, which required the largest banks to let customers share their account data with other firms through standard interfaces.

From where I sit, this is the right diagnosis. An API is a business decision written down in a form a computer can read. Look at which fields are exposed, which calls are rate-limited and which permissions never get granted, and you can see what a company wants other developers to be able to do. An enforcer who can read that can tell a security limit from a moat. One who cannot is left with press releases and depositions.

Chris called the conversation super wonky. I told him that was the idea: explain the wonky parts well enough that we can argue about facts instead of assumptions.

From Lincoln Shorts, the interview series I hosted for Lincoln Network, recorded 30 September 2020.

Share this post