1999Q1/
<!-- MHonArc v2.4.4 -->
<!--X-Subject: [MUD&#45;Dev] Re: META: list "peerage" -->
<!--X-From-R13: "Ybfgre, Dncu" <exbfgreNbevtva.rn.pbz> -->
<!--X-Date: Wed, 20 Jan 1999 16:06:14 &#45;0800 -->
<!--X-Message-Id: 11A17AA2B9EAD111BCEA00A0C9B41793EDCA40#forest,origin.ea.com -->
<!--X-Content-Type: text/plain -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, [MUD-Dev] Re: META: list "peerage"</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:rkoster#origin,ea.com">
</head>
<body background="/backgrounds/paperback.gif" bgcolor="#ffffff"
      text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000">

  <font size="+4" color="#804040">
    <strong><em>MUD-Dev<br>mailing list archive</em></strong>
  </font>
      
<br>
[&nbsp;<a href="../">Other Periods</a>
&nbsp;|&nbsp;<a href="../../">Other mailing lists</a>
&nbsp;|&nbsp;<a href="/search.php3">Search</a>
&nbsp;]
<br clear=all><hr>
<!--X-Body-Begin-->
<!--X-User-Header-->
<!--X-User-Header-End-->
<!--X-TopPNI-->

Date:&nbsp;
[&nbsp;<a href="msg00222.html">Previous</a>
&nbsp;|&nbsp;<a href="msg00235.html">Next</a>
&nbsp;]
&nbsp;&nbsp;&nbsp;&nbsp;
Thread:&nbsp;
[&nbsp;<a href="msg00236.html">Previous</a>
&nbsp;|&nbsp;<a href="msg00242.html">Next</a>
&nbsp;]
&nbsp;&nbsp;&nbsp;&nbsp;
Index:&nbsp;
[&nbsp;<A HREF="author.html#00223">Author</A>
&nbsp;|&nbsp;<A HREF="#00223">Date</A>
&nbsp;|&nbsp;<A HREF="thread.html#00223">Thread</A>
&nbsp;]

<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>[MUD-Dev] Re: META: list "peerage"</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: "'<A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A>'" &lt;<A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A>&gt;</LI>
<LI><em>Subject</em>: [MUD-Dev] Re: META: list "peerage" </LI>
<LI><em>From</em>: "Koster, Raph" &lt;<A HREF="mailto:rkoster#origin,ea.com">rkoster#origin,ea.com</A>&gt;</LI>
<LI><em>Date</em>: Wed, 20 Jan 1999 18:01:41 -0600</LI>
<LI><em>Reply-To</em>: <A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A></LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
Please forgive the extra layer of attribution, it arose from Caliban having
to repost. Also please forgive the extremely "meta" nature of the post.

&gt; -----Original Message-----
&gt; From: Caliban Tiresias Darklock [<A  HREF="mailto:caliban#darklock,com">mailto:caliban#darklock,com</A>]
&gt; Sent: Wednesday, January 20, 1999 3:02 PM
&gt; To: mud-dev#kanga,nu
&gt; Subject: [MUD-Dev] Re: Levels versus Skills, who uses them and when. 

&gt; Reposting...
&gt; 
&gt; &gt;-----Original Message-----
&gt; &gt;From: J C Lawrence &lt;claw#under,engr.sgi.com&gt;
&gt; &gt;To: mud-dev#kanga,nu &lt;mud-dev#kanga,nu&gt;
&gt; &gt;Date: Thursday, January 14, 1999 10:47 PM
&gt; &gt;Subject: [MUD-Dev] Re: Levels versus Skills, who uses them and when.
&gt; &gt;
&gt; &gt;&gt;At the danger of treading into meta territory, considering MUD-Dev
&gt; &gt;&gt;as a MUD, what of the same danger and problem with the more
&gt; &gt;&gt;established (well known, reputations, etc) posters in MUD-Dev, or
&gt; &gt;&gt;even of myself here?  There is a definate peerage (nod to Lambert)
&gt; &gt;&gt;in the older posters in MUD-Dev.  I find it worrisome.  It also acts
&gt; &gt;&gt;as a significant barrier to entry for new posters.
&gt; &gt;
&gt; &gt;I would think the *biggest* barrier is the need to ask 
&gt; &gt;permission to post.

Yet at the same time, this is what keeps the signal high... 

&gt; &gt;I would have been reluctant to do so, because many of the people here are
Big
&gt; &gt;Names if you pay attention to the industry. (I feel reasonably unworthy
of
&gt; &gt;membership every time Dr. Cat posts.) When the list was invitation only,
you
&gt; &gt;got a nod from someone else first; someone would encourage you and say
hey,
&gt; &gt;it's okay, you'll fit in here, your ideas are good enough for us.

This is an excellent point. It had the feeling of being invited to join the
elite--actually, given how little publicized the list, a feeling of being
invited to join a secret society. Perhaps that minimized the gradual
realization that there was an elite within the elite. Which I think is
fairly apparent, though it took a while for me to realize that many
listmembers considered me to be in said group! (I was somewhat horrified,
albeit gratified, by your "goal of getting into Koster's Laws" remark, you
see).

&gt; &gt;When you have to ask, it immediately puts the list in an exclusionary
light:
&gt; &gt;you must petition the great and powerful Oz for the right to post. When
the
&gt; &gt;great and powerful Oz has people out roaming the world and inviting
&gt; &gt;"compatible" people in, then it's more of a community-building thing.

See now, this peerage, these deputy Ozzes... (Hey JCL, I didn't realize you
were so short, and that you liked green so much...!) it'd be worth analyzing
why they are peers in the first place. Posting volume (a very powerful
factor in this case, IMHO)? Insight? And if insight, insight judged by who?
Number of concepts/approaches/solutions/opinions that evolve into orthodoxy?
Number of times they get cited by others as knowing their shit? Number of
muds they have in the FAQ as "touchstones"?

Little things like saying, "I was trading offlist emails with soNso last
night &amp;..." reinforce the sense of elite (particularly if the soNso is JCL).
Working for a commercial endeavor seems to. If I had to build a peerage
list, I'd pretty quickly dump in names like Chris Gray, Dr Cat, Nathan
Yospe, Jon Lambert, you, Marian Griffith, Ola--and more, but I will stop
now--and I imagine that anyone else building such a list would probably
arrive at a similar list. It's worth asking, how much of the nature of the
list is said people sitting in a room and a lot of people eavesdropping? And
is that the list we want it to be?

&gt; &gt;Can you imagine the agony you'd go through if you were a reasonably young
&gt; &gt;and inexperienced MUD developer with some new ideas who had to compose a
&gt; &gt;post "worthy" of this list?

No, when JCL invited me I was already arrogant and a know-it-all. :) I
suffered no agony. Then again--saying that I was invited (and thus date from
back then) is in itself a marker of elitedom, I bet. I bet that who invited
you is also probably such a marker.

&gt; &gt;People resist change, and familiarity breeds
&gt; &gt;contempt: so the ideas must be fresh enough to interest, yet not so
&gt; &gt;different that they become uncomfortably radical. I could spend weeks
&gt; &gt;composing mail like that.

More frightening: how many list members never post, because they feel that
they cannot compose a mail such as that? It also gets as the issue of what
the nature of the list is. If the list is a research institution (which it
is currently heavily biased towards) then that is fine. You want the
contributors to be those who actively advance or elucidate the state of the
art every time they open their mouth. The danger is that said state of the
art never materializes because we're all too busy talking about it to
actually make it happen. (I seem to recall one poster--was it John
Bertoglio?--who stopped posting last time I made a similar comment, with the
remark, "You're right, I am going to stop talking and start coding now.").
There is also the danger, in a research institution, of getting too far
divorced from reality, and ceasing to be relevant. And of course, there's
all the lovely academic politics that probably ensue, the ossification of
thought processes, the acceptance of assumed orthodoxies, etc.

On the other hand, much of the charm of the list is that it isn't a teaching
institution. I daresay many of the posters would be chased away by countless
inquiries on how to add ANSI color to their mud. (Then again, I bet that a
good thread could probably be generated from, "coolest way to add ANSI color
to a mud, with the most elegant implementation, and the slickest
interface-wise and usability-wise". Is it possible we're too snooty a
research institution to delve into that just because we see ANSI color as a
topic beneath us?)

The problem with NOT being a teaching institution is that the list is
devoted to advancing the state of the art. And it's not going to advance
unless the general caliber of endeavor improves as a result of the
discussions here. At some point, somebody has to turn around and say to the
general mud community, "Hey, you know what? We like, completely LICKED the
problem of &lt;insert topic here--uh, say, proper database backends for muds&gt;
and here's a detailed spec and what's more, you can use it in ANY mud
codebase, check it out!" or else the general mud community will continue to
develop at the current (slow) pace.

&gt; &gt;I don't really have a solution to this, because allowing everyone to read
&gt; &gt;this list is the Right Thing. Allowing everyone to post to it without
&gt; &gt;qualification is the Wrong Thing. 

And arriving at what "qualification" is moved from the hands of the extant
list membership to the hands of the single (highly esteemed) list moderator.
Thereby making a move to open the list to a wider readership actually
resulting in reinforcement of the sense of the elite. Delightfully
paradoxical. :)

