From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS56201 103.117.158.0/23 X-Spam-Status: No, score=-3.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sender-of-o50.zoho.in (sender-of-o50.zoho.in [103.117.158.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 0D9601F852 for ; Thu, 22 Dec 2022 06:43:47 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; secure) header.d=siddh.me header.i=code@siddh.me header.b="DNkY9Jpb"; dkim-atps=neutral ARC-Seal: i=1; a=rsa-sha256; t=1671691424; cv=none; d=zohomail.in; s=zohoarc; b=V+Qq4M/OYE1EPwrle7UnRH7KT/IDYk+gbB7c3BG/0RNKmbUsBcjDV4H1+Hzq9CZvjRPgXgJR8/QDSNFV6jU++HXkL7vfszYAVNWQTf8zSZO+ws/f0TinV1Qj42/Md4717NfiJ6Ir3ZeYx6glOg+nQ/u09fj4fdfdFqavax0ob/s= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.in; s=zohoarc; t=1671691424; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=RaVQ9DGvtBXOAuM61/hIcDzZAkc6XztGgyPp0iXvJBg=; b=bBne04Rrm0E338KfJFGG7TNJ60IqstsnkRboDMLbznjhFJIN3vgFh7tPe3YciJyMyd8tXXxQfyba/NkjhcM/S3Zh1e4SOWUo1GiID8X2IiZd8gCm+O8fz/zQkyxeHfaJh5PU0fwB8ItG9LKcfg5pr3A0qYdPm+dnj9O2JPRFGWA= ARC-Authentication-Results: i=1; mx.zohomail.in; dkim=pass header.i=siddh.me; spf=pass smtp.mailfrom=code@siddh.me; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1671691424; s=zmail; d=siddh.me; i=code@siddh.me; h=Date:Date:From:From:To:To:Cc:Cc:Message-ID:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id:Reply-To; bh=RaVQ9DGvtBXOAuM61/hIcDzZAkc6XztGgyPp0iXvJBg=; b=DNkY9JpbpX4XoT+NPY57VjERmwcyiZBdWiGcAfA+cZoa0Xl8m0/2x1R7VQgzKuH+ 9DZ2v/SvB53UM0iIcgzl4CePBt7+wqZZLndBVuR5fdVK0Tx3ov/7NLnBzoeR901C98T 1nwL3hNZ3udLdN/TEyHQLcCeZSFxOJPaEerW+ytE= Received: from mail.zoho.in by mx.zoho.in with SMTP id 1671691411473244.76075243403977; Thu, 22 Dec 2022 12:13:31 +0530 (IST) Date: Thu, 22 Dec 2022 12:13:31 +0530 From: Siddh Raman Pant To: "Eric Wong" Cc: "meta" Message-ID: <18538929ff8.403f681413425.3049598018127849867@siddh.me> In-Reply-To: <20221221210419.M104936@dcvr> References: <18535462dd8.51aa0823363186.5436123899292105414@siddh.me> <20221221210419.M104936@dcvr> Subject: Re: Feature request: Support for body in mailto links MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail List-Id: 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