From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [TUHS] [COFF] Topics...
Date: Wed, 8 Jul 2020 08:53:30 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2007080844370.455@aneurin.horsfall.org> (raw)
In-Reply-To: <8af3a571-aeb5-21fc-0041-be8649e3f9ba@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
On Mon, 6 Jul 2020, Grant Taylor via COFF wrote:
> I see this type of change happen — in my not so humble opinion — /way/
> /too/ /often/.
It is the nature of unmoderated mailing lists that topics will drift over
time until someone jumps in to change the Subject: (and it really ought to
be a new thread) and hope that others will take the hint.
Yes, I'm just as guilty as others; then again, I've also changed the
subject when I realise my transgression.
> So, I'm wondering if people are interested in configuring TUHS and / or
> COFF mailing list (Mailman) with topics. That way people could
> subscribe to the topics that they are interested in and not receive
> copies of topics they aren't interested in.
They would then need to see what new topics come up from time to time...
> I'm assuming that TUHS and COFF are still on Mailman mailing lists and
> that Warren would be amicable to such.
I believe they are on Mailman, but I have little experience with running
it.
> To clarify, it would still be the same mailing list(s) as they exist
> today. They would just have the to be utilized option of picking
> interesting topics. Where topics would be based on keywords in the
> message body.
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.
-- Dave
next prev parent reply other threads:[~2020-07-07 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:11 [TUHS] Topics Grant Taylor via TUHS
2020-07-07 2:56 ` [TUHS] [COFF] Topics Adam Thornton
2020-07-07 14:33 ` [TUHS] Topics Tomasz Rola
2020-07-07 14:38 ` Alan D. Salewski
2020-07-07 15:26 ` John Cowan
2020-07-07 22:53 ` Dave Horsfall [this message]
2020-07-07 23:23 ` [TUHS] [COFF] Topics Jacob Goense
2020-07-07 23:45 ` Michael Usher via TUHS
2020-07-08 2:09 ` Dave Horsfall
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.21.9999.2007080844370.455@aneurin.horsfall.org \
--to=dave@horsfall.org \
--cc=coff@tuhs.org \
--cc=tuhs@tuhs.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.
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 NNTP newsgroup(s).