From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 8 May 2018 13:48:46 -0600 [thread overview]
Message-ID: <cb7bedc9-a9d0-c3d7-785c-4de7fcdd437e@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <00c501d3e702$65f60850$31e218f0$@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
On 05/08/2018 01:26 PM, Ron Natalie wrote:
> I know what killed it, the lack of any real moderation (the moderation
> system was really the honor system).
Are you referring to 3rd party cancel messages and the likes?
I'd swear that I'm subscribed to some moderated newsgroups where posted
articles pass through moderators (algorithm) before being posted to the
newsgroup. — I've not looked at the technology under the hood.
The various mozilla.* newsgroups immediately come to mind.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180508/00540a75/attachment-0001.bin>
next prev parent reply other threads:[~2018-05-08 19:48 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 [this message]
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=cb7bedc9-a9d0-c3d7-785c-4de7fcdd437e@spamtrap.tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
/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).