From: martin f krafft <madduck@madduck.net>
To: Carl Worth <cworth@cworth.org>
Cc: notmuch discussion list <notmuch@notmuchmail.org>,
mailtags discussion list <mailtags@lists.madduck.net>
Subject: Re: Idea for storing tags
Date: Thu, 14 Jan 2010 21:04:21 +1300 [thread overview]
Message-ID: <20100114080421.GA17305@lapse.rw.madduck.net> (raw)
In-Reply-To: <87hbqpfp47.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 2974 bytes --]
also sprach Carl Worth <cworth@cworth.org> [2010.01.14.1432 +1300]:
> Yes. This approach requires some external means of synchronizing the
> tags from one system to another.
>
> I don't understand what it would mean to have the mailstore and the
> database out of synch here. This approach doesn't have the tags in the
> mailstore by definition, right?
You might have marked a message 'read' on one machine and if the two
get out of sync on another machine, you might have the same message
unread there.
> > How about using pseudo-mails stored in Maildir and synchronised by
> > IMAP? E.g. every folder could have a subfolder .TAGS and if we find
> > a way to smartly pair messages between parent and subfolder, we'd
> > have a tag store alongside the mailstore it refers to, but without
> > the danger of leakage, and without having to rewrite messages.
> ...
> > Anyway, the idea is out now. Thoughts?
>
> There are a couple of problems that I don't see addressed at all with
> this approach. The first is that there's not a one-to-one mapping
> between messages and files in the mail store. (I'm CCed on a lot of list
> mail meaning that I have multiple files in my mail store for a single
> message.)
Shouldn't this just be solved? I've had formail+procmail delete my
duplicates for 10+ years, and while I don't like the fact that
I usually get the CC before the list mail, and thus cannot filter on
Delivered-To, I have never looked back.
> Second, the only reason I would be interested in synchronizing mail
> between two systems is so that I could manipulate the tag data in
> multiple places, (that is, remove the "unread" tag whether on my
> network-disconnected laptop or via web-mail when away from my
> laptop). Using imap for synchronizing a file of tags within the mail
> store gives you no mechanism for doing any sort of conflict resolution,
> right? (Which I think in almost all cases is going to be quite trivial
> if there's a chance for a program to resolve it.)
I have not thought about this, but you are right. IMAP does not
really allow for conflict resolution, which may well be *the* reason
why you cannot update existing messages.
> [*] Though, I think a plain-text file with tags managed with
> something like git (and perhaps a custom merger) could save a lot
> of work. Or perhaps a plain-text journal of tag manipulations on
> either end that could be replayed on the other.
Git is good at conflict resolution if run interactively, but [0]
still makes me question whether it can ever take the place of IMAP.
However, Asheesh Laroia, who has floated the idea of Git-for-mail at
DebConf8 already, has some ideas and hopefully will soon reply to my
mail [0], which I just bounced.
0. http://notmuchmail.org/pipermail/notmuch/2010/001114.html
--
martin | http://madduck.net/ | http://two.sentenc.es/
apt-get source --compile gentoo
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-14 8:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 22:19 Idea for storing tags martin f krafft
2010-01-12 3:44 ` Scott Robinson
2010-01-12 4:06 ` martin f krafft
2010-01-12 4:51 ` Potential problem using Git for mail (was: Idea for storing tags) martin f krafft
2010-01-12 19:38 ` Jameson Rollins
2010-01-12 19:55 ` martin f krafft
2010-01-14 8:12 ` Asheesh Laroia
2010-01-14 20:37 ` martin f krafft
2010-01-21 6:28 ` Asheesh Laroia
2010-01-25 0:46 ` Git as notmuch object store (was: Potential problem using Git for mail) martin f krafft
2010-01-25 5:19 ` Asheesh Laroia
2010-01-25 7:43 ` martin f krafft
2010-01-25 13:49 ` Sebastian Spaeth
2010-01-25 16:22 ` Mike Kelly
2010-01-25 21:46 ` tag dir proposal [was: Re: Git as notmuch object store] Jameson Rollins
2010-01-26 16:32 ` Scott Robinson
2010-01-26 17:03 ` Jameson Rollins
2010-01-28 5:12 ` martin f krafft
2010-01-28 5:28 ` James Westby
2010-01-28 5:34 ` martin f krafft
2010-01-28 6:22 ` James Westby
2010-01-28 9:55 ` martin f krafft
2010-01-28 5:10 ` martin f krafft
2010-01-28 12:32 ` Servilio Afre Puentes
2010-01-28 20:39 ` martin f krafft
2010-01-28 20:49 ` Ben Gamari
2010-01-28 21:11 ` martin f krafft
[not found] ` <1264713802-sup-620@ben-laptop>
[not found] ` <20100128221735.GE8942@lapse.rw.madduck.net>
2010-01-28 23:30 ` Ben Gamari
2010-01-28 21:16 ` Jed Brown
2010-01-25 19:49 ` Git as notmuch object store (was: Potential problem using Git for mail) martin f krafft
2010-01-27 9:00 ` Sebastian Spaeth
2010-02-15 0:51 ` Stewart Smith
2010-01-12 4:11 ` Idea for storing tags Scott Morrison
2010-01-13 1:24 ` martin f krafft
2010-01-13 5:39 ` Scott Morrison
2010-01-13 5:52 ` martin f krafft
2010-01-14 1:37 ` Carl Worth
2010-01-12 21:39 ` David A. Harding
2010-01-14 1:32 ` Carl Worth
2010-01-14 8:04 ` martin f krafft [this message]
2010-01-14 22:24 ` Carl Worth
2010-01-14 22:32 ` martin f krafft
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=20100114080421.GA17305@lapse.rw.madduck.net \
--to=madduck@madduck.net \
--cc=cworth@cworth.org \
--cc=mailtags@lists.madduck.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).