9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <dodell@offmyserver.com>
To: Jack Johnson <knapjack@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: Tue, 24 May 2005 17:54:34 -0400	[thread overview]
Message-ID: <4293A29A.5070106@offmyserver.com> (raw)
In-Reply-To: <6e35c06205052414317b157a2e@mail.gmail.com>

Jack Johnson wrote:
> On 5/24/05, Dan Cross <cross@math.psu.edu> wrote:
> 
>>Because the data isn't accumulated over time, the damage
>>done by the bad data remains done.  The correction is never applied.
> 
> 
> So, this begs the question, do people using IRC understand this?  If
> so, then the newbie swears, tries again with a new crowd, or tries
> 9fans and waits.  If not, then they assume the software is broken or
> that it will not do what it asks and they give up.

No, they do not. When I first started in there, I was given absolute 
hell and did not understand what everyone's problem was. I've come to 
appreciate that some of that attitude is qualified by being a Plan 9 
user/developer/enthusiast as I have taken some of the mental stances myself.

But I still notice that far too many people (potential developers 
included!) have been scared away by the overzealous ideals and twisted 
advocacy of some individuals.

This has caused me to `indefinitely' leave the channel. At least until I 
noticed it getting better. During this time, I started #Plan-9, which 
was pretty successful at getting people who really wanted to talk about 
Plan 9 to do so in a kind fashion. It still exists, though the 
conversation has moved en masse back to #Plan9.

Surprisingly, it did. I still notice some of the behaviors, but they are 
in general getting better. Unfortunately, I have not been around for the 
last set of quotes that sparked this thread. Normally, I check uriel on 
his statements.

> If I were really concerned about the quality of information on IRC, I
> would donate an hour a week to straightening out the locals or just
> roll an infobot that references the wiki and the mailing list archives
> and let the locals qualify the result with their own $0.02 (though
> possibly not USD).

There are a lot of great minds in #Plan9. Infrequently, I see Ron, 
Andrey and Russ. Other than that, there's usually Vester, Boyd, Steve 
Simon, Tim Newsham, Eric van Hensbergen and myself. I'm probably leaving 
lots of people out; this is simply to give people an idea.

In general, the discussion is good when I'm discussing, simply because 
interesting development / usage issues are being discussed. I tend to 
leave when it gets too hairy. Which is why it's oddly good discussion 
when I'm there ;). (Don't mean to glorify myself one bit).

> Otherwise, I would assume the visitors were looking for easy
> information and that they realize they might not walk away with
> answers.
> 
> -Jack

This is always something to watch out for on IRC, and unfortunately many 
IRC newbies do not understand this.

I'd say it's generally a good place. But you have to know who to watch 
for. Generally that's straightforward, but it can get messy sometimes.

In any case, I think this thread is somewhat moot. IRC is known for its 
crap; I think it just hits us hard because it's such a niche OS (at the 
moment, at least). The best thing to do (in my experience) is say `BS, 
<user>' and drop it. /ignore also works wonders for most clients.

I might petition Freenode to make a ##Plan9 channel per its ridiculous 
`this is not an official project channel' guidelines, but it might help 
users who are new to Freenode (who have read the page / MOTD) to 
understand that it's not an official channel.

Kind regards,

Devon H. O'Dell


  reply	other threads:[~2005-05-24 21:54 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 [this message]
2005-05-26  4:04               ` McLone
2005-05-26  4:19                 ` Devon H. O'Dell
2005-05-26  4:29                 ` Dan Cross
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=4293A29A.5070106@offmyserver.com \
    --to=dodell@offmyserver.com \
    --cc=9fans@cse.psu.edu \
    --cc=knapjack@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).