From: David Edmondson <dme@dme.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: using the fringe to indicate good signatures
Date: Tue, 08 Sep 2015 10:53:44 +0100 [thread overview]
Message-ID: <m2si6p8cev.fsf@heart-of-gold.hh.sledj.net> (raw)
In-Reply-To: <87twr5jtqy.fsf@alice.fifthhorseman.net>
On Tue, Sep 08 2015, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>> More seriously, we could use the indentation space for a similar
>> indicator, which would allow us some room at an appropriate depth for
>> each message (but not each part (in the default configuration)).
>
> hm, but couldn't the indentation space be spoofed by a well-crafted
> message? that is: a non-indented message will consume space up to (but
> not including) the fringe. so a well-crafted message could be made to
> *look* like an indented message, including whatever is comparable to the
> chrome/UI elements we would use for an actual signed message.
Yes, I guess that is possible at some level.
The fringe is a bitmap - we could use the leftmost vertical line of it
for the outermost component, next line for the next component, ...
Or perhaps use images:
- all levels of the message at this line are "good",
- some of the levels of the message at this line are "good".
Or maybe display a QR code in the fringe, and you point your phone at it
to find out what is going on?
> I think it is also acceptable to just punt at some level -- we can say
> "notmuch-emacs will indicate the outermost signed message part in the
> fringe; it will not indicate nested signed messages in the fringe".
> this is still an improvement from the status quo.
next prev parent reply other threads:[~2015-09-08 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 13:12 using the fringe to indicate good signatures David Edmondson
2015-09-07 22:50 ` Daniel Kahn Gillmor
2015-09-08 6:01 ` David Edmondson
2015-09-08 6:43 ` Daniel Kahn Gillmor
2015-09-08 9:53 ` David Edmondson [this message]
2015-09-08 18:00 ` Tomi Ollila
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=m2si6p8cev.fsf@heart-of-gold.hh.sledj.net \
--to=dme@dme.org \
--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).