← Back to Posts

Who decides what a messaging baseline includes: Chris Riley on co-regulation

Sean Roberts•September 30, 2020•4 min read

After our conversation about the FTC, I gave Chris Riley a longer proposal. The business moves too fast for an agency to manage alone, so what if an open source foundation worked alongside a regulator like the FTC to define the baseline API functions the big platforms must offer, so small companies could plug in and compete?

He liked the idea, and then took a step back to the problem underneath it: enforcement. His example was the GDPR, which he celebrates. It was a turning point in how laws about the internet get written, and it changed the global conversation about privacy for the better. But its enforcement model is, as he put it, a little bit broken. The privacy activists are not happy. The data protection authorities are under-resourced and stretched too thin. The companies are not happy either, because they do not get enough certainty about what is allowed.

When competition policy starts requiring interoperability, which he called a matter of when rather than if, the same question arrives. He does not want a government agency producing, as its output, what goes into an API. That is too hands-on and too slow, and it would not adapt. He would love to see agencies staffed with enough technologists, but politics makes that a low-probability bet. So what would an institution look like that builds trust over time, includes platforms large and small, established companies and startups, and works with the regulators too?

So particularly when you get to a space like messaging, how do you talk about what would need to be in a messaging baseline to enable greater interoperability than what we have in the messaging ecosystem today? How do you talk about encryption in that context, and how you can facilitate more security and more interoperability and not hold back messaging from doing interesting things? How do you fund the research that says you have to have sufficient emoji interchange between these services? I mean, yes, it's funny, but it's also real.

It is real. Text messages have crossed between carriers for years because the carriers agreed on how. The modern messaging apps agree on nothing with each other. Signal deliberately stays separate to protect its security model and its values. WhatsApp and Messenger succeed inside Facebook's walls, and last year Facebook said it would join its own messaging services together with end-to-end encryption, which is interoperability inside a single company. Chris also saw small cracks opening: Apple's latest iOS update lets people choose an email app and a browser that are not Apple's as their defaults.

Every one of those shifts raises the question of who decides what is enough. Today no trusted body exists to answer it. It would have to bring in Google, Facebook, Signal, startups and governments, carry enough governmental weight to get everyone to the table in good faith, and still avoid the familiar failures: pure self-regulation, which does not work, capture by the largest members, or paralysis by politics. He called it a co-regulatory approach, something we do not have today, and he was honest that he does not have all the answers.

Messaging is the right place to start because the hard part is visible. Interoperability that weakens end-to-end encryption would be worse than none. A baseline therefore has to be written by people who understand cryptography and how people actually use these apps, not only by lawyers. That argues for exactly the mixed body Chris described, and against leaving it to the largest platform or to a statute.

In a separate post I have written up the rest of our conversation, about what such a body would mean for a founder trying to get funded: a better AdWords that no one will fund.

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

Share this post