From 72edb7224192e53cb67e8272a8bf1addd220b2da Mon Sep 17 00:00:00 2001 From: Christopher Lemmer Webber Date: Sun, 21 Jul 2019 09:51:22 -0400 Subject: [PATCH] An attempt at discussing ocaps via the car key metaphor I don't think it's working --- README.org | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/README.org b/README.org index fa41d8c..8487233 100644 --- a/README.org +++ b/README.org @@ -768,9 +768,29 @@ there is a lot we can make better. * How to build it ** Object capabilities (ocaps) -So far we've spoken +*** But really, what is the ocap paradigm, I'm confused + +So far we've spoken of object capabilities only at a high level. +Regrettably, I'm going to continue that for this subsection, but I +promise to get into the implementation details in the next section. +For the moment, I'm going to continue the high-level, long-spun +ocap introductory narrative of ocaps as car keys. + +We previously gave an example of object capabilities as being like a +car key: possessing them is what gives you access, rather than who you +are being what gives you access (the car doesn't need to scan your face; +if you have the key, you can drive). +Like a car key, you can also hand ocaps to other people and they can +use them (delegation). + +[... continue with valet and revocation car key metaphors here?] + +*** Ocaps as capability URLs + + + +*** Ocaps as bearcaps -# - *** Ocaps meet ActivityPub objects/actors