From: "Henry Mensch" <henry@henare.com>
To: "Henry Mensch" <henry@henare.com>
Cc: TUHS@tuhs.org
Subject: [TUHS] Re: [off-topic] Anyone still using USENET?
Date: Fri, 27 Jan 2023 12:42:43 -0500 [thread overview]
Message-ID: <086b01d93276$c3982c80$4ac88580$@henare.com> (raw)
In-Reply-To: <m24jsbkhbi.fsf@thuvia.hamartun.priv.no>
I'd like to find solid Android and Windows clients so I could once again use USENET. The web interfaces I've seen have been pretty awful for the way I want to use it.
- Henry
-----Original Message-----
From: Tom Ivar Helbekkmo via TUHS <tuhs@tuhs.org>
Sent: 27 January 2023 12:39
To: arnold@skeeve.com
Cc: TUHS@tuhs.org
Subject: [TUHS] Re: [off-topic] Anyone still using USENET?
arnold@skeeve.com writes:
> If anyone has suggestions for a good free NNTP server, please let me
> know.
Not free, but very cheap: I use news.individual.net, run by the Freie Universität Berlin, where the subscription fee is a mere 10 euros/year.
-tih
--
Most people who graduate with CS degrees don't understand the significance of Lisp. Lisp is the most important idea in computer science. --Alan Kay
next prev parent reply other threads:[~2023-01-27 17:43 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 [this message]
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
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='086b01d93276$c3982c80$4ac88580$@henare.com' \
--to=henry@henare.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).