From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Signal/noise
Date: Mon, 4 Feb 2019 15:55:37 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1902041535470.64931@aneurin.horsfall.org> (raw)
In-Reply-To: <1ACB2A2B-FE88-42E4-B08A-BDA6D074D902@bitblocks.com>
On Sun, 3 Feb 2019, Bakul Shah wrote:
> I have said this before (or at least thought it!) but I, and I suspect
> some others, think of TUHS much like comp.unix.wizards of the old.
That's pretty much how I think of it (until the filthy spammers trashed
the joint, of course, there being no authentication in those days, because
there was no need for it; if there was a problem child, you merely picked
up the phone or sent a short email to the site admin: end of problem[*]).
> Though Jimmy >PAGE< would certainly fit TUHS :-)
Well done, sir :-) Perhaps we need a list for Old-Unix-Lovers-Into-Rock?
[*]
With exceptions; one ISP merely had an auto-responder on their abuse
address ("He's gone"), but that's OT (ask me privately, if anyone cares).
-- Dave, the anti-spammer Unix-loving ageing hippie
next prev parent reply other threads:[~2019-02-04 4:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 15:02 [TUHS] OSI stack (Was: Posters) Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
2019-02-03 23:33 ` [TUHS] Signal/noise (Was: OSI stack (Was: Posters)) Mantas Mikulėnas
2019-02-04 0:10 ` Arthur Krewat
2019-02-04 0:54 ` Grant Taylor via TUHS
2019-02-04 2:23 ` [TUHS] Signal/noise Warren Toomey
2019-02-04 2:37 ` Larry McVoy
2019-02-04 2:57 ` Bakul Shah
2019-02-04 3:26 ` Warner Losh
2019-02-04 3:26 ` Dan Cross
2019-02-04 4:55 ` Dave Horsfall [this message]
2019-02-04 6:20 ` Jon Steinhart
[not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16 ` [TUHS] OSI stack (Was: Posters) Warner Losh
2019-02-06 17:23 ` Larry McVoy
2019-02-06 23:37 ` George Michaelson
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.1902041535470.64931@aneurin.horsfall.org \
--to=dave@horsfall.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).