[cap-talk] Blue sky: I have a dream, cap-share

[John Carlson]

I'm not sure if you want to share the file, or the editing window.
These would be two different things, possibly enabled by the
same software.

Have you played with Remote Assistance, VNC, and others?
Obviously, these give much more power than just one file.

I have multiuser editing software that I would like to add
persistence to.

Were you thinking about sending commands across the
system to update the document, or just sending the whole
document back and forth.

Confluence offers pretty good source control functions.
It even tells you when someone else is editing the page.
What it doesn't do is capabilties.

John
On Dec 13, 2006, at 6:20 PM, Jed Donnelley wrote:

> cap-talk,
>
> I have a dream.  If you've been reading this list long, that won't
> surprise you.  Let me describe the sort of embodiment that I
> think would add significant value to our Internet interactions,
> just to get a reaction from others.
>
> Suppose (infrastructure) people all have personal computers
> that stay on and on the network.  Suppose everybody has
> a private key identity (blue sky with me for a bit).  I really
> think these are absolute requirements, but just for this
> thought...
>
> Now I download the famous "cap-share" software.  Once I
> install it, it comes up when my system comes up.  It ties
> into a network (I think of it a bit like the bit-torrent network)
> so other clients can find it (more infrastructure to skip over
> in the blue sky phase).
>
> Now here's the simple function.  Suppose I have a file
> (let's do this for files first - if it works for files I expect it
> will work for anything else, e.g. printers, directories, etc.)
> that I want to share with MarkM (e.g. as I did, a Word document).
> I tell my cap-share software:
>
> make cap <path1> MarkM
>
> to make a capability to this file on <path1> on my system for MarkM.
> I get back a <blob> of text.  I send it to MarkM in an email.  MarkM
> runs his instance of cap-share and says something like
>
> make file <blob> <path2>
>
> After doing so there is what appears to be a file at <path2> on
> his system.  He runs Word on <path2> and, like magic, we're sharing.
> I change the file, he changes the file, we both see the same thing.
> Sure it would be nice to have a "go back" function (source control).
> It would be great to have responsibility tracking and revocation
> (seems easy to me).  Logging would be good of course.   I think
> of such things as niceties.  It is the fundamental and basic sharing
> of access that I believe is most needed.
>
> MarkM decides he wants to delegate (e.g. he has a tech writer
> that volunteered to look at the English), great.  He just delegates
> (makes up a new capability and sends it) to his tech writer and
> off we go.  My server honors it and logs any accesses.
>
> I'd like to hear what others think about such a sharing mechanism.
>
> --Jed http://www.webstart.com/jed/
>
>
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk