Aggressive Interoperability

Right now, everyone in this space is clamoring for The One Interoperable System to Rule Them All. If you're really in this field, you know that the current problems are all about unifying proxies from different projects under a single technology, and avoiding duplication of work -- both in building tech and building userbases.

As we've always suspected, our big opportunity here is in interoperability.

The problem: in trying to rush BU to market for use with Lantern, we've incrementally jeopardized our interoperability.

We need to pause, survey our current state of interoperability, back out our bad decisions, and start leading -- in our comms and the presentation of the project -- with interoperability.

We need to make a list of all the projects we'd like BU to interoperate with -- Tor, Signal, and what else?

Maybe we can organize hackathons focused on making BU work as a transport for these potential partners, and then use the solutions to identify places where we're not providing the right interfaces and such?

The issue names no files, tests, or entry points. Start by surveying BU's current interfaces and existing integrations with Lantern, Tor, and Signal; done would require an agreed interoperability inventory and a plan for addressing incompatible decisions.