From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18572 invoked from network); 7 Jul 2020 23:47:07 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 7 Jul 2020 23:47:07 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 624AB9C8F7; Wed, 8 Jul 2020 09:47:06 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5AD8B9C72F; Wed, 8 Jul 2020 09:46:11 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; secure) header.d=ucsc.edu header.i=@ucsc.edu header.b="ZJkF/D+0"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id DB30E9C72F; Wed, 8 Jul 2020 09:46:09 +1000 (AEST) Received: from mail-vk1-f179.google.com (mail-vk1-f179.google.com [209.85.221.179]) by minnie.tuhs.org (Postfix) with ESMTPS id 559EC9C6B5 for ; Wed, 8 Jul 2020 09:46:09 +1000 (AEST) Received: by mail-vk1-f179.google.com with SMTP id s192so9826129vkh.3 for ; Tue, 07 Jul 2020 16:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google-2018; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QRfqitqkuzsUQTj+3S3lPFdTfG5XCb9/tgNeR2+sbl4=; b=ZJkF/D+0+drSEWy6xvIgJu+bJeEH91+trnuHKEj1KL3N55lbCbUaPr+z+J/RWDI+LW HHyK1/M78rktI74YZdc/Ft6VOYtswLL7cSG+f3dg2MBGCrAGpF97w1r+8aDCkwv5wzaK HiNwRnIvpGx1+g1l48AyD+EUf1zZyEAF3nQQiH+CAq+HsYSggafbJ4Oh3G2a+e/NsbcZ 6lbssRm+ln9S2cyPWpsAADxqu3U/wIvsyrmiqpKRE7wClnhp8c5xNyXnNAjnvBLewSi3 r2fnXeyN+KqH3F05AY8rmCJhAixc7e0yIQttuWPdhecxRClyu8k0K8eIfk1KyGS0hCps sd9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QRfqitqkuzsUQTj+3S3lPFdTfG5XCb9/tgNeR2+sbl4=; b=Gyyg0zmu2K7sDvuVic/e6sU3IkCHbwprjC6Zps6uZOMlJk2WOl+lgPYioEDuNgOQZl mCU9UhwuvrgSgdoCp6S/Gw/OOAfoqVX1vaposcIWX2brldsQJtt7JwlVarq5J3Pj3eW8 +3wX7tClmGDv6WKIkt7mPsbh+HY6GM9xRPRgpjrWgGHsAi5B3+IV/61964nCTYIicQeT wOOZbHquYawKJRdU+3eSC4alfa7zVsBvTiejaWrZzu/5W433AVnIkLr01JLJ8o/JqGsV UzWgLHgujzqFLOw62rEhJpmXi98lEfspFYKuZ/FSGMSYu0IdRpwh4t9RQG/VGImA97LH AntQ== X-Gm-Message-State: AOAM533Y12S+wxtuAp1LkKhECOvxCi0X66D7E20y6dIKR+Wy5zdgleUO XuOzD3bKurBU2+gU8TKNETrQSmfTtuYp7U7t25CscA== X-Google-Smtp-Source: ABdhPJzL/4e2Vk0BxAoMoFyk5yH4A5fqH6uRodHyvA6dfBXZZdv29RHnb0Efq4eomMrHsceCH5iTczhe6TGXOkpRD78= X-Received: by 2002:a1f:1182:: with SMTP id 124mr24305565vkr.75.1594165568462; Tue, 07 Jul 2020 16:46:08 -0700 (PDT) MIME-Version: 1.0 References: <8af3a571-aeb5-21fc-0041-be8649e3f9ba@spamtrap.tnetconsulting.net> <97902a98ce76c281160840d78ed838be@xs4all.nl> In-Reply-To: <97902a98ce76c281160840d78ed838be@xs4all.nl> Date: Tue, 7 Jul 2020 16:45:57 -0700 Message-ID: To: Jacob Goense Content-Type: multipart/alternative; boundary="0000000000006bf4a405a9e298e6" Subject: Re: [TUHS] [COFF] Topics... X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Usher via TUHS Reply-To: Michael Usher Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000006bf4a405a9e298e6 Content-Type: text/plain; charset="UTF-8" I usually edit it to say "Was (not Was)". Hmmm. Wouldn't it be great if we had a Markov chain subject generator that sourced the actual email thread contents as its driver, and then when the topic drifted far enough, it simply replaced the subject line with a new creation ? Ooohhh -- another idea -- RFC5322 states that subject may occur from 0 to 1 times per email. Why don't we just delete the subject lines entirely? Michael (it's late. I need to poke a bear) On Tue, Jul 7, 2020 at 4:30 PM Jacob Goense wrote: > On 2020-07-08 00:53, Dave Horsfall wrote: > > On one list I use, a predecessor of it used to require a subject tag > > in the form [Blah] (taken from a set of known tags); I've always hated > > that, but I'm still in the habit of putting my own tag there as a > > hint. > > When I have tuned out of a long running thread and the topic drifts > significantly I'm always grateful to the kind soul that tags..: > > Subject: Re: new [was: old] > -- Michael Usher Senior Wireless Network Engineer University of California, Santa Cruz musher@ucsc.edu 831-459-3697 --0000000000006bf4a405a9e298e6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I usually edit it to say "Was (not Was)".
Hmmm.=C2=A0 Wouldn't it be great if we had a Markov chain = subject generator that sourced the actual email thread contents as its driv= er, and then when the topic drifted far enough, it simply replaced the subj= ect line with a new creation ?

Ooohhh -- another i= dea -- RFC5322 states that subject may occur from 0 to 1 times per email.= =C2=A0 Why don't we just delete the subject lines entirely?
<= br>
Michael

(it's late.=C2=A0 I need= to poke a bear)


<= div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 7, 2020 at 4:30 PM Jacob G= oense <dugo@xs4all.nl> wrote:
On 2020-07-08 00:53, Dave Horsfall wrote:
> On one list I use, a predecessor of it used to require a subject tag > in the form [Blah] (taken from a set of known tags); I've always h= ated
> that, but I'm still in the habit of putting my own tag there as a<= br> > hint.

When I have tuned out of a long running thread and the topic drifts
significantly I'm always grateful to the kind soul that tags..:

=C2=A0 =C2=A0 =C2=A0Subject: Re: new [was: old]


--
Mich= ael Usher
Senior Wireless Network Engineer
University of Calif= ornia, Santa Cruz
musher@ucsc.edu=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0831-459-3697
<= /div>
--0000000000006bf4a405a9e298e6--