IETF Logo Mail Archive

Re: [Jmap] Submission is not hard

"Adrien de Croy" <adrien@qbik.com> Fri, 21 April 2017 23:14 UTC

Return-Path: <adrien@qbik.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39B14128896 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 16:14:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mn9a8N0ceHaI for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 16:14:27 -0700 (PDT)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1032127071 for <jmap@ietf.org>; Fri, 21 Apr 2017 16:14:26 -0700 (PDT)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.0.5 (Build 5926)) with SMTP id <0001026438@smtp.qbik.com>; Sat, 22 Apr 2017 11:14:23 +1200
From: Adrien de Croy <adrien@qbik.com>
To: John R Levine <johnl@taugh.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
Date: Fri, 21 Apr 2017 23:14:23 +0000
Message-Id: <em915919ef-c7e7-46bf-9033-357547a1b063@bodybag>
In-Reply-To: <alpine.OSX.2.20.1704211854460.56587@ary.qy>
References: <BC098A22-2837-4316-822A-27232A896EF1@fugue.com> <20170421151636.28173.qmail@ary.lan> <em9926309f-c4d3-41e7-8016-dcbda8fcbd73@bodybag> <alpine.OSX.2.20.1704211843530.56587@ary.qy> <embbc99f95-a227-447d-9731-60bcb5a02ddf@bodybag> <alpine.OSX.2.20.1704211854460.56587@ary.qy>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/GZZfTmUqLfnAb3q84xa9q4OGzn0>
Subject: Re: [Jmap] Submission is not hard
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 23:14:29 -0000

If I had a mail client I would do it already.  I can only commit to 
doing it for the server side.

In general, I think any system which involves humans, where things 
happen which cause the system to require the human to wait for something 
should be designed in a way that allows for status updates to be given 
to the human in a timely fashion.

This is why I wrote the draft for status updates in http.

This is why I suggest we allow for status notifications in mail.

because when you send a message, you have to wait to find out what 
happened.  And sometimes it's important.

When people are forced to wait for things for too long without any 
feedback, they start doing things (like getting on the phone to see if 
the message got through).  Often these things are unnecessary and 
wasteful of resources.  More wasteful than a system that provided 
adequate feedback in the first place.

Designing protocols with this in mind allows implementors of these 
systems to treat the humans (their customers) politely.  Leaving 
feedback / notifications out of the protocols puts the implementers in a 
position where they are forced to treat their users badly / rudely.

Adrien


------ Original Message ------
From: "John R Levine" <johnl@taugh.com>
To: "Adrien de Croy" <adrien@qbik.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
Sent: 22/04/2017 10:55:18 AM
Subject: Re: [Jmap] Submission is not hard

>>It's only vapourware if nobody implements it.
>>MUA designers tend to be interested in things like usability.
>
>Well, sure.  We eargerly await your prototypes.
>
>Regards,
>John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>Please consider the environment before reading this e-mail. 
>https://jl.ly
>
>_______________________________________________
>Jmap mailing list
>Jmap@ietf.org
>https://www.ietf.org/mailman/listinfo/jmap

v2.23.0 | Report a Bug | By Email