From: Bakul Shah <bakul@bitblocks.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Steve Bellovin recounts the history of USENET
Date: Wed, 20 Nov 2019 19:58:50 -0800 [thread overview]
Message-ID: <20191121035858.125CA156E9F9@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 20 Nov 2019 19:52:46 -0800." <20191121035246.GJ23794@mcvoy.com>
On Wed, 20 Nov 2019 19:52:46 -0800 Larry McVoy <lm@mcvoy.com> wrote:
Larry McVoy writes:
> On Wed, Nov 20, 2019 at 07:50:53PM -0800, Bakul Shah wrote:
> > On Wed, 20 Nov 2019 19:14:23 -0800 Larry McVoy <lm@mcvoy.com> wrote:
> > > Yeah, I'd be super happy if he joined the list. I enjoyed reading
> > > those, wished he had gone into more detail.
> > >
> > > On the Usenet topic, does anyone remember dejanews? Searchable
> > > archive of all the posts to Usenet. Google bought them and then,
> > > so far as I know, the searchable part went away.
> > >
> > > If someone knows how to search back to the beginnings of Usenet,
> > > my early tech life is all there, I'd love to be able to show my kids
> > > that. Big arguing with Mash on comp.arch, following Guy Harris on
> > > comp.unix-wizards, etc.
> >
> > I have occasionally downloaded some mbox.zip files from
> > https://archive.org/details/usenet
> > But there are too many files there. Would be nice if there
> > was a collaborative effort to organize them in a more usable,
> > searchable state. Pretty much all of it (minus binaries
> > groups) can be stored locally (or using some global
> > namespace.
>
> So is that all of Usenet?
Probably not. Too many files to check but I think most or all
of dejanews stuf is there.
next prev parent reply other threads:[~2019-11-21 3:59 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
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 [this message]
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=20191121035858.125CA156E9F9@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=lm@mcvoy.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).