--
You received this message because you are subscribed to the Google Groups "cap-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cap-talk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/87blfyh2xz.fsf%40dustycloud.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CANpA1Z05yJ%2BPTZAfWQyv7_vfGmBk6BP0C%2Bj8Z%2BEOLh2PO1-y-Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CAMJVQOUCtAkunCi2hiFBsA1cZdGeh%3DqCh-dhVauyhZ7Li4vEjg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/61dabded-627e-47ee-b36e-f694c70d724fn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/61dabded-627e-47ee-b36e-f694c70d724fn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/61dabded-627e-47ee-b36e-f694c70d724fn%40googlegroups.com.
(/brokenrecord I'd continue to try to split hairs and urge people to not use e.g. keys for cars or other large hard to copy objects in such metaphors as I feel it misses the very key important fundamental issue with digital info. So maybe more James Bond style "somebody uses their phone to take a picture of your documents" scenario that is straddling the physical-digital spectrum.)
--
You received this message because you are subscribed to the Google Groups "cap-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cap-talk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CAJ7XQb6Wp-pv%3DLTXuM0Pmn6G68ugh0ba9nFrr%3DuB7ZojVZ_oEA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CACTLOFqc8p0PHvOtMWzRwpLxn9_KHOHKTPY_Mx2zKn0Cb-25zw%40mail.gmail.com.
> > The key metaphor was always problematic. Maybe the answer is that a capability is a capability and we have to note the billet and explain it.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CACTLOFpW%3DteXieLhi%2BTMVzTObUhpC9mn1QfzSUdArdXh3DuKnA%40mail.gmail.com.
I know of very few keys that
have an identifier which lets you locate the associated lock,
something most (all?) capabilities have.
"Oh... this is just ordinary programming, taken seriously!"