From: henry.r.bent@gmail.com (Henry Bent)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 8 May 2018 18:22:06 -0400 [thread overview]
Message-ID: <CAEdTPBfoSbh8HygKKB+pABBs8a6P0zsSYyZ6sNpheLtppX=ZcQ@mail.gmail.com> (raw)
In-Reply-To: <990f91e8-01c0-cf25-4889-43e1580398ef@kilonet.net>
My father was the sysadmin for Deja News at the time they were bought by
Google. I was told that the "buyout" consisted of some Google folks
showing up with a rack of drives, dumping all of Deja News's data over a
weekend, and then flying back out to Mountain View.
-Henry
On 8 May 2018 at 15:11, Arthur Krewat <krewat at kilonet.net> wrote:
> On 5/8/2018 3:00 PM, Lyndon Nerenberg wrote:
>
>> The problem is, many of us have stopped using it for whatever reason, and
>>> certainly don't store/forward much.
>>>
>>> Maybe it's time to take it back and get back to the original intention
>>> of USENET.
>>>
>>
>> So where on Earth does one get an NNTP feed from these days? Lord knows
>> I've tried. An no, I'm not talking about a pay-for-access NNRP host that I
>> have to pull things from.
>>
>> That was going to be my next question ;) - Google has the entire archive
> (minus binaries), and most commercial places have it going back only 3000
> days or so.
>
> Where's Deja News when you need 'em.
>
>
> ak
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180508/9b6862b7/attachment.html>
next prev parent reply other threads:[~2018-05-08 22:22 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 16:25 Seth Morabito
2018-05-08 16:36 ` Larry McVoy
2018-05-08 16:43 ` Warner Losh
2018-05-08 17:06 ` arnold
2018-05-08 17:27 ` Dan Cross
2018-05-08 17:42 ` Andy Kosela
2018-05-08 21:27 ` [TUHS] Old Usenet / local communitites Mike Markowski
2018-05-08 17:53 ` [TUHS] Old Usenet newsreader source code? Seth Morabito
2018-05-08 18:28 ` Grant Taylor
2018-05-08 18:35 ` Arthur Krewat
2018-05-08 18:45 ` Warner Losh
2018-05-08 19:00 ` Lyndon Nerenberg
2018-05-08 19:09 ` Grant Taylor
2018-05-08 19:11 ` Arthur Krewat
2018-05-08 21:50 ` Grant Taylor
2018-05-08 21:54 ` Larry McVoy
2018-05-08 21:58 ` Grant Taylor
2018-05-08 22:22 ` Henry Bent [this message]
2018-05-08 22:32 ` Arthur Krewat
2018-05-08 22:59 ` Henry Bent
2018-05-09 2:01 ` Michael Parson
2018-05-09 1:55 ` Michael Parson
2018-05-08 20:01 ` Bakul Shah
2018-05-08 21:56 ` Grant Taylor
2018-05-08 20:54 ` Lyndon Nerenberg
2018-05-08 19:05 ` Grant Taylor
2018-05-08 19:15 ` Arthur Krewat
2018-05-08 19:35 ` Grant Taylor
2018-05-08 19:23 ` Steve Nickolas
2018-05-08 19:29 ` Grant Taylor
2018-05-09 0:46 ` Steve Nickolas
2018-05-08 19:26 ` Ron Natalie
2018-05-08 19:48 ` Grant Taylor
2018-05-08 20:54 ` Daniel Camolês
2018-05-08 22:55 ` Grant Taylor
2018-05-08 23:16 ` Lyndon Nerenberg
2018-05-08 23:18 ` Henry Bent
2018-05-08 23:21 ` George Michaelson
2018-05-08 23:25 ` Grant Taylor
2018-05-08 23:22 ` Grant Taylor
2018-05-08 23:37 ` Grant Taylor
2018-05-09 0:54 ` Steve Nickolas
2018-05-08 17:09 ` Clem Cole
2018-05-08 16:53 ` Arthur Krewat
2018-05-08 17:01 ` Seth Morabito
2018-05-08 19:41 ` Dave Horsfall
2018-05-08 21:49 ` Jeremy C. Reed
2018-05-08 23:39 ` John Labovitz
2018-05-09 0:08 ` Jeremy C. Reed
2018-05-09 0:11 ` Jeremy C. Reed
2018-05-09 0:42 ` Warren Toomey
2018-05-09 0:31 ` 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='CAEdTPBfoSbh8HygKKB+pABBs8a6P0zsSYyZ6sNpheLtppX=ZcQ@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
/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).