Re: Joins on capabilities that have passed through different membranes

On 2016-01-05 21:01, Kenton Varda wrote:
> On Tue, Jan 5, 2016 at 11:14 AM, Alan Karp <[email protected]>
> wrote:
>> Marc Stiegler came up with a clever UI affordance to make all this
>> clear.  If Ihab views the document with Kenton's capability, Ihab
>> sees a ro view.  If Ihab opens it with his own, he sees a rw view.
>> In either case, he see the same document, which reduces any possible
>> confusion.  Since Ihab does have write permission, his UI has an
>> Edit button (actually a tab in Stiegler's UI).
> 
> I really doubt that a user would understand that landing on the
> read-only view implies that the sender only had read access, if an
> edit button or tab is readily visible and is normally part of the UI.
> The user would merely think: "Huh, why am I on the read-only view?
> I'll switch to edit mode so I can make the requested edit."
> 

Perfect, you could offer a drop down right there so the user is asked to
designate the cap:

   Document is currently opened with read only privileges as supplied by 
Bob.
   Re-opening the document in rw mode requires the use of authority 
obtained
   from other sources. please pick the source of authority you want to 
use:

            |Carol  |V|                   |Edit|
            |Dave   |
            |Eileen |