Re: [Last-Call] New Version Notification for draft-crocker-inreply-react-07.txt

Barry Leiba <barryleiba@computer.org> Sat, 27 February 2021 03:47 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E2F3A0CA7 for <last-call@ietfa.amsl.com>; Fri, 26 Feb 2021 19:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 IFwPxhRCNK05 for <last-call@ietfa.amsl.com>; Fri, 26 Feb 2021 19:47:19 -0800 (PST)
Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FD423A0CA2 for <last-call@ietf.org>; Fri, 26 Feb 2021 19:47:19 -0800 (PST)
Received: by mail-ed1-f45.google.com with SMTP id p1so8807040edy.2 for <last-call@ietf.org>; Fri, 26 Feb 2021 19:47:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EdAn6FqRqeiozX8MTI5txuokmRjeIhzPQTOgQfBvSNA=; b=IdMpt7yeNuDJ08hcSeYQmnfJqm3EqhpXqBmhYFAt4gi5UgoIprKkeMI9MJhGf1g2+s Cwpfq60mVmjFMhj0OgJijpMjRs3llnAwh7DBHUnNEKRieSCwMacJiYQgu8q59hYjOJio dRyEdHZ2i+5bzO7M7bAdeMmOtt3d13sagTFRpONt8mKj5FthCA7UjnYHlmnCng18Mtv8 76pCu2UJzKXi8ugXlHlPhjMqNdLmZUTJVHR41WkVOraY3welL8YNtzVyY/iBA7b+FePn z8zPPkoNcgd/zpxf4tIlyQm/JkpLiqdqYoc/ArtGhe7WR/SfaMa8y0E8tdQ5nzM52xMq apRw==
X-Gm-Message-State: AOAM532sjLUsMYDO0/CJqvRhLVJiu9SBBf0Ck9rNCoxTzLRHhXcA/MhN BZz7Gv1VKTasLjZx3emtBLxXr6+GKO4JQUbL2ao=
X-Google-Smtp-Source: ABdhPJyL6tNjJV9NtntgjORRU57BHUQCrrOETVPU+OzI7hOtItS2bd1deZvO6KolTsy8eCgZ6b9DBPYFRvSX35N/d+I=
X-Received: by 2002:a05:6402:2707:: with SMTP id y7mr6398892edd.5.1614397637767; Fri, 26 Feb 2021 19:47:17 -0800 (PST)
MIME-Version: 1.0
References: <20210227000746.583206EF7036@ary.qy> <1bf0f5b1-a7a8-8c9f-3d6a-6f29f57fdb37@bbiw.net> <aaa9869-a44f-d23c-a5d-4f9e9d6d6c75@taugh.com> <688c9a89-1d37-deb9-9a93-2a69f1a63f28@bbiw.net> <2da68d7e-5f5f-b4bd-3d14-e5be523b5de@taugh.com>
In-Reply-To: <2da68d7e-5f5f-b4bd-3d14-e5be523b5de@taugh.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 26 Feb 2021 22:47:06 -0500
Message-ID: <CAC4RtVDX0ycSx7pPZObEzLAJX8ja6U5siAog9o6w2HYyt9wkpA@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: Dave Crocker <dcrocker@bbiw.net>, last-call@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b9b68405bc493d60"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/fJue-k8RtKDrQGVaiDkVXRbcQyA>
Subject: Re: [Last-Call] New Version Notification for draft-crocker-inreply-react-07.txt
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2021 03:47:21 -0000

Two things here, speaking as he AD who agreed to sponsor what I thought
would be an uncontroversial Experimental document:

1. This is an Experimental draft defining a way to put an (or a few, and
maybe the problem is not keeping it to one) emoji symbol in a reply as a
reaction to the original message, with the idea that said emoji symbol
might be shown in a conveniently streamlined way in the UI.  Variations of
that, such as putting in arbitrary strings, might also be reasonable
experiments, but they’re not this one.  I agree with Dave when he says that
keeping it simpler is better.

2. My personal image of this, which does relate to existing practice, is
based on the iOS Message app.  If I get a text message from someone, I can
long-press the message and get a popup that offers me six symbols to react
with.  Those symbols are a heart, a thumb up, a thumb down, a “ha ha”, two
exclamation points, and a question mark.  Of course, I can compose a text
message in response that has anything else I want to say, including a whole
long string of emoji... but the “reaction” interface is quite simple and
easy.  And when someone sends, say, a heart reaction to me, it’s up to me
to decide whether that means, “What a great photo!”, or “I’m in love with
you!”, or “I’d really like to be your cardiologist.”

I do think that this might be useful, is a worthwhile experiment, won’t
cause any real damage to the email system, and should best be kept simpler,
rather than being made more complicated.

I think text suggestions that add clarification or make the extent of the
experiment clearer are quite reasonable.  But I’m puzzled by objections to
trying it out to see how well it works.

Barry

On Fri, Feb 26, 2021 at 8:40 PM John R Levine <johnl@taugh.com> wrote:

> >> On Fri, 26 Feb 2021, Dave Crocker wrote:
> >> I'd flip it around.  What reason do we have to believe that any
> particular
> >> restricted vocabulary that we might define would be useful to users we
> >> don't know and who may not even speak any language we speak?
> >
> > cf, the reference to established practice, which is distinguished from
> > free-form text, which is what you now seem to be proposing
>
> I see a rule allowing a string of emoji, which we've heard is problematic,
> and a base-emoji rule which has an unupported assertion that it's five
> emoji developed from existing practice, although I'm not aware of any
> existing application that uses that set.  Do you have a reference?  In the
> apps I use, the set of emoji responses differs from one device to the next
> and is invariably very large, hundreds at least.
>
> > (which is odd, > given what stage of processing this draft is in.)
>
> I agree that it was extremely premature to last call this draft.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly--
>
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call
>