From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 08 May 2018 13:01:27 -0700 [thread overview]
Message-ID: <20180508200135.47C7B156E510@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 08 May 2018 12:00:48 -0700." <alpine.BSF.2.21.1.1805081159390.81704@orthanc.ca>
On Tue, 08 May 2018 12:00:48 -0700 Lyndon Nerenberg <lyndon at orthanc.ca> wrote:
Lyndon Nerenberg writes:
> > 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.
$ echo $NNTPSERVER
news.eternal-september.org
I think you have to register and authenticate when you connect.
I use tin now. Used to use nn in nn-6.4 days. Also used
thunderbird in between. May have used every other reader at
various times.
Back in 1989 timeframe I used to get a pretty complete feed
via uucp and maintain locally with cnews. Recently I tried
using "fetchnews" recently for that purpose (for the groups I
want) since eternal-september is a bit slow but something went
wrong.
next prev parent reply other threads:[~2018-05-08 20:01 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
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 [this message]
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=20180508200135.47C7B156E510@mail.bitblocks.com \
--to=bakul@bitblocks.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).