unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Siddh Raman Pant <code@siddh.me>
To: "Eric Wong" <e@80x24.org>
Cc: "meta" <meta@public-inbox.org>
Subject: Re: Feature request: Support for body in mailto links
Date: Thu, 22 Dec 2022 12:13:31 +0530	[thread overview]
Message-ID: <18538929ff8.403f681413425.3049598018127849867@siddh.me> (raw)
In-Reply-To: <20221221210419.M104936@dcvr>

On Thu, 22 Dec 2022 02:34:19 +0530, Eric Wong, wrote:
> Siddh Raman Pant code@siddh.me> wrote:
> > Hello,
> > 
> > It would be nice if mailto links also contained the body of the
> > email one is replying to in quoted form (i.e. have leading "> ")
> > so that one can directly start replying when the client opens. It
> > seems the "body" hname allows this behaviour.
>
> How many mail clients does it work on? And do people even use
> mailto: links?

I tried it on mutt, Thunderbird, GMail web and mobile, Outlook web,
and Samsung's mobile mail app. So it does seem to have wide support.

If mailto is unused, why would the option and its support be there
in this project, and also in proprietary clients on mobile and web?

Debbugs also has the behaviour I mentioned, you may try it on any of
their bug report email pages. For example:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018118
(I know it's not exactly an archival project like this.)

> It would roughly double the the size of HTML
> responses for /$INBOX/$MSGID/ endpoints and probably increase
> browser memory use a similar amount.

That makes sense, thanks.

While I can't say much about performance in general (I am not much
familiar with the project internals, and came across this due to
lore.kernel.org), but regarding browser memory, the threaded view
already shows multiple messages, so I don't think it would be too
much of an issue, and the mailto links are apparently only shown
when you open permalinks.

I just tried loading on w3m an 896 KB HTML thread from lore.kernel.org
(containing 2-3 kernel configs, which you'd agree is normally huge
spam), and w3m seems to take 33MB of memory, a normal amount.

> Fwiw, I'm not a fan of quoting publicly-archived mail;
> especially with our "archives first" philosophy.
> 
> Quotes makes messages significantly bigger than they need to be;
> thus more expensive to mirror when the replied message is
> readily accessible in public archives.  I end up skipping over
> quotes 99% of the time.

Isn't quoting when replying to the convention? And most mailing lists
I have seen use quoting...

Thanks,
Siddh

  reply	other threads:[~2022-12-22  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 15:21 Feature request: Support for body in mailto links Siddh Raman Pant
2022-12-21 21:04 ` Eric Wong
2022-12-22  6:43   ` Siddh Raman Pant [this message]
2022-12-22 11:28     ` Eric Wong

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=18538929ff8.403f681413425.3049598018127849867@siddh.me \
    --to=code@siddh.me \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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.
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).