From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: [TUHS] Re: [off-topic] Anyone still using USENET?
Date: Fri, 27 Jan 2023 14:45:52 +0000 [thread overview]
Message-ID: <20230127144552.7E3F12135B@orac.inputplus.co.uk> (raw)
In-Reply-To: <202301270853.30R8rif6014271@freefriends.org>
Hi Arnold,
> I've been using trn for decades
Very fond memories of trn(1). In comparison, I've never seen a web
interface, e.g. for RSS reading, be so geared towards the user and his
likely actions whilst also allowing for powerful expression.
> to read a very few USENET groups.
Bringing it back to heritage, I was wondering about Usenet the other
day. Deja News was excellent, Google Groups is pitiful. A good search
of a comprehensive, historic Usenet archive would be useful from the
TUHS side, but I expect modern analysis means it would also be
interesting to those wanting cultural analysis of a subset of the public
in earlier decades.
Henry Spencer's UTZOO archive is available. Sites like
https://www.usenetarchives.com have used it in the past, but none I know
of are well maintained. In part, anything popular would attract legal
requests for posts to be taken down; IIRC that's why archive.org took
down their official copy of UTZOO.
But the data is so small by modern standards, perhaps a self-hosted
searcher is a way forward.
--
Cheers, Ralph.
next prev parent reply other threads:[~2023-01-27 14:46 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 [this message]
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
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=20230127144552.7E3F12135B@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--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).