From: Jinwoo Lee <jinwoo68@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: privacy problem: text/html parts pull in network resources
Date: Thu, 29 Jan 2015 10:14:27 -0800 [thread overview]
Message-ID: <yq65wq45sbcs.fsf@jinwoo-macbookair.roam.corp.google.com> (raw)
In-Reply-To: <87wq45cvls.fsf@alice.fifthhorseman.net>
On Thu, Jan 29, 2015 at 10:03 AM, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> On Wed 2015-01-28 18:57:25 -0500, Jinwoo Lee wrote:
>> Do you mind if I add a boolean defcustom, which determines whether to
>> block remote images? Its default value will be T (block), but people
>> who want to see remote images can customize it.
>
> I have no objection to this kind of knob in an already fiddly config
> space. In the other thread, i see the discussion of whether this should
> expose something fancier than a boolean, but given the number of
> possible rendering backends, i don't know how well we can support any of
> these options reliably.
>
> What should notmuch do when the customization variable is set to t
> (block remote images) but the html rendering backend doesn't support
> blocking remote images?
>
> It seems dangerous/disingenuous to offer the option to the user but not
> be able to enforce it in this case. Should having this set to t
> restrict the range of html renderers to only those that we can force to
> respect it?
I'm not very knowledgeable in the notmuch codebase, but I think I agree
with your concern about this customization variable being dangerous or
misleading users.
+1 to restricting renderers.
>
> --dkg
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2015-01-29 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 21:00 privacy problem: text/html parts pull in network resources Daniel Kahn Gillmor
2015-01-21 21:14 ` Austin Clements
2015-01-21 21:36 ` Daniel Kahn Gillmor
2015-01-21 22:39 ` Austin Clements
2015-01-21 21:46 ` David Bremner
2015-01-22 7:25 ` Tomi Ollila
2015-01-25 17:51 ` David Bremner
2015-01-28 3:47 ` Daniel Kahn Gillmor
2015-01-28 4:44 ` Jinwoo Lee
2015-01-28 23:57 ` Jinwoo Lee
2015-01-29 18:03 ` Daniel Kahn Gillmor
2015-01-29 18:14 ` Jinwoo Lee [this message]
2015-01-30 12:12 ` David Edmondson
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=yq65wq45sbcs.fsf@jinwoo-macbookair.roam.corp.google.com \
--to=jinwoo68@gmail.com \
--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).