I've finished writing part 1 of "OcapPub: Towards networks of consent", which is to say the "Conceptual Overview" section gitlab.com/spritely/ocapp
There's a lot there already, and we haven't even gotten to Part 2, the "How to Build It" section yet. I'll begin that tomorrow.
Conversation
Replying to
I'm interested in the social aspect of how do you get people to accept ocaps as a way to do things. People really seem to intuitively revolt against the idea of delegation (A person you grant a capability can then share it with others).
1
1
Replying to
True, though as pointed in the document (and by a document pointed to by the document), no system can prevent delegation, including ACLs. That's a myth.
However, we can add accountability to whoever we handed the capability to. We can also "politely request" no delegation.
1
1
Replying to
Yeah, I agree. It's just that many people seem to have this mental block where they can't understand this. I also wish it weren't so ingrained in many compliance/security standards that you must "prevent" any kind of unrestricted delegation.