unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: should notmuch handle or generate message responses (RFC 9078) (or, "why can't i 👍 an e-mail message?")
Date: Mon, 09 Aug 2021 23:06:52 +0300	[thread overview]
Message-ID: <m2a6lqz8kj.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87mtpv3763.fsf@fifthhorseman.net>

On Thu, Aug 05 2021, Daniel Kahn Gillmor wrote:

> Hi notmuch folks--
>
> RFC 9078 is an experimental draft "Reaction: Indicating Summary Reaction
> to a Message":
>
> https://www.rfc-editor.org/rfc/rfc9078.html
>
> In short form, this lets you "thumbs up" an e-mail message without
> sending a longer reply.
>
> Basically, it formalizes a way to respond to an e-mail with a single
> emoji sequence [0] by sending a message using the following headers:
>
>  - In-Reply-To: <some-message-id@example.com>
>  - Content-Type: text/plain; charset=utf-8
>  - Content-Disposition: reaction
>
>
> [0] https://www.unicode.org/reports/tr51/#def_emoji_sequence Note that
>     "emoji sequence" is *not* just "a series of emoji characters", but
>     rather it is a sequence of codepoints that is typically expected to
>     render as a single emoji, for example a raised hand with dark skin
>     tone is U+270B RAISED HAND followed by U+1F3FF EMOJI MODIFIER
>     FITZPATRICK TYPE-6
>
>
> Currently in Notmuch these responses would be rendered as simple, short
> one-line text replies.
>
> Some questions for notmuch to consider:
>
>  0) Should a message that conforms to this standard be treated
>     differently by notmuch than any other message?  If the answer is
>     "nope" then the rest of the questions don't make sense :P
>
>  1) does the database need any modification to store/report these things
>     as distinct responses?
>
>  2) should "notmuch new" treat the message differently upon ingestion?
>
>  3) should message threading information count the list of messages in
>     the thread differently depending on how many messages are
>     "response" messages?
>
>  4) How should a notmuch frontend decide when to clear the "unread" flag
>     from such a response message?
>
>  5) Should notmuch frontends facilitate creation of this kind of
>     response?
>
>  6) how should a frontend render the summaries of these responses?

I'd wait for "standards track" ;D (or de-facto usage it that takes too long...)

Tomi

>
> Interesting times,
>
>  --dkg

      parent reply	other threads:[~2021-08-09 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 21:36 should notmuch handle or generate message responses (RFC 9078) (or, "why can't i 👍 an e-mail message?") Daniel Kahn Gillmor
2021-08-06  7:35 ` Ralph Seichter
2021-08-06  9:34   ` Reto
2021-08-09 18:32   ` Daniel Kahn Gillmor
2021-08-10 16:59     ` Ralph Seichter
2021-08-09 20:06 ` Tomi Ollila [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2a6lqz8kj.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).