Braid and Statebus, 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

  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