9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: McLone <mclone@gmail.com>,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] the futility of #plan9 on irc
Date: Thu, 26 May 2005 00:29:05 -0400	[thread overview]
Message-ID: <20050526042905.GA22273@augusta.math.psu.edu> (raw)
In-Reply-To: <451cb301050525210456f27637@mail.gmail.com>

On Thu, May 26, 2005 at 07:04:24AM +0300, McLone wrote:
> /msg memoserv help

I have no idea what that does.  Evidently, it sends a help request
message to some sort of `bot' that can serve memos (that much is
obvious); perhaps you're implying that you can use this as a way to
implement a FAQ listing.  Regardless, I don't see how it addresses my
point:  In the IRC model, if you get bad data, you have significantly
less chance of getting a correction if you don't stick around and
monitor future traffic to pick it out.  If someone who doesn't know the
answer isn't monitoring, you have no chance of getting a correction,
unless people sit around and read IRC logs and go back and post
corrections to questions asked in the past and unrelated to the current
topic(s) of discussion in the channel (that's another thing about IRC:
you don't get threading in the robust way you do with a mailing list or
even, God Forbid, USENET Newsgroups).

And then you're back to waiting around until someone who knows what
they're talking about sees the request, which is the same situation you
have with 9fans.  Or somebody says, ``ask the bot....'' and you spend
time figuring out how, but even then the bot may not be programmed with
the answer to YOUR question.  You might as well read the Wiki instead.

	- Dan C.



  parent reply	other threads:[~2005-05-26  4:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 11:27 Russ Cox
2005-05-23 12:18 ` Vester Thacker
2005-05-23 17:44   ` Bruce Ellis
2005-05-23 17:46     ` Rob Pike
2005-05-23 18:43       ` Tim Newsham
2005-05-24  4:41     ` Dan Cross
2005-05-23 12:22 ` Uriel
2005-05-23 15:55   ` jmk
2005-05-24  0:54   ` Country Joe
2005-05-23 23:33 ` Chris Collins
2005-05-23 23:57   ` andrey mirtchovski
2005-05-24  0:03     ` Eric Van Hensbergen
2005-05-24  0:12       ` andrey mirtchovski
2005-05-24  4:29       ` Tim Newsham
2005-05-24 15:19         ` Russ Cox
2005-05-24 16:39           ` Vester Thacker
2005-05-24 16:43             ` William Josephson
2005-05-24 17:08               ` Vester Thacker
2005-05-26  4:02               ` McLone
2005-06-19 11:41             ` Vester Thacker
2005-06-19 11:43               ` Vester Thacker
2005-05-24 21:07           ` Chris Collins
2005-05-24 21:18             ` Russ Cox
2005-05-25 16:42               ` David Leimbach
2005-05-25 16:58                 ` Bruce Ellis
2005-05-26  9:17                 ` Abhey Shah
2005-05-24 21:20             ` Dan Cross
2005-05-24 21:31               ` Jack Johnson
2005-05-24 21:54                 ` Devon H. O'Dell
2005-05-26  4:04               ` McLone
2005-05-26  4:19                 ` Devon H. O'Dell
2005-05-26  4:29                 ` Dan Cross [this message]
2005-05-24  4:46       ` Dan Cross
2005-05-24  5:29         ` Lucio De Re
2005-05-24  0:14   ` Skip Tavakkolian

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=20050526042905.GA22273@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --cc=9fans@cse.psu.edu \
    --cc=mclone@gmail.com \
    /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).