The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: George Michaelson <ggm@algebras.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Steve Bellovin recounts the history of USENET
Date: Wed, 20 Nov 2019 19:28:32 -0800	[thread overview]
Message-ID: <20191121032832.GD23794@mcvoy.com> (raw)
In-Reply-To: <CAKr6gn2jeiGpziCmObXBWAgujEFeyOqFJ=0uYu4wg2Z-ZWH3Zw@mail.gmail.com>

On Thu, Nov 21, 2019 at 11:18:10AM +0800, George Michaelson wrote:
> there is a big US bias in the archives of USENET. All I could find
> preserved (before Google deleted it) was my updates to the maps for
> York.ac.uk. In collecting history, the US erased most of Europe and
> Asia basically.  Our timelines are artificially compressed into the
> modern era.

Can you explain this a bit?  When I was on Usenet, 1980-1990 or so, it
was very small, my guess is maybe 10,000 people that posted, maybe less.
My memory is I could post a question to comp.arch or where ever, and I'd
wake up in the morning and someone from Australia or some other place
over the pond had an answer.  It was usually a grad student or a prof
or someone really smart.

So is this an archive thing?  Because in my memory, it was not a Usenet
thing, smart people from all over the world posted.

As an aside, I remember being on a canoe with my dad, a physics researcher
and prof, and trying to explain Usenet to him.  I said something like
"it is so cool Dad, so many cool people, everyone should be on it".  And
then AOL happened and it went to shit.  If my thoughts helped that along
I am _so_ sorry.  It was awesome when it was small.

This list is sort of like early Usenet, smart people, people who know the
history.  Lets keep it small but Steve should be here.

--lm

  reply	other threads:[~2019-11-21  3:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 19:01 Arnold Robbins
2019-11-21  3:14 ` Larry McVoy
2019-11-21  3:18   ` George Michaelson
2019-11-21  3:28     ` Larry McVoy [this message]
2019-11-21  8:56       ` George Michaelson
2019-11-21  9:40         ` Bakul Shah
2019-11-21  9:51           ` George Michaelson
2019-11-21 11:16         ` Arrigo Triulzi
2019-11-21  3:34   ` reed
2019-11-21  3:39     ` Larry McVoy
2019-11-21  3:40   ` Chet Ramey
2019-11-21  3:42     ` Larry McVoy
2019-11-21  3:50       ` Chet Ramey
2019-11-21  3:51         ` Larry McVoy
2019-11-21  3:58           ` Steve Nickolas
2019-11-21  3:50   ` Bakul Shah
2019-11-21  3:52     ` Larry McVoy
2019-11-21  3:58       ` Bakul Shah
2019-11-21 20:36   ` Dave Horsfall
2019-11-24  2:19   ` Michael Parson
2019-11-21 12:46 Jason Stevens
2019-11-21 13:23 ` arnold
2019-11-21 13:31   ` Jason Stevens
2019-11-21 15:58   ` Leah Neukirchen
2019-11-22 20:18     ` Justin R. Andrusk
2019-11-22 20:49       ` Henry Bent
2019-11-22 21:06         ` Kurt H Maier
2019-11-22 21:32           ` Larry McVoy
2019-11-23  1:48             ` Jason Stevens
2019-11-23  3:45               ` Larry McVoy
2019-11-23  4:42                 ` Warren Toomey
2019-11-22 22:21           ` Henry Bent
2019-11-23  0:00             ` Kurt H Maier
2019-11-23  1:36               ` Theodore Y. Ts'o
2019-11-22 23:21       ` Arthur Krewat
2019-11-23  1:32         ` Justin R. Andrusk
2019-11-23 22:25           ` Arthur Krewat
2019-11-21 17:22 ` Tomasz Rola

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=20191121032832.GD23794@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=ggm@algebras.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).