From: johnl@johnlabovitz.com (John Labovitz)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 8 May 2018 19:39:00 -0400 [thread overview]
Message-ID: <81216ABB-D4DF-4A63-B26D-6DB2A5428E1F@johnlabovitz.com> (raw)
In-Reply-To: <1525796737.680198.1365037152.60B79FDC@webmail.messagingengine.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On May 8, 2018, at 12:25 PM, Seth Morabito <web at loomcom.com> wrote:
> As an aside: If you were active on Usenet in 1989, what software were you using?
Maybe a bit earlier — 1985–1987? — but I always loved Kenneth Almquist’s ‘vnews’ as a newsreader. There was something incredibly simple and graceful about it. It was curses-based, but at the same time very Unix-y — no BBS-like prompts or extra noise. Minimal and perfect. Many times I’ve tried to build a similar interface on modern systems, and it’s harder than one would think.
A few years back I found a shar file of some late vnews distribution. (Sadly, I can’t find a link now — but have the sources if anyone wants.) I was surprised how complicated the C code was, not to mention the build system! No blame to Almquist at all — I’d simply forgotten how difficult it was in the ‘80s to architect software that could work on more than one Unix distribution.
I ran vnews, and I think C news, on a Parallel XR300 machine, which was (in theory) a fault-tolerant box with Sun motherboards. That was in Maryland — I was psc!jsl.
—John
next prev parent reply other threads:[~2018-05-08 23:39 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
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 [this message]
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=81216ABB-D4DF-4A63-B26D-6DB2A5428E1F@johnlabovitz.com \
--to=johnl@johnlabovitz.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).