From: Greg Hudson ghudson@mit.edu
Subject: 9fans <-> comp.os.plan9
Date: Thu, 8 May 1997 14:16:35 -0400 [thread overview]
Message-ID: <19970508181635.ex9BOOoBpVN6zBJbOdrEkvI3sjqyJd3V5uxj0sJtZI0@z> (raw)
Sorry for the meta-discussion; I'll say one thing about it and shut
up.
> Is the pain of the occasional usenet spam worth the trade-off? To
> me, most definitely not.
I have three arguments against.
* I get "the occasional usenet spam" from a bunch of different
lists these days, to the point where it's no longer
"occasional."
* 9fans is not a high-traffic list right now, and it has a
comparatively good S/N ratio; one or two spam messages a
week is enough to damage that.
* Newsgroups also tend to have a higher level of clueless
questions.
Most of the mailing lists I'm on which are gatewayed to usenet groups
have a much lower S/N ratio than they did before the gateway was set
up. I know that from a technical point of view they're just two
different ways of reading the same stuff, but socially the entrance
barrier to joining a mailing list is a big deal.
next reply other threads:[~1997-05-08 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-08 18:16 Greg [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-05-08 18:55 forsyth
1997-05-08 17:58 Rich
1997-05-08 17:46 Scott
1997-05-08 16:56 Icarus
1997-05-08 16:30 G.David
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=19970508181635.ex9BOOoBpVN6zBJbOdrEkvI3sjqyJd3V5uxj0sJtZI0@z \
--to=9fans@9fans.net \
/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).