The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 8 May 2018 15:23:07 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.02.1805081521210.83706@frieza.hoshinet.org> (raw)
In-Reply-To: <1b32c1a7-69ae-6593-cd01-156f15b87edc@spamtrap.tnetconsulting.net>

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

On Tue, 8 May 2018, Grant Taylor via TUHS wrote:

> On 05/08/2018 12:35 PM, Arthur Krewat wrote:
>> USENET as an entity is still alive and well.
>
> Indeed.  Some might argue that there's a resurgence of Usenet servers. I'm 
> just one example that's has decided to run a text only news server. I see 
> more of them every year.
>
>> The reason for it might be sharing of warez and porn,
>
> I personally don't object to content leveraging the Usenet infrastructure, 
> *as* *long* *as* *it's* *legal*.
>
> I can personally decide if I want to partake / consume in content or not.  — 
> Obviously my text only news server does not partake in non-textual content.
>
>> but for example, alt.sys.pdp10 still exists
>
> Yep.
>
> I'm showing 164 messages since October 10th 2017.
>
> % ls -1 /var/spool/news/articles/alt/sys/pdp10 | wc -l
> 164
> % ls -l /var/spool/news/articles/alt/sys/pdp10 | grep 2017
> -rw-rw-r-- 1 news news 1463 Oct 10  2017 1
>
>> The problem is, many of us have stopped using it for whatever reason, and 
>> certainly don't store/forward much.
>
> Fair.
>
> I wonder how different things would be if various web applications leveraged 
> Usenet (NNTP) (or IMAP) as a back end storage for things like blogs / forums.
>
>> Maybe it's time to take it back and get back to the original intention of 
>> USENET.
>
> I question if there is really anything to take back.  I was active in 
> comp.mail.sendmail for years and then stopped when I changed jobs.  All I had 
> to do was subscribe my news reader and continue like nothing ever changed. 
> (Save for the smaller amount of content in said newsgroup these days.)

:(

> I've personally run small news servers with ~10 peers twice.  One time years 
> ago, and again now I have two news servers.  One is on my VPS with a bunch of 
> peers and the other is in my house that only peers with my VPS.
>
> If anyone wants to get back into the game, let me know and I'll happily peer 
> with you.

I've thought of running a usenet server or servers - I've got a few 
servers - but I don't even know about software to do so, let alone servers 
to peer with.

> I think that "take back" really directly translates to "use again".

I've never really stopped. xD

-uso.


  parent reply	other threads:[~2018-05-08 19:23 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 [this message]
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=alpine.BSF.2.02.1805081521210.83706@frieza.hoshinet.org \
    --to=usotsuki@buric.co \
    /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).