2 ms·

Braid and Statebus, https://stateb.us/what https://stateb.us/what > Every piece of state has a state:// URL. You can re-use another site's state as easily as l

Braid and Statebus, https://stateb.us/what https://stateb.us/what > Every piece of state has a state:// URL. You can re-use another site's state as easily as linking to a page with today's web. Websites can build on top of one another, and collaboratively outcompete today's centralized monopolies. If multiple businessses are cooperating to process state owned by multiple websites, how does Statebus envision the encapsulation of state for {user, device, app, feature, business}? Could some state be opaque/encrypted? What's the best place to learn more about the use cases below, https://stateb.us/why https://stateb.us/why Built-in offline mode Collaborative editing by default Website internal state is opened Make a new user interface Implement a blockchain on top of the web Enables better Email protocol: decentralized, simpler, realtime, spam-free, encrypted Improves source control: Source code becomes state—replaces git with the web protocol itself Any user can edit source for any website, and have their own version Editable, brancheable, forkable inline

snthpy 2y ago
That is wild! I'd also like to learn more about this. The language is a bit, idk superlative, but if it does what it says then it would be great.
- toomim 2y ago
  Yes, when I wrote that stateb.us/what page, my intent was to express the aspirational vision of statebus. It soon became clear that, in order for the vision to succeed, we needed the network protocol to become a widely-used standard. Thus began my Braid work. I started approaching the IETF to learn how to standardize State Synchronization in HTTP. I ran across this HN comment by JosephG [1] making a call to the same mission. I sent him an email, we decided to team up, and we went to dwebcamp in California and then IETF in Montreal together, and made a presentation to the HTTPWG proposing to extend HTTP into a state sync protocol. We got an enthusiastic reception, and I have been working on it ever since. The HTTP extension is getting into pretty good shape, and we're now manifesting the promises on that /what page. They aren't all production-ready (e.g. no blockchains built on statebus/braid yet), but they are coming true at a steady clip! [1] https://news.ycombinator.com/item?id=19816648 https://news.ycombinator.com/item?id=19816648

snthpy 2y ago

That is wild! I'd also like to learn more about this. The language is a bit, idk superlative, but if it does what it says then it would be great.

toomim 2y ago
Yes, when I wrote that stateb.us/what page, my intent was to express the aspirational vision of statebus. It soon became clear that, in order for the vision to succeed, we needed the network protocol to become a widely-used standard. Thus began my Braid work. I started approaching the IETF to learn how to standardize State Synchronization in HTTP. I ran across this HN comment by JosephG [1] making a call to the same mission. I sent him an email, we decided to team up, and we went to dwebcamp in California and then IETF in Montreal together, and made a presentation to the HTTPWG proposing to extend HTTP into a state sync protocol. We got an enthusiastic reception, and I have been working on it ever since. The HTTP extension is getting into pretty good shape, and we're now manifesting the promises on that /what page. They aren't all production-ready (e.g. no blockchains built on statebus/braid yet), but they are coming true at a steady clip! [1] https://news.ycombinator.com/item?id=19816648 https://news.ycombinator.com/item?id=19816648