Re: notmuch.el: controlling what does and doesn't get expanded in searches
[notmuch-archives.git] / db / 6f08af960b659ef9e2ab6e65428470321fd1ca
1 Return-Path: <jinwoo68@gmail.com>\r
2 X-Original-To: notmuch@notmuchmail.org\r
3 Delivered-To: notmuch@notmuchmail.org\r
4 Received: from localhost (localhost [127.0.0.1])\r
5         by olra.theworths.org (Postfix) with ESMTP id 22992431FCB\r
6         for <notmuch@notmuchmail.org>; Thu, 29 Jan 2015 10:14:34 -0800 (PST)\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: 2.639\r
10 X-Spam-Level: **\r
11 X-Spam-Status: No, score=2.639 tagged_above=-999 required=5\r
12         tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
13         DNS_FROM_AHBL_RHSBL=2.438, FREEMAIL_ENVFROM_END_DIGIT=1,\r
14         FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
15 Received: from olra.theworths.org ([127.0.0.1])\r
16         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
17         with ESMTP id U-wwF6V+vKuL for <notmuch@notmuchmail.org>;\r
18         Thu, 29 Jan 2015 10:14:31 -0800 (PST)\r
19 Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com\r
20         [209.85.220.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
21         (No client certificate requested)\r
22         by olra.theworths.org (Postfix) with ESMTPS id C9A17431FBC\r
23         for <notmuch@notmuchmail.org>; Thu, 29 Jan 2015 10:14:30 -0800 (PST)\r
24 Received: by mail-pa0-f53.google.com with SMTP id kx10so41975403pab.12\r
25         for <notmuch@notmuchmail.org>; Thu, 29 Jan 2015 10:14:29 -0800 (PST)\r
26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
27         h=from:to:subject:in-reply-to:references:user-agent:date:message-id\r
28         :mime-version:content-type;\r
29         bh=Shk5IEFVaWoI92e39P87CwLNRTC3/laoke8/QTa6YsY=;\r
30         b=b1JPJ2JNu3xgP3WFEtzsnOklVxHCr0AUV0GbyAi6Zt/CRzHBG53NlACEHP2JowFCRV\r
31         7hoNyvWgzdrAmwINS+CO6WAgXa487gjkXLSfE7EI8oAONwfUdESj/y1XEKGlEgSsSagg\r
32         ouQ4CDGRBfjOeHQJMoUwCXod5DJMyJdmg9UwBtPX2z2Q1ccOHgqdAW0TMDM6ck6MQ4uZ\r
33         Ec2Ng2eCUrrjDEUQU+LjTC0naacaywsh+k1C9LM2NAhuPZingJ035qRu5TuMrJTW0+0d\r
34         Gi/k+ya7WyIUbjoQUIFupHD5RE+UUAdjxVr9ZNECrU0yWynUw+LwE+1PKnazoSjTzTNb\r
35         Gr3w==\r
36 X-Received: by 10.66.157.5 with SMTP id wi5mr2571642pab.37.1422555269869;\r
37         Thu, 29 Jan 2015 10:14:29 -0800 (PST)\r
38 Received: from localhost ([2601:9:5d00:15b9:9997:a9cd:4a6a:40f0])\r
39         by mx.google.com with ESMTPSA id fg6sm8450866pdb.24.2015.01.29.10.14.28\r
40         (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
41         Thu, 29 Jan 2015 10:14:29 -0800 (PST)\r
42 From: Jinwoo Lee <jinwoo68@gmail.com>\r
43 To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
44         notmuch mailing list <notmuch@notmuchmail.org>\r
45 Subject: Re: privacy problem: text/html parts pull in network resources\r
46 In-Reply-To: <87wq45cvls.fsf@alice.fifthhorseman.net>\r
47 References: <87ppa7q25w.fsf@alice.fifthhorseman.net>\r
48         <87fvay3g0g.fsf@maritornes.cs.unb.ca>\r
49         <871tmfin1k.fsf@alice.fifthhorseman.net>\r
50         <yq65h9vbtsyt.fsf@jinwoo-macbookair.roam.corp.google.com>\r
51         <yq65386uqx0a.fsf@jinwoo-macbookair.roam.corp.google.com>\r
52         <87wq45cvls.fsf@alice.fifthhorseman.net>\r
53 User-Agent: Notmuch/0.18.1 (http://notmuchmail.org) Emacs/24.4.1\r
54         (x86_64-apple-darwin13.2.0)\r
55 Date: Thu, 29 Jan 2015 10:14:27 -0800\r
56 Message-ID: <yq65wq45sbcs.fsf@jinwoo-macbookair.roam.corp.google.com>\r
57 MIME-Version: 1.0\r
58 Content-Type: text/plain\r
59 X-BeenThere: notmuch@notmuchmail.org\r
60 X-Mailman-Version: 2.1.13\r
61 Precedence: list\r
62 List-Id: "Use and development of the notmuch mail system."\r
63         <notmuch.notmuchmail.org>\r
64 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
65         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
66 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
67 List-Post: <mailto:notmuch@notmuchmail.org>\r
68 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
69 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
70         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
71 X-List-Received-Date: Thu, 29 Jan 2015 18:14:34 -0000\r
72 \r
73 On Thu, Jan 29, 2015 at 10:03 AM, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
74 > On Wed 2015-01-28 18:57:25 -0500, Jinwoo Lee wrote:\r
75 >> Do you mind if I add a boolean defcustom, which determines whether to\r
76 >> block remote images?  Its default value will be T (block), but people\r
77 >> who want to see remote images can customize it.\r
78 >\r
79 > I have no objection to this kind of knob in an already fiddly config\r
80 > space.  In the other thread, i see the discussion of whether this should\r
81 > expose something fancier than a boolean, but given the number of\r
82 > possible rendering backends, i don't know how well we can support any of\r
83 > these options reliably.\r
84 >\r
85 > What should notmuch do when the customization variable is set to t\r
86 > (block remote images) but the html rendering backend doesn't support\r
87 > blocking remote images?\r
88 >\r
89 > It seems dangerous/disingenuous to offer the option to the user but not\r
90 > be able to enforce it in this case.  Should having this set to t\r
91 > restrict the range of html renderers to only those that we can force to\r
92 > respect it?\r
93 \r
94 I'm not very knowledgeable in the notmuch codebase, but I think I agree\r
95 with your concern about this customization variable being dangerous or\r
96 misleading users.\r
97 \r
98 +1 to restricting renderers.\r
99 \r
100 >\r
101 >         --dkg\r
102 > _______________________________________________\r
103 > notmuch mailing list\r
104 > notmuch@notmuchmail.org\r
105 > http://notmuchmail.org/mailman/listinfo/notmuch\r