The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andy Kosela <akosela@andykosela.com>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: [off-topic] Anyone still using USENET?
Date: Sat, 28 Jan 2023 11:15:12 +0100	[thread overview]
Message-ID: <CALMnNGgBGW=jw65SX6hprkiej4_svquopCf3uwdHk=Z7Baxp=w@mail.gmail.com> (raw)
In-Reply-To: <CAK7dMtB8ZWT6_WSaY12Ti_Qo3Z=_fUNHT07+1kY795X+6REjYQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]

On Saturday, January 28, 2023, Kevin Bowling <kevin.bowling@kev009.com>
wrote:

>
>
> On Fri, Jan 27, 2023 at 1:54 AM <arnold@skeeve.com> wrote:
>
>> Hi.
>>
>> I've been using trn for decades to read a very few USENET groups. Until
>> recently I've
>> been using aioe.org as my NNTP server but it seems to have gone dark.
>> Before that
>> I used eternal-september.org, but when I try that I now get:
>>
>> | $ NNTPSERVER=news.eternal-september.org trn
>> | Connecting to news.eternal-september.org...Done.
>> |
>> | Invalid (bogus) newsgroup found: comp.sys.3b1
>> |
>> | Invalid (bogus) newsgroup found: comp.sources.bugs
>> |
>> | Invalid (bogus) newsgroup found: comp.misc
>> |
>> | Invalid (bogus) newsgroup found: comp.compilers
>> | ....
>>
>> And those all are (or were!) valid groups. If anyone has suggestions for
>> a good
>> free NNTP server, please let me know. Privately is fine.  I'm at a bit of
>> a loss otherwise.
>>
>
> I maintain inn and some related ports for FreeBSD.  I run a public server
> at csiph.com and am happy to provide accounts or peering to interested
> parties.  Read access is open.
>
>>
>>
Great initiative and idea! While I am personally not interested in reading
USENET that much nowadays, the concept of providing free, public access to
classic Internet services (public USENET, FTP, IRC, finger, etc.) gets all
my praise. What happened to free, public services these days? Everything
appears to to be subscriber pay-as-you-go based. The commercialization
killed the free spirit of Internet we all loved in the 90s.

PS> And I also love the layout of your website. Plain HTML with no fancy
css, js bloat; classic colors with white background. I miss it on the
Internet. These modern color themes with dark backrounds is getting harder
and harder to read and is just awful if you ask me.

--Andy

[-- Attachment #2: Type: text/html, Size: 2963 bytes --]

  reply	other threads:[~2023-01-28 10:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  8:53 [TUHS] " arnold
2023-01-27  9:03 ` [TUHS] " Lars Brinkhoff
2023-01-27  9:24   ` Ron Natalie
2023-01-27  9:34     ` John Cowan
2023-01-27 16:05     ` Larry McVoy
2023-01-27 17:01       ` Angel M Alganza
2023-01-27 17:08         ` Larry McVoy
2023-01-27 10:36 ` parodper via TUHS
2023-01-27 14:45 ` Ralph Corderoy
2023-01-27 14:51   ` Ron Natalie
2023-01-27 14:56   ` Ron Young via TUHS
2023-01-27 17:39 ` Tom Ivar Helbekkmo via TUHS
2023-01-27 17:42   ` Henry Mensch
2023-01-27 19:23     ` Stuff Received
2023-01-29  9:00   ` arnold
2023-01-28  0:23 ` Kevin Bowling
2023-01-28 10:15   ` Andy Kosela [this message]
2023-01-28 17:01     ` John Cowan

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='CALMnNGgBGW=jw65SX6hprkiej4_svquopCf3uwdHk=Z7Baxp=w@mail.gmail.com' \
    --to=akosela@andykosela.com \
    --cc=kevin.bowling@kev009.com \
    --cc=tuhs@tuhs.org \
    /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).