Re: [notmuch] Idea for storing tags

diff --git a/bb/b73d10b9df9759b366d80d25b207b4d8e88eb9 b/bb/b73d10b9df9759b366d80d25b207b4d8e88eb9
new file mode 100644 (file)
index 0000000..5124a28
--- /dev/null
+++ b/bb/b73d10b9df9759b366d80d25b207b4d8e88eb9
@@ -0,0 +1,108 @@
+Return-Path: <cworth@cworth.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id A1C10431FBC\r
+       for <notmuch@notmuchmail.org>; Wed, 13 Jan 2010 17:32:10 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.821\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5\r
+       tests=[ALL_TRUSTED=-1.8, AWL=-0.022, BAYES_50=0.001] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id lIzYD6TKr9K5; Wed, 13 Jan 2010 17:32:09 -0800 (PST)\r
+Received: from yoom.home.cworth.org (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 95AC4431FAE;\r
+       Wed, 13 Jan 2010 17:32:09 -0800 (PST)\r
+Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
+       id 43112254090; Wed, 13 Jan 2010 17:32:09 -0800 (PST)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: martin f krafft <madduck@madduck.net>, mailtags discussion list\r
+       <mailtags@lists.madduck.net>\r
+In-Reply-To: <20100111221909.GA30299@lapse.rw.madduck.net>\r
+References: <20100111221909.GA30299@lapse.rw.madduck.net>\r
+Date: Wed, 13 Jan 2010 17:32:08 -0800\r
+Message-ID: <87hbqpfp47.fsf@yoom.home.cworth.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\r
+Cc: notmuch discussion list <notmuch@notmuchmail.org>\r
+Subject: Re: [notmuch] Idea for storing tags\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 14 Jan 2010 01:32:10 -0000\r
+\r
+--=-=-=\r
+\r
+On Tue, 12 Jan 2010 11:19:09 +1300, martin f krafft <madduck@madduck.net> wrote:\r
+> 1. External database, which has the downside of not being\r
+>    synchronisable with standard IMAP, like the rest of your mail\r
+>    (assuming you use IMAP). Also, it's possible for mailstore and\r
+>    database to get out of sync.\r
+\r
+Yes. This approach requires some external means of synchronizing the\r
+tags from one system to another.\r
+\r
+I don't understand what it would mean to have the mailstore and the\r
+database out of synch here. This approach doesn't have the tags in the\r
+mailstore by definition, right?\r
+\r
+> How about using pseudo-mails stored in Maildir and synchronised by\r
+> IMAP? E.g. every folder could have a subfolder .TAGS and if we find\r
+> a way to smartly pair messages between parent and subfolder, we'd\r
+> have a tag store alongside the mailstore it refers to, but without\r
+> the danger of leakage, and without having to rewrite messages.\r
+...\r
+> Anyway, the idea is out now. Thoughts?\r
+\r
+There are a couple of problems that I don't see addressed at all with\r
+this approach. The first is that there's not a one-to-one mapping\r
+between messages and files in the mail store. (I'm CCed on a lot of list\r
+mail meaning that I have multiple files in my mail store for a single\r
+message.)\r
+\r
+Second, the only reason I would be interested in synchronizing mail\r
+between two systems is so that I could manipulate the tag data in\r
+multiple places, (that is, remove the "unread" tag whether on my\r
+network-disconnected laptop or via web-mail when away from my\r
+laptop). Using imap for synchronizing a file of tags within the mail\r
+store gives you no mechanism for doing any sort of conflict resolution,\r
+right? (Which I think in almost all cases is going to be quite trivial\r
+if there's a chance for a program to resolve it.)\r
+\r
+So it sounds to me like we're going to need *something* custom for doing\r
+the synchronization, (to handle modifications on both ends). At which\r
+point there's only disadvantages to keeping the data inside the\r
+mailstore, and there's also no disadvantage left to keeping the data\r
+inside a database. [*]\r
+\r
+[*] Though, I think a plain-text file with tags managed with something\r
+like git (and perhaps a custom merger) could save a lot of work. Or\r
+perhaps a plain-text journal of tag manipulations on either end that\r
+could be replayed on the other.\r
+\r
+-Carl\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iD8DBQFLTnQZ6JDdNq8qSWgRAkEHAJ4wqrIK/iL1iB8FzudLc40ToYs8ZACcD3wu\r
+mgLY8cAlsCbTaPTdD7Zou8o=\r
+=HSmh\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r