Re: [Jmap] message copying and moving

["J.B. Nicholson" <[e-mail]>]

Ted Lemon wrote:
> I think this is right, and is the right way to document it.   Default
> behavior on the client should be link—it's unlikely that the user ever
> wants a copy when a link is possible.   The only use case for copy is
> when the mail client is showing two mail stores on separate servers, or
> in the rare case where the user _wants_ two copies that are treated
> differently.   (I'm curious if there is general agreement on this or if
> folks think I'm crazy, though!)
I could be misreading or misunderstanding what you've written but I think I 
don't agree because I can't remember the last time I used an MUA that let 
me choose to link an email via the MUA's UI.

I also cannot recall when I would have wanted a link as a default choice 
while, say, dragging and dropping an email from one folder to another. I 
would think the default behavior on GUI MUAs would be moving or copying 
with the other option available via holding down a dead key.

I also think moving and copying are far more straightforward and familiar 
actions to non-technical users.

Hence, I think linking functionality is interesting but unlikely to be used 
much in practice. Therefore I believe copying and moving should be clear in 
the protocol.

I do understand the attraction for mail server implementers and sysadmins 
to want to use linking as much as possible to save storage space.