&gt; &gt;We can still encourage others to join up,
&gt; &gt;but it's intimidating as hell when you first get here. I felt very much
out
&gt; &gt;of my depth. (Still do, a lot of the time.)

If it is any consolation, I have repeatedly heard from "peerage" people that
they feel the same way. I feel that way regularly (the database discussion
went miles over my head in many places). Then again, here's a separate
dilemma: the peerage right now also seems to be the most active posters. I'd
count YOU as one of said peers, in fact. So even this discussion about how
the peerage dominates the list via intimidation &amp; posting volume is
happening only among the peerage. Maybe the rest of the list doesn't think
it's a problem at all. Lurkers, what do you think?

&gt; &gt;Perhaps the best thing to do is to encourage people reading the archives
not
&gt; &gt;to be afraid of the list. I think most of us were scared of it at some
&gt; &gt;point, but then we realised that everyone else is still sort of lost too.
;)

One problem about reading the archives is that they seem to be a) infallible
b) totally comprehensive and c) easily traced back to the peerage. How many
times have we seen threads die with a "The answer to is in the archives at
this link: http://...."? Now, this is an illusion, because the archives are
not any of those things except (c), usually. Plenty of topics could easily
be taken in new directions, if the stone tablets of the archives weren't
presented as a definitive answer quite so readily.

