The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: Mangled and non-mangled TUHS mail lists
Date: Wed, 04 Oct 2017 22:59:22 +0200	[thread overview]
Message-ID: <20171004205922.oHRB1%steffen@sdaoden.eu> (raw)
In-Reply-To: <alpine.BSF.2.21.1710041326421.73049@aneurin.horsfall.org>

Dave Horsfall <dave at horsfall.org> wrote:
 |On Tue, 3 Oct 2017, Steffen Nurpmeso wrote:
 |>|I think that modifying the subject to add a tag is a perfectly valid 
 |>|thing.  As such, provisions should make such modifications /possible/. 
 |>|Then leave the choice of doing so or not up to each list's 
 |>|administrator.
 |>
 |> As has happened recently.  Sure.
 |
 |Except Warren did it backwards; he should've left the original list as it 
 |was, and migrated those with fussy clients to the new list.

Waves and material of various nature pervades us, for example
100 billion Neutrinos per second per fingertip i have learned
a few days ago.  To let it be consciously can thus not only be
seen as waving a red flag, but also as an indication of maturity,
as could have been teached by a ML guru.  Is that exaggerated.

I have turned on DKIM stripping for these tiny lists of mine.
That is not polite to people who use DKIM to say the least, shall
there be any, but i am not (experienced as) an administrator,
i have a very restricted (ridiculous to most of you for sure)
working environment and all i want is that this mess works
smoothly, so that i can spend time on things i have interest in.
And whereas i avoid a footer that would introduce a MIME multipart
where otherwise there would be none, i do prepend something to the
subject, because i like to see this.  It is a small project, and
people should have the possibility to visually degrade it and come
back when they have time for it.  Or something like this.  You
know, small projects of little interest cannot act as if they were
giants.  Of course you can pre-select on headers as in 'from
@<@tuhs\.org', but i never used this style of inbox stuff, i am
reading top-down, some mails keep lingering for later, but they
will be read and then dispatched, not vice versa, and this way of
doing things requires some easy visual thread methody.  Hm.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


  reply	other threads:[~2017-10-04 20:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01  3:25 Warren Toomey
2017-10-01 14:00 ` Clem Cole
2017-10-01 14:08   ` Don Hopkins
2017-10-02  1:01 ` Dave Horsfall
2017-10-02  8:22   ` jason-tuhs
2017-10-02 12:38     ` Steve Nickolas
2017-10-02 13:34       ` David Ryskalczyk
2017-10-03  0:51         ` Dave Horsfall
2017-10-03  2:19           ` Steve Nickolas
2017-10-03  3:25             ` Grant Taylor
2017-10-03  3:33               ` Dave Horsfall
2017-10-03  3:55                 ` Grant Taylor
2017-10-03  4:17                   ` Dave Horsfall
2017-10-03  4:12                 ` Kurt H Maier
2017-10-03  7:40                   ` Ian Zimmerman
2017-10-03 14:08                 ` Steffen Nurpmeso
2017-10-03 18:20                   ` Grant Taylor
2017-10-03 18:43                     ` Ian Zimmerman
2017-10-03 21:59                       ` Grant Taylor
2017-10-03 18:49                     ` Steffen Nurpmeso
2017-10-03 21:54                       ` Grant Taylor
2017-10-03 22:00                         ` Mangled and non-mangled TUHS mail lists [ enough already? ] Jon Steinhart
2017-10-04 20:17                         ` Mangled and non-mangled TUHS mail lists Steffen Nurpmeso
2017-10-04  2:28                       ` Dave Horsfall
2017-10-04 20:59                         ` Steffen Nurpmeso [this message]
2017-10-03 10:12               ` Steve Nickolas
2017-10-03 19:21                 ` Bakul Shah

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=20171004205922.oHRB1%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /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).