Yeah this is a really interesting question. It's the point Moxie brings up when people ask why signal isn't federated or otherwise decentralized. You basically

Yeah this is a really interesting question. It's the point Moxie brings up when people ask why signal isn't federated or otherwise decentralized. You basically have to solve multi-stakeholder collaboration. You want projects/companies to have the flexibility to add features, but you also don't want subtle incompatibilities to plague the system like "I can't see the picture on your tweet because you use the MediaEmbeds schema and I used the EmbeddedMedias schema." This is the topic I get nerd-sniped about a lot. There are a couple of ideas I want to try. One is machine-readable schemas that get published on the network. That's kind of conceptually similar to what smart contracts represent; there's a program that essentially "lives on the network" and which people can build against, reference by hash/pubkey, etc. It's a coordination primitive. I like how intuitive that feels. Another idea is schema negotiation, essentially metadata that says "this post uses MediaEmbeds, here's what needs to happen if you don't support it." A third idea is using graphs of fact-triples like RDF, which gives you a lot of flexibility but I worry may not solve coordination well enough. And a fourth idea is to use lenses like Ink and Switch talked about with Project Cambria. I think this is a really interesting topic, I hope we find some good answers.