Resource blobs:
tombstone, redirect
republish (exact version), republish (latest RID)
state/snapshot
changes (with optional state shortcut)
Agent is mounted at a path
Agent session is only writable by the agent key
MAIN question/decision?!
maybe: no floating children, only explicit children/rollups
Rollups only, explicit children: Children RIDs are defined in a map of child names. Or a prolly tree in large cases.
Placement/paths are explicit
Authority graph is entirely different from placement
Discussion: how are children established
option 1: children are resources who refer to their parent
option 2: parents define children by explicitly listing a Map of names to resources. Explicit children
there are tradeoffs for both. option 2 resembles the docs who define children with cards. option 1 is more like a "collection".
note: this relationship is not about permissions, it is about resolving the human-readable path and sidebar organization.
Discussion: how ResourceBlobs are allowed to refer to each-other
Can a ResourceBlob reference the previous version of the ReferenceBlob, like changes do? Can you mix and match state resources with change resources?
Important: Change resources should specify which CRDT program is used to handle the operations and compute the output state.
Eric says: as long as you have a deterministic way to resolve the previous version, your change can refer to it.
Thursday
How to resolve site.com/foo/bar or hm://AID/foo/bar/
determine the home document resource ID deterministically, somehow (easy)
read the home document
find the block id "foo"
if this is an embed block of another hm://r/RID, then resolve and load that doc
otherwise, zoom into that block
repeat for "bar"
Children of Collections do not have pretty URLs
The child resource explicitly names the parent through a new collectionId attribute
Arbitrary attributes are already indexed properly for fast searching
Why do we have permanodes
because we need a blob that specifies the owner (admin delegation)!
it must be retained therefore it should be empty, so deletion can be effective
and, what is a permanode? its a deterministic blob whose id we can use
revocations cannot be deleted
if you're the one distributing content, then you need to keep track of who you cannot send to
blob accounting
no more "give me this CID" api call. Only requests in the context of the resource
also need to provide read proof when writing a reference to data without uploading it
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime