From: Kevin Bowling <kevin.bowling@kev009.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: [off-topic] Anyone still using USENET?
Date: Fri, 27 Jan 2023 17:23:52 -0700 [thread overview]
Message-ID: <CAK7dMtB8ZWT6_WSaY12Ti_Qo3Z=_fUNHT07+1kY795X+6REjYQ@mail.gmail.com> (raw)
In-Reply-To: <202301270853.30R8rif6014271@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
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.
> Thanks,
>
> Arnold
>
[-- Attachment #2: Type: text/html, Size: 1939 bytes --]
next prev parent reply other threads:[~2023-01-28 0:25 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 [this message]
2023-01-28 10:15 ` Andy Kosela
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='CAK7dMtB8ZWT6_WSaY12Ti_Qo3Z=_fUNHT07+1kY795X+6REjYQ@mail.gmail.com' \
--to=kevin.bowling@kev009.com \
--cc=arnold@skeeve.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).