-Raph


</PRE>

<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<ul compact><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><A NAME="00242" HREF="msg00242.html">[MUD-Dev] Re: META: list "peerage"</A></strong>
<ul compact><li><em>From:</em> &lt;diablo#best,com&gt;</li></ul>
</UL></LI></UL>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00222.html">[MUD-Dev] Re: ADMIN: List server and Kanga.Nu host changes</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00235.html">[MUD-Dev] Re: META: list "peerage"</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00236.html">[MUD-Dev] Re: Graphic design doc</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00242.html">[MUD-Dev] Re: META: list "peerage"</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00223"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00223"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
<ul><li>Thread context:
<BLOCKQUOTE><UL>
<LI><STRONG>[MUD-Dev] Re: Java I/O and threads.</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<LI><strong><A NAME="00265" HREF="msg00265.html">[MUD-Dev] Re: Java I/O and threads.</A></strong>, 
Elis Pomales <a href="mailto:pomales#caip,rutgers.edu">pomales#caip,rutgers.edu</a>, Mon 25 Jan 1999, 21:39 GMT
</LI>
</ul>
</ul>
</LI>
<LI><strong><A NAME="00244" HREF="msg00244.html">[MUD-Dev] ADMIN: We're working again.</A></strong>, 
J C Lawrence <a href="mailto:claw#kanga,nu">claw#kanga,nu</a>, Mon 25 Jan 1999, 01:49 GMT
<LI><strong><A NAME="00237" HREF="msg00237.html">[MUD-Dev] Re: Mugu</A></strong>, 
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Thu 21 Jan 1999, 02:42 GMT
<LI><strong><A NAME="00236" HREF="msg00236.html">[MUD-Dev] Re: Graphic design doc</A></strong>, 
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Thu 21 Jan 1999, 02:31 GMT
<LI><strong><A NAME="00223" HREF="msg00223.html">[MUD-Dev] Re: META: list "peerage"</A></strong>, 
Koster, Raph <a href="mailto:rkoster#origin,ea.com">rkoster#origin,ea.com</a>, Thu 21 Jan 1999, 00:06 GMT
<UL>
<LI><strong><A NAME="00242" HREF="msg00242.html">[MUD-Dev] Re: META: list "peerage"</A></strong>, 
diablo <a href="mailto:diablo#best,com">diablo#best,com</a>, Thu 21 Jan 1999, 04:06 GMT
</LI>
</UL>
<UL>
<li>&lt;Possible follow-up(s)&gt;<br>
<LI><strong><A NAME="00235" HREF="msg00235.html">[MUD-Dev] Re: META: list "peerage"</A></strong>, 
John Bertoglio <a href="mailto:alexb#internetcds,com">alexb#internetcds,com</a>, Thu 21 Jan 1999, 02:25 GMT
</LI>
<LI><strong><A NAME="00238" HREF="msg00238.html">[MUD-Dev] Re: META: list "peerage"</A></strong>, 
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Thu 21 Jan 1999, 03:11 GMT
</LI>
<LI><strong><A NAME="00245" HREF="msg00245.html">[MUD-Dev] Re: META: list "peerage"</A></strong>, 
Travis Casey <a href="mailto:efindel#io,com">efindel#io,com</a>, Mon 25 Jan 1999, 03:22 GMT
</LI>
</UL>
</LI>
</UL></BLOCKQUOTE>

</ul>
<hr>
<center>
[&nbsp;<a href="../">Other Periods</a>
&nbsp;|&nbsp;<a href="../../">Other mailing lists</a>
&nbsp;|&nbsp;<a href="/search.php3">Search</a>
&nbsp;]
</center>
<hr>
</body>
</html>