An attempt at discussing ocaps via the car key metaphor

I don't think it's working
This commit is contained in:
Christopher Lemmer Webber 2019-07-21 09:51:22 -04:00
parent 72e8065d72
commit 72edb72241
No known key found for this signature in database
GPG Key ID: 4BC025925FF8F4D3

View File

@ -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