Bootpages

The structure of this page: every node, what a consumer does with it, and which of them can be addressed.

digest

bp1-sha256:9d6c89789a23bc53f9bc694eb7cae4a9966774256904011a88cb7fbd6c1ae193

revision

1

tags

a, p

falls back on

nothing

1. pno id
   1. A store for public, permanent documents that other sites can treat as capability rather than as content to copy.
2. pno id
   1. A bootpage is not a web page. It describes an experience — what parts it has, what each one requires, where its data comes from, and what its author would prefer it to look like. It carries no code, no secrets, and no per-viewer state. A site that receives one decides what to do with it, for whoever is asking.
3. pno id
   1. The point is that you publish once, and every site consuming the page changes with it: no server code touched, nothing redeployed, no file shipped.
4. pno id
   1. Pages here are permanent. An address, once issued, is never reassigned — it is what consumers pin, embed and cite.
5. pno id
   1. ano id
      structuralhrefhttps://page.babb.tel/How-bootpages-works-and-why-08-06
      1. How this works, and why
6. pno id
   1. Served from a PowerBook G4.