The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Historic "Communications Etiquette" Practices?
Date: Sat, 23 Dec 2023 14:46:34 -0500	[thread overview]
Message-ID: <CABH=_VTBbuKcZj_i2PMbgCVQ6Q+szAZKKRf3WrkUSUPJNpSLcQ@mail.gmail.com> (raw)
In-Reply-To: <Iop9R1VmcIrrpV4FTHilvetZLf2vvp_JSdkhsipAwRyPG0SBBNa-xv-pZQDYhbGGHH9GPqNmHbaR89dwdgd5LhH0dXzJO-zwXkjzTOZhbpc=@protonmail.com>

On 12/23/23, segaloco via TUHS <tuhs@tuhs.org> wrote:
>
> What this has me curious on is if in the early days of UNIX there were
> attempts at suggesting which provided communication mechanisms were
> appropriate for what.

In the early days of Unix and Usenet terminal speeds were very
slow--10 characters/second if you were on an acoustic modem dial-up
line.  Slow line speeds dictated two major communications etiquette
rules:

o Be terse and to the point.  Don't waste your readers' time by being
excessively verbal or by unnecessarily quoting previous posts in the
discussion stream.  And sending an email just to say "thank you" was
considered being rude, not courteous, because you were wasting your
correspondents' time.  Similarly avoid "me too" messages.

This caused quite the culture clash when AOL users were let loose on
Usenet.  AOL charged their customers based on their connect time, and
so they encouraged a culture of excessive (by Unix standards)
verbosity.

o Don't top-post when replying to emails.  You can't scroll down to
see the context of the reply when working on a printing terminal.

-Paul W.

      reply	other threads:[~2023-12-23 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 16:56 [TUHS] " segaloco via TUHS
2023-12-23 19:46 ` Paul Winalski [this message]

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='CABH=_VTBbuKcZj_i2PMbgCVQ6Q+szAZKKRf3WrkUSUPJNpSLcQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=segaloco@protonmail.com \
    --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).