3 ms·

For modifiable content, more useful than UUIDs would be (chosen-name, content-hash) tuples that are then signed by the publishing crypto-identity. The chosen-

by gojomo 12y ago

For modifiable content, more useful than UUIDs would be (chosen-name, content-hash) tuples that are then signed by the publishing crypto-identity. The chosen-name can be a UUID, but doesn't have to be something so semantically-opaque. It's more likely to be a tree-namespace like traditional domain-centric URLs. The publishers-key replaces the role of the domain-name as the 'authority' portion of the URL. (Once upon a time, I suggested 'kau:' – for Keyed AUthority – as a URI-scheme for such URLs in a location/protocol-oblivious web: http://zgp.org/pipermail/p2p-hackers/2002-July/000719.html http://zgp.org/pipermail/p2p-hackers/2002-July/000719.html )

rakoo 12y ago
Interestingly camlistore does that: - First you create a "random" blob that has an identity (called a permanode), that you sign with your private key. It acts as an "anchor" you can link to. - Then you sign a piece of json that references the permanode and the content you wish; it effectively means "I, owner of key XXX, claim that permanode called 12345 now references value ABCD". - To get the content of a permanode, you search all modifications and merge them to obtain the final value