From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: feature request: caching message arrival time
Date: Fri, 31 May 2019 23:29:01 -0400 [thread overview]
Message-ID: <8736kuhtky.fsf@fifthhorseman.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
Hi Notmuch folks--
I'm working on Autocrypt integration for notmuch right now, and it
occurs to me that it might be useful to know the time that any given
message was first seen by notmuch.
I'm trying to not get distracted by implementing such a feature, but I
wanted to log this as a feature request, along with a few thoughts about
it.
My idea is that the first time notmuch indexes a message, it would add a
property to the message like firstseen=2019-05-31T23:15:24Z.
Some nuances spring to mind:
* This should *not* be cleared and reset on reindexing, so it doesn't
belong in the index.* property namespace.
* What happens when you delete a message? Maybe we should keep that
value around for "ghosts" too -- can ghost documents have properties?
Or is it bad to remember that we've seen the message if someone
deletes it?
* When even the ghost goes away (e.g. full thread deletion), presumably
this property would go away. So If you deleted the message from your
message store, notmuch would forget about it, and then the next time
you ingest it it would get a later "firstseen=" property. I'm ok
with this.
* i don't think we have a way to search properties by range (e.g. the
way that we can search date ranges). i don't need that feature for
my use case, but maybe someone will come up with a use case that
wants it? is there a way to store the datestamp in a way that it can
be scanned the way that "date" can? or do we already have this and
i'm just unaware?
* What is the cost in terms of database size? It doesn't look like it
would be expensive to me, but i haven't profiled it.
* if we make such a change, how should we deal with already-indexed
messages?
Anyone have any thoughts, suggestions, or objections to this? I'm happy
to explain more about my use case if people are interested too.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2019-06-01 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 3:29 Daniel Kahn Gillmor [this message]
2019-06-01 14:13 ` feature request: caching message arrival time David Bremner
2019-06-01 14:19 ` Ralph Seichter
2019-06-01 15:30 ` Daniel Kahn Gillmor
2019-06-03 8:57 ` Örjan Ekeberg
2019-06-03 13:17 ` Daniel Kahn Gillmor
2019-06-03 14:02 ` Ralph Seichter
2019-06-03 22:16 ` Daniel Kahn Gillmor
2019-06-03 16:02 ` Örjan Ekeberg
2019-06-03 22:21 ` Daniel Kahn Gillmor
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=8736kuhtky.fsf@fifthhorseman.net \
--to=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).