Re: [ietf-822] RFC 9078 Reaction: Indicating Summary Reaction to a Message

Rob Sayre <sayrer@gmail.com> Thu, 11 April 2024 16:27 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29CD5C14F6F6 for <ietf-822@ietfa.amsl.com>; Thu, 11 Apr 2024 09:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yt_kKd79jzj9 for <ietf-822@ietfa.amsl.com>; Thu, 11 Apr 2024 09:27:33 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 854BDC14F697 for <ietf-822@ietf.org>; Thu, 11 Apr 2024 09:27:33 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id 38308e7fff4ca-2d89346eb45so59080311fa.0 for <ietf-822@ietf.org>; Thu, 11 Apr 2024 09:27:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712852851; x=1713457651; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IAmeGsxXO3FatHPYyzjY7oYRvHxl9OCIZ/AmG9EaVNU=; b=bL3oiWi1yaimqSJ8XsYrXbNIdRhdgWzDnjYsrfPg4nbko2fk5GKdfPs+PhZOiPyhdQ PZ9F/5hd1GbbR2kietorqqh4/dGJ2xJQSxf0SkvXz6kp/aTxPDrJmYFzPZjdqdJ8r872 LyHrwBWf9dra6mIqoHoeC03eM05+LKAls/FUkF5pN7akYaa7VQ7dhlTyyd80i+RBMHly nmvwR4nDkwaPTwBGXmk3jFI/CcOT09npyEbr1fu7PY+jNrN/uEY14ONmXhcDVZJj7z0g vEFtMsIVhl14gTo/60yq7qbQ90zt075Y5zdg0tUPb2ZDXE2I2iO+7JGmoFBs+M5Nf+R5 zJeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712852851; x=1713457651; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IAmeGsxXO3FatHPYyzjY7oYRvHxl9OCIZ/AmG9EaVNU=; b=BWLy/DzaG8dDKcPEexuh770y5lDfyvfC2/yk4tB46dajoCdn6rDILM38maqaQK3fa3 9ZXEpCiIJdbcatv6X0iozHx1uQD/+4iXud5xs63S53ule+P1rLWsYmdr9CGKQYUfCSTm mmrBMgLh27aYp46Xe8kcRVA6d+i5+mU1nIg7sscwJh2xKAeJmATiTi+Iwo6mEYkvdl5S KtrMk7mpZQAIYUKFvHFpzwIFfWtYhTAx6ee+WTkCF6W211PYc2iDgxDRai4JdY2zWkHf HRX5GiF+g5/q32foETqN/gFKxBbMjRPpAWr2lyEVoJaKLeSc8vJooKFUmZJ2RfmLywjA wjQQ==
X-Gm-Message-State: AOJu0YwDSKxXbtVMFpXCFRzvtt6Ndyoi/v9Cxo/IL9AmTYIBq08hoCfg au/CYEAR19zX9Zf28pydKbOTshqZfESeWORQfKW/75YCe6XjNyyXYssxFUYhWPVeDXKe6rvp5hE ymHJu4cNS6YWWOl4Tt8QHuDqEt5nic+hMlyL8WQ==
X-Google-Smtp-Source: AGHT+IHbkShpcRt0TaJOZmvSI/M5pUIXVqrOo5ci0zDxI/Ugq6ls2uwNsS/rVQJYCL1nkk5M/TuRO1EAeJX9XGiYAEY=
X-Received: by 2002:a2e:bc29:0:b0:2d6:f793:3434 with SMTP id b41-20020a2ebc29000000b002d6f7933434mr176482ljf.2.1712852850706; Thu, 11 Apr 2024 09:27:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SxeXVvysoQ2ymOtkD0aV4YbcekOcXE2617s4Bmr0GBeNA@mail.gmail.com> <bb4e790d-4d39-4499-a99c-f51bd938c3f4@tana.it>
In-Reply-To: <bb4e790d-4d39-4499-a99c-f51bd938c3f4@tana.it>
From: Rob Sayre <sayrer@gmail.com>
Date: Thu, 11 Apr 2024 09:27:19 -0700
Message-ID: <CAChr6SyWKWYVj5=GdFayVGd4NStDxeg0tbj9HgN_vcPpAz3X8A@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: ietf-822@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b81aaf0615d4a12f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/v0hwAhe_LfwcEIVqSUXUc7LDM-E>
Subject: Re: [ietf-822] RFC 9078 Reaction: Indicating Summary Reaction to a Message
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 16:27:38 -0000

On Thu, Apr 11, 2024 at 4:57 AM Alessandro Vesely <vesely@tana.it> wrote:

> Yes, IMAP lets you just tag a message as, say, $reacted-star.  Then you
> must
> send a message to the original author, with the content as described in
> RFC
> 9078, {U+2B50} in case of ⭐.
>

OK, this is what I understood.


>
> The receiving server will presumably display the star near to the original
> message, that is in the Sent folder.  It may do so using IMAP keywords,
> but it
> should also count the number of reactions received, by whom, etcetera,
> perhaps
> storing those messages in a Reactions folder.  This is the challenging
> part.
>

I think it might be tough to fit this feature into IMAP folders, but JMAP <
https://jmap.io> seems flexible enough. There is already an existence
proof, since GMail has this feature.


>
> > The reason I say ⭐ and ♥️ need to be in the base emoji set is because
> these
> > are often the only option. Think of Twitter, Instagram, Mastodon. I think
> > the general approach in the draft is good.
>
>
> Although RFC 9078 exemplifies a set of base-emojis, an emoji-sequence is
> not
> limited by that.  You can use any *emoji sequence* defined in the
> referenced
> document[*].
>

 I understand that. The draft says:

"The rule base-emojis is provided as a simple, common list, or 'vocabulary'
of emojis. It was developed from some existing practice in social
networking and is intended for similar use."

Look at the Threads post that prompted my original email. The only
available reaction is ♥️, In ActivityPub/Mastodon, the "Like Activity" <
https://www.w3.org/TR/activitypub/#like-activity-inbox> is usually
represented as a ⭐,

Those two should be in there to meet the goal of that production. Another
choice here might be to follow the ActivityPub feature, allowing a reaction
of "like" without specifying an emoji character. That follows what you'll
find on the Facebook app, where clicking the button will send a 👍 (like),
but there are more options as well.

thanks,
Rob