From: Larry McVoy <lm@mcvoy.com>
To: ama@ugr.es
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: [off-topic] Anyone still using USENET?
Date: Fri, 27 Jan 2023 09:08:36 -0800 [thread overview]
Message-ID: <20230127170836.GG5393@mcvoy.com> (raw)
In-Reply-To: <35180c48b0a162da2a53d8fce1c50a81@ugr.es>
On Fri, Jan 27, 2023 at 06:01:03PM +0100, Angel M Alganza wrote:
> I find the ratio signal/noise of Reddit far too low to use it as a regular
> news source for me. For technical news, there is Hacker News (HN), which in
> place of a voting system, has a tipping system which rewards with small
> amounts of money the more interesting/useful posts and comments.
I left hacker news a few years ago for two reasons:
A) the signal noise ratio, as a systems person, is awful. They talk about
trivial stuff like it is a big deal. There is very little in the way
of interesting stuff there. It all sounds technical until you look
into it, it's 98% fluff.
B) There is some paid(?) schill there who stomps on anyone saying anything
bad about Roundup. Cancer got my dad, he got it from Roundup.
Every time I tried point out I had personal data on the topic (and all
you have to do is google Roundup and cancer and you get a bizillion
law firms who want to represent you), this schill jumped on me.
I complained to the admins and they did nothing, so I left. They
were getting more out of me than I was getting out of that site
so sucks to be them.
On the signal/noise on reddit, /r/news is reasonable and not that
different than Google news other than it shows up on reddit first.
next prev parent reply other threads:[~2023-01-27 17:08 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 [this message]
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
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=20230127170836.GG5393@mcvoy.com \
--to=lm@mcvoy.com \
--cc=ama@ugr.es \
--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).