Yes! This is the approach we're taking at https://braid.org https://braid.org -- extending HTTP itself into a decentralized synchronization protocol, so that a

Yes! This is the approach we're taking at https://braid.org https://braid.org -- extending HTTP itself into a decentralized synchronization protocol, so that any application built on top of it can be decentralized. Specifically, you can divide any application's protocol into two parts: - A data synchronization protocol - A data schema on top of that protocol Existing decentralized social protocols (like ActivityPub) encode both the data synchronization and a set of data schemas into a single protocol. ActivityPub lets you broadcast a bunch of tweets to a bunch of subscribers, but doesn't work very well for other features, like decentralized moderation. It's hard to add new features to these protocols because you have to go through the entire consensus process for each feature. This makes it hard to improve ActivityPub to add new features, such as decentralized moderation. Instead, Braid tackles just the synchronization, with a very simple extension to HTTP, so that different applications just boil down to different data schemas. These data schemas are very easy to translate between (manually, or automatically), which means that any individual application can innovate to its heart's content on new features, and any other application can easily synchronize with any of those new features, to interoperate, and grow a decentralized web of state + features. As an example, here's a prototype for decentralized moderation that we are building on braid: https://peeryview.org https://peeryview.org. See https://peeryview.org/about https://peeryview.org/about for a description.