make: Write a post about my email to jwz

1 files changed, 77 insertions, 1 deletions

diff --git a/public/index.atom b/public/index.atom
index 6423bca..dd10c2c 100644
--- a/public/index.atom
+++ b/public/index.atom
@@ -5,12 +5,88 @@
 	<link rel="self"      type="application/atom+xml" href="./index.atom"/>
 	<link rel="alternate" type="text/html"            href="./"/>
 	<link rel="alternate" type="text/markdown"        href="./index.md"/>
-	<updated>2023-07-10T00:00:00+00:00</updated>
+	<updated>2024-06-08T00:00:00+00:00</updated>
 	<author><name>Luke T. Shumaker</name><uri>https://lukeshu.com/</uri><email>lukeshu@lukeshu.com</email></author>
 	<id>https://lukeshu.com/blog/</id>
 
 	
 	<entry xmlns="http://www.w3.org/2005/Atom">
+		<link rel="alternate" type="text/html"     href="./message-threading.html"/>
+		<link rel="alternate" type="text/markdown" href="./message-threading.md"/>
+		<id>https://lukeshu.com/blog/message-threading.html</id>
+		<updated>2024-06-08T00:00:00+00:00</updated>
+		<published>2024-06-08T00:00:00+00:00</published>
+		<title>Notes on email message threading</title>
+		<content type="html">&lt;h1 id="notes-on-email-message-threading"&gt;Notes on email message
+threading&lt;/h1&gt;
+&lt;blockquote&gt;
+&lt;p&gt;I sent an email to Jamie Zawinski with feedback on his venerable
+email threading algorithm. Perhaps my commentary will be a useful
+reference to others implementing email threading.&lt;/p&gt;
+&lt;p&gt;You can see my implementation of his algorithm at &lt;a
+href="https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread_alg.go"
+class="uri"&gt;https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread_alg.go&lt;/a&gt;
+(and a use of it at &lt;a
+href="https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread.go"
+class="uri"&gt;https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread.go&lt;/a&gt;).&lt;/p&gt;
+&lt;/blockquote&gt;
+&lt;div style="font-family: monospace"&gt;
+&lt;p&gt;To: &lt;a href="https://www.jwz.org/"&gt;Jamie Zawinski&lt;/a&gt; &lt;a
+href="https://www.jwz.org/about.html"&gt;&amp;lt;jwz@jwz.org&amp;gt;&lt;/a&gt;&lt;br/&gt;
+Subject: message threading&lt;br/&gt; Date: Sat, 08 Jun 2024 22:34:41 -0600
+Message-ID: &amp;lt;87tti2ybry.wl-lukeshu@lukeshu.com&amp;gt;&lt;/p&gt;
+&lt;/div&gt;
+&lt;p&gt;Hi,&lt;/p&gt;
+&lt;p&gt;I'm implementing message threading, and have been referencing both
+your document &lt;a
+href="https://www.jwz.org/doc/threading.html"&gt;&amp;lt;https://www.jwz.org/doc/threading.html&amp;gt;&lt;/a&gt;;
+and &lt;a href="https://datatracker.ietf.org/doc/html/rfc5256"&gt;RFC
+5256&lt;/a&gt;. I'm not sure whether you're interested in updating a document
+that's more than 25 years old, but if you are: I hope you find the
+following feedback valuable.&lt;/p&gt;
+&lt;p&gt;You write that the algorithm in RFC 5256 is merely a &lt;q&gt;restating&lt;/q&gt;
+of your algorithm, but I noticed 3 (minor) differences:&lt;/p&gt;
+&lt;ol type="1"&gt;
+&lt;li&gt;&lt;p&gt;In your step 1.C, the RFC says to check whether this would create
+a loop, and if it would to skip creating the link; your version only
+says to perform this check in step 1.B.&lt;/p&gt;&lt;/li&gt;
+&lt;li&gt;&lt;p&gt;The RFC says to sort the messages by date between your steps 4
+and 5; that is: when grouping by subject, containers in the root set
+should be processed in date-order (you do not specify an order), and
+that if container in the root set is empty then the subject should be
+taken from the earliest-date child (you say to use an arbitrary
+child).&lt;/p&gt;&lt;/li&gt;
+&lt;li&gt;&lt;p&gt;The RFC precisely states how to trim a subject down to a "base
+subject," rather than simply saying &lt;q&gt;Strip ``Re:'', ``RE:'',
+``RE[5]:'', ``Re: Re[4]: Re:'' and so on.&lt;/q&gt;&lt;/p&gt;&lt;/li&gt;
+&lt;/ol&gt;
+&lt;p&gt;Additionally, there are two minor points on which I found their
+version to be clearer:&lt;/p&gt;
+&lt;ol type="1"&gt;
+&lt;li&gt;&lt;p&gt;The RFC specifies how to handle messages without a Message-Id or
+with a duplicate Message-Id (on &lt;a
+href="https://datatracker.ietf.org/doc/html/rfc5256#page-9"&gt;page 9&lt;/a&gt;),
+as well as how to normalize a Message-Id (by referring to &lt;a
+href="https://datatracker.ietf.org/doc/html/rfc2822"&gt;RFC 2822&lt;/a&gt;). This
+is perhaps out-of-scope of your algorithm document, but I feel that it
+would be worth mentioning in your background or definitions
+section.&lt;/p&gt;&lt;/li&gt;
+&lt;li&gt;&lt;p&gt;In your step 1.B, I did not understand what &lt;q&gt;If they are
+already linked, don't change the existing links&lt;/q&gt; meant until I read
+the RFC, which words it as &lt;q&gt;If a message already has a parent, don't
+change the existing link.&lt;/q&gt; It was unclear to me what &lt;q&gt;they&lt;/q&gt; was
+referring to in your version.&lt;/p&gt;&lt;/li&gt;
+&lt;/ol&gt;
+&lt;div style="font-family: monospace"&gt;
+&lt;p&gt;-- &lt;br/&gt; Happy hacking,&lt;br/&gt; ~ Luke T. Shumaker&lt;br/&gt;&lt;/p&gt;
+&lt;/div&gt;
+</content>
+		<author><name>Luke T. Shumaker</name><uri>https://lukeshu.com/</uri><email>lukeshu@lukeshu.com</email></author>
+		<rights type="html">&lt;p&gt;The content of this page is Copyright © 2024 &lt;a href="mailto:lukeshu@lukeshu.com"&gt;Luke T. Shumaker&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;This page is licensed under the &lt;a href="https://creativecommons.org/licenses/by-sa/4.0/"&gt;CC BY-SA 4.0&lt;/a&gt; license.&lt;/p&gt;</rights>
+	</entry>
+	
+	<entry xmlns="http://www.w3.org/2005/Atom">
 		<link rel="alternate" type="text/html"     href="./btrfs-rec.html"/>
 		<link rel="alternate" type="text/markdown" href="./btrfs-rec.md"/>
 		<id>https://lukeshu.com/blog/btrfs-rec.html</id>