The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 8 May 2018 16:55:31 -0600	[thread overview]
Message-ID: <d569f4c8-fe39-b220-3313-07b3be365ebf@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAM4FNSvrv-FGPFTywEj1YyFyYGvh_10ngXaBb0R1ae9UY92rCQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2900 bytes --]

On 05/08/2018 02:54 PM, Daniel Camolês wrote:
> I got in quite late in the game, in 2001, but as of today I still 
> remember it as the best way to discuss over the internet that I have 
> experienced. I agree on the lack of moderation being the weakness that 
> made the noise surpass the signal. All the web forum software that 
> surfaced on the 00's and beyond was mostly a response to that. If it 
> weren't for this weakness, people nowadays would probably be using web 
> interfaces to nntp just like they do to email, and we old farts could 
> still be happily using our preferred news clients.

As much as I want to agree with you, I think that the stand alone 
islands still would have gotten more popular than Usenet at least for 
the following reason:

1)  Web sites can control what the site looks like, thus the GUI people 
can fiddle to their hearts content.
2)  It's much simpler to build some random database to hold comments for 
a web forum than it is to comply with / inter operate with / adhere to 
(arguably simple) standards.

> So while I applaud the ones who are trying to keep the system alive, 
> this weakness (and maybe others), if not addressed, will pose a natural 
> limit to Usenet growth and quality. If we start putting servers up and 
> manage to attract good contributors back, the spam will follow and then 
> the noise will drive them away again.

I don't know how many people can be brought back to Usenet.  Further, I 
don't know how many people I want brought back to Usenet.

IMHO Usenet works for those that want it to work.  It provides the 
desired service and is IMHO just obscure enough that the mainstream is 
not on it.  I'm cool with that.

> But yet, we are at such a point where bandwidth and storage is so cheap 
> that reviving Usenet could be accomplished by a bunch of hobbists 
> spending little money. If at least we could solve the moderation 
> weakness. Does someone have any idea if there were any attempts at 
> cracking this problem that were open source and effective?

I think there are a number of people / hobbyists that run (text only) 
news servers (like myself) doing exactly that.

I think there are some efforts at reducing spam and making moderation 
work.  I don't know any details about them.

I think that we need to hold server operators accountable for people 
that post crap through them.  I routinely see lots of crap posted to 
specific Linux newsgroups, and almost all of it passes through a 
specific server (network).  Just about the time that I get motivated to 
contact the abuse contact, the crap stops.



-- 
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/a8c2da37/attachment.bin>


  reply	other threads:[~2018-05-08 22:55 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 [this message]
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=d569f4c8-fe39-b220-3313-07b3be365ebf@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).