<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Great Failure of Wikipedia</title>
	<atom:link href="http://ascii.textfiles.com/archives/808/feed" rel="self" type="application/rss+xml" />
	<link>http://ascii.textfiles.com/archives/808</link>
	<description>Jason Scott's Weblog</description>
	<lastBuildDate>Sat, 21 Nov 2009 20:59:02 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: EVALS TEN</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2842</link>
		<dc:creator>EVALS TEN</dc:creator>
		<pubDate>Thu, 13 Jan 2005 05:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2842</guid>
		<description>&lt;strong&gt;è‰æ ¹ã€ç«‹å ´ã€çƒæ‰˜é‚¦&lt;/strong&gt;

YahooçŸ¥è­˜+å‰›ä¸Šç·šæ¸¬è©¦æ™‚ï¼ŒScheeæ›¾èªª&quot;bloggerå€‘å¯ä»¥è¶betaéšŽæ®µï¼Œä¸€èˆ‰å¤§å¹…æ”»å…‹å¥‡æ‘©çŸ¥è­˜é »é“&quot;ã€‚ éŽäº†ä¸€å€‹åŠæœˆï¼Œä¸çŸ¥é“æœ‰æ²’æœ‰å“ªä½bloggeræˆç‚ºçŸ¥è­˜åäººï¼Ÿæˆ–æ˜¯æœ‰å“ªä½çŸ¥è­˜åäººæœ‰åœ¨å¯«blogï¼Ÿ æˆ‘è¦ºå¾—é™¤äº†Ri...
</description>
		<content:encoded><![CDATA[<p><strong>è‰æ ¹ã€ç«‹å ´ã€çƒæ‰˜é‚¦</strong></p>
<p>YahooçŸ¥è­˜+å‰›ä¸Šç·šæ¸¬è©¦æ™‚ï¼ŒScheeæ›¾èªª&#8221;bloggerå€‘å¯ä»¥è¶betaéšŽæ®µï¼Œä¸€èˆ‰å¤§å¹…æ”»å…‹å¥‡æ‘©çŸ¥è­˜é »é“&#8221;ã€‚ éŽäº†ä¸€å€‹åŠæœˆï¼Œä¸çŸ¥é“æœ‰æ²’æœ‰å“ªä½bloggeræˆç‚ºçŸ¥è­˜åäººï¼Ÿæˆ–æ˜¯æœ‰å“ªä½çŸ¥è­˜åäººæœ‰åœ¨å¯«blogï¼Ÿ æˆ‘è¦ºå¾—é™¤äº†Ri&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Range Librarian</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2841</link>
		<dc:creator>Free Range Librarian</dc:creator>
		<pubDate>Tue, 04 Jan 2005 04:08:22 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2841</guid>
		<description>&lt;strong&gt;Wikipedia&#039;s Reality Check&lt;/strong&gt;

The responses from some corners of the Wikipedia community were predictable when Larry Stanger, part of the team that developed Wikipedia, published a long article on kuro5shin arguing that &quot;anti-elitism&quot; and &quot;trolls&quot; were undermining this user-contrib...
</description>
		<content:encoded><![CDATA[<p><strong>Wikipedia&#8217;s Reality Check</strong></p>
<p>The responses from some corners of the Wikipedia community were predictable when Larry Stanger, part of the team that developed Wikipedia, published a long article on kuro5shin arguing that &#8220;anti-elitism&#8221; and &#8220;trolls&#8221; were undermining this user-contrib&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: º£±ßµÄ±´¿Ç</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2840</link>
		<dc:creator>º£±ßµÄ±´¿Ç</dc:creator>
		<pubDate>Sun, 02 Jan 2005 12:53:39 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2840</guid>
		<description>&lt;strong&gt;Á½¸öÅúÆÀÒâ¼û&lt;/strong&gt;

&lt;p&gt;Ëæ×ÅÎ¬»ù°Ù¿ÆÔÚ2004ÄêµÄÓ°Ïì³ÖÐøÀ©´ó£¬¹«ÖÚ¿ªÊ¼¸ü¶àµØ¹Ø×¢Õâ¸ö¼Æ»®¡£ÔÚÐí¶àÈËÃÇ¸øÓèÈÏÍ¬µÄÍ¬Ê±£¬Ò²ÓÐÒ»Ð©ÈËÌá³öÁËËûÃÇÅúÆÀµÄÒâ¼û¡£Î¬»ù°Ù¿ÆÊÇÒ»¸öÐÂÉúµÄÊÂÎï£¬¶Ì¶ÌµÄÈý¡¢ËÄÄê£¬ÕâÖÖÈºÌå´´×÷µÄ·½Ê½Õ¹ÏÖ³öÁËËüµÄÉúÃüÁ¦¡£µ«Î¬»ù°Ù¿ÆÏÂÒ»²½¾¿¾¹ÔõÃ´Òª³É³¤ÎªÒ»¸öÔõÑùµÄÊÂÎï£...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>Á½¸öÅúÆÀÒâ¼û</strong></p>
<p>Ëæ×ÅÎ¬»ù°Ù¿ÆÔÚ2004ÄêµÄÓ°Ïì³ÖÐøÀ©´ó£¬¹«ÖÚ¿ªÊ¼¸ü¶àµØ¹Ø×¢Õâ¸ö¼Æ»®¡£ÔÚÐí¶àÈËÃÇ¸øÓèÈÏÍ¬µÄÍ¬Ê±£¬Ò²ÓÐÒ»Ð©ÈËÌá³öÁËËûÃÇÅúÆÀµÄÒâ¼û¡£Î¬»ù°Ù¿ÆÊÇÒ»¸öÐÂÉúµÄÊÂÎï£¬¶Ì¶ÌµÄÈý¡¢ËÄÄê£¬ÕâÖÖÈºÌå´´×÷µÄ·½Ê½Õ¹ÏÖ³öÁËËüµÄÉúÃüÁ¦¡£µ«Î¬»ù°Ù¿ÆÏÂÒ»²½¾¿¾¹ÔõÃ´Òª³É³¤ÎªÒ»¸öÔõÑùµÄÊÂÎï£&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Scott</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2837</link>
		<dc:creator>Jason Scott</dc:creator>
		<pubDate>Wed, 24 Nov 2004 01:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2837</guid>
		<description>Well, there&#039;s something you&#039;re fighting against here, and that&#039;s where the real problems are, if an &quot;alternative solution&quot; is proposed.

Wikipedia is, fundamentally, founded on anarchist/communist principles, which propose that people working as a collective will be stronger than whacko individualists locking out the people and controlling all the toys for themselves. Any divergence from these principles immediately lose the kind of people who are deeply into Wikipedia.

That is, once you start adding these barriers to entry, then come the natural concerns about elitism, the belief that &quot;they&quot; will pull the power in for &quot;themselves&quot;, and in most ways, that people will be shut out of &quot;the club&quot;. And since this openness, this very thing I claim turns the endeavor to crap, is what the whole project is &lt;i&gt;founded on&lt;/i&gt;, I just don&#039;t see reconcilliation.

As it is, my pages are actually sort of a collaboration. If you look at my &lt;a href=&quot;http://software.bbsdocumentary.com&quot; rel=&quot;nofollow&quot;&gt;BBS Software&lt;/a&gt; page, it is the result of dozens of people mailing me software and suggestions and stories, and I implement them with attribution. But this wouldn&#039;t be acceptable by Wiki standards, nor should it.

I should mention that I&#039;ve actually spent several years doing work for an organization, using software that is, basically, a Wiki. However, there&#039;s only about 12 of us with access, and of the 12 maybe 6 are frequent contributors... And I thought this is how they all were. We just didn&#039;t get in each others&#039; way. It was quite a shock to be on Wikipedia.

So I don&#039;t know if I&#039;m helping here. I would say that Wikipedia is definitely advancing on one side: the software that allows people to work on the same bits of data without stepping on each other in more mundane hey-where-the-hell-is-my-paragraph version control issues. And guess what... that software is maintained by a very small amount of people compared to the users, who submit their changes to them.
</description>
		<content:encoded><![CDATA[<p>Well, there&#8217;s something you&#8217;re fighting against here, and that&#8217;s where the real problems are, if an &#8220;alternative solution&#8221; is proposed.</p>
<p>Wikipedia is, fundamentally, founded on anarchist/communist principles, which propose that people working as a collective will be stronger than whacko individualists locking out the people and controlling all the toys for themselves. Any divergence from these principles immediately lose the kind of people who are deeply into Wikipedia.</p>
<p>That is, once you start adding these barriers to entry, then come the natural concerns about elitism, the belief that &#8220;they&#8221; will pull the power in for &#8220;themselves&#8221;, and in most ways, that people will be shut out of &#8220;the club&#8221;. And since this openness, this very thing I claim turns the endeavor to crap, is what the whole project is <i>founded on</i>, I just don&#8217;t see reconcilliation.</p>
<p>As it is, my pages are actually sort of a collaboration. If you look at my <a href="http://software.bbsdocumentary.com" rel="nofollow">BBS Software</a> page, it is the result of dozens of people mailing me software and suggestions and stories, and I implement them with attribution. But this wouldn&#8217;t be acceptable by Wiki standards, nor should it.</p>
<p>I should mention that I&#8217;ve actually spent several years doing work for an organization, using software that is, basically, a Wiki. However, there&#8217;s only about 12 of us with access, and of the 12 maybe 6 are frequent contributors&#8230; And I thought this is how they all were. We just didn&#8217;t get in each others&#8217; way. It was quite a shock to be on Wikipedia.</p>
<p>So I don&#8217;t know if I&#8217;m helping here. I would say that Wikipedia is definitely advancing on one side: the software that allows people to work on the same bits of data without stepping on each other in more mundane hey-where-the-hell-is-my-paragraph version control issues. And guess what&#8230; that software is maintained by a very small amount of people compared to the users, who submit their changes to them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wibble</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2839</link>
		<dc:creator>Wibble</dc:creator>
		<pubDate>Wed, 24 Nov 2004 01:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2839</guid>
		<description>&lt;strong&gt;Worse is easier&lt;/strong&gt;

The ever brilliant Jason Scott has a ather long rant up on his site about collaborative writing, and the effect it has on quality of content. This is something I&#039;ve come up against so many times on the KDE docs....
</description>
		<content:encoded><![CDATA[<p><strong>Worse is easier</strong></p>
<p>The ever brilliant Jason Scott has a ather long rant up on his site about collaborative writing, and the effect it has on quality of content. This is something I&#8217;ve come up against so many times on the KDE docs&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: milli@kaewth</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2836</link>
		<dc:creator>milli@kaewth</dc:creator>
		<pubDate>Mon, 22 Nov 2004 20:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2836</guid>
		<description>My comments are aimed at questioning throwing out the proverbial baby with the dirty water. I realize you&#039;ve made your choice, and you are entitled to it. I&#039;m hoping you&#039;d like to help others out who are dealing with these problems even though you&#039;ve chosen to wash your hands of the baby with the dirty water, or something like that.

I really liked Kevin&#039;s idea:
&quot;I think one start is mostly unlimited viewing access for most general content while having a hierarchy of users which limit modification of content or at the very least have a moderated approval process of content. I think there&#039;s still a place for limited access to viewing and editing certain content before it&#039;s released for general consumption.&quot;

That would help. And maybe a more broadly-conceived and regulated page-locking policy, even though page-locking is not a good habit and kind of goes against the whole principle.

Can you think of other improvements that would benefit, if not Wikipedia, other collaborative projects that are using Wikipedia as a guide?

Obviously the NPOV doesn&#039;t effectively attend to &quot;people [who] make little empires, have their agendas, push through ideas and themes they want, and disregard and delete things they do not&quot; or to vandals. As you said, it&#039;s more like a weapon than a guideline.  Maybe a NPOV commission or system instead of delete-first-blame-later?

What about something that can accommodate individualist researchers, like a project manager who has demonstrated a level of knowledge receives help and can opt to refuse help on their locked pages? I don&#039;t really see why it has to be &quot;Collaborate or Die&quot; in Wiki land. Can&#039;t we have the best of both worlds?

The copyright problem is probably something that Wikipedia is experiencing now more acutely, since copyright is just this big, big problem with any cultural creation now.

Some forums have &quot;newbie&quot; or some ranking system which could locate people who don&#039;t have anything invested in the project. I wonder if that could be implemented in the software somehow to (passively or silently) deal with the problems you&#039;re bringing up.

I&#039;m also wondering if these problems are limited to Wikipedia&#039;s controversial pages or if it is a problem system-wide.

Sorry if I&#039;m blasting questions here, just trying to learn more about collaborative projects in general.

Thanks to author and authors of this post/comments.
</description>
		<content:encoded><![CDATA[<p>My comments are aimed at questioning throwing out the proverbial baby with the dirty water. I realize you&#8217;ve made your choice, and you are entitled to it. I&#8217;m hoping you&#8217;d like to help others out who are dealing with these problems even though you&#8217;ve chosen to wash your hands of the baby with the dirty water, or something like that.</p>
<p>I really liked Kevin&#8217;s idea:<br />
&#8220;I think one start is mostly unlimited viewing access for most general content while having a hierarchy of users which limit modification of content or at the very least have a moderated approval process of content. I think there&#8217;s still a place for limited access to viewing and editing certain content before it&#8217;s released for general consumption.&#8221;</p>
<p>That would help. And maybe a more broadly-conceived and regulated page-locking policy, even though page-locking is not a good habit and kind of goes against the whole principle.</p>
<p>Can you think of other improvements that would benefit, if not Wikipedia, other collaborative projects that are using Wikipedia as a guide?</p>
<p>Obviously the NPOV doesn&#8217;t effectively attend to &#8220;people [who] make little empires, have their agendas, push through ideas and themes they want, and disregard and delete things they do not&#8221; or to vandals. As you said, it&#8217;s more like a weapon than a guideline.  Maybe a NPOV commission or system instead of delete-first-blame-later?</p>
<p>What about something that can accommodate individualist researchers, like a project manager who has demonstrated a level of knowledge receives help and can opt to refuse help on their locked pages? I don&#8217;t really see why it has to be &#8220;Collaborate or Die&#8221; in Wiki land. Can&#8217;t we have the best of both worlds?</p>
<p>The copyright problem is probably something that Wikipedia is experiencing now more acutely, since copyright is just this big, big problem with any cultural creation now.</p>
<p>Some forums have &#8220;newbie&#8221; or some ranking system which could locate people who don&#8217;t have anything invested in the project. I wonder if that could be implemented in the software somehow to (passively or silently) deal with the problems you&#8217;re bringing up.</p>
<p>I&#8217;m also wondering if these problems are limited to Wikipedia&#8217;s controversial pages or if it is a problem system-wide.</p>
<p>Sorry if I&#8217;m blasting questions here, just trying to learn more about collaborative projects in general.</p>
<p>Thanks to author and authors of this post/comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2835</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Mon, 22 Nov 2004 08:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2835</guid>
		<description>This is tangentially related to semi-developed theories I have about why small community BBSes back in the day had a much higher signal to noise ratio than places like newsgroups and slashdot do now.

Part of my theory is a smaller number of participants, but also that there were often hierarchies of access, often even to find the bbs number or initial password to gain access to the bbs before you could even ASK for access (which you&#039;d get from other people you knew or from BBS lists from other similar boards).

Then once you were on, there&#039;d be general boards that you would be able to post on, but there were often other boards that you wouldn&#039;t even know about until you were approved by a sysop/cosysop or some similar higher trusted user.  You had to gain acceptance by &#039;proving your worth&#039; in some sense, varying depending on the board.  (large numbers of post, providing content, uploading, etc).

Now, one hard part in all this is how you balance general wide access and appropriate limited use that seems to generate a high quality user community and experience.

I think one start is mostly unlimited viewing access for most general content while having a hierarchy of users which limit modification of content or at the very least have a moderated approval process of content.  I think there&#039;s still a place for limited access to viewing and editing certain content before it&#039;s released for general consumption.
</description>
		<content:encoded><![CDATA[<p>This is tangentially related to semi-developed theories I have about why small community BBSes back in the day had a much higher signal to noise ratio than places like newsgroups and slashdot do now.</p>
<p>Part of my theory is a smaller number of participants, but also that there were often hierarchies of access, often even to find the bbs number or initial password to gain access to the bbs before you could even ASK for access (which you&#8217;d get from other people you knew or from BBS lists from other similar boards).</p>
<p>Then once you were on, there&#8217;d be general boards that you would be able to post on, but there were often other boards that you wouldn&#8217;t even know about until you were approved by a sysop/cosysop or some similar higher trusted user.  You had to gain acceptance by &#8216;proving your worth&#8217; in some sense, varying depending on the board.  (large numbers of post, providing content, uploading, etc).</p>
<p>Now, one hard part in all this is how you balance general wide access and appropriate limited use that seems to generate a high quality user community and experience.</p>
<p>I think one start is mostly unlimited viewing access for most general content while having a hierarchy of users which limit modification of content or at the very least have a moderated approval process of content.  I think there&#8217;s still a place for limited access to viewing and editing certain content before it&#8217;s released for general consumption.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peterb</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2834</link>
		<dc:creator>peterb</dc:creator>
		<pubDate>Sun, 21 Nov 2004 00:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2834</guid>
		<description>Thanks for clarifying; that makes a lot more sense.

Given that I work for a living with inferior development tools (gdb, anyone?) that are in widespread use because, let&#039;s face it, worse is better, I feel your pain.
</description>
		<content:encoded><![CDATA[<p>Thanks for clarifying; that makes a lot more sense.</p>
<p>Given that I work for a living with inferior development tools (gdb, anyone?) that are in widespread use because, let&#8217;s face it, worse is better, I feel your pain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mediageek</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2838</link>
		<dc:creator>mediageek</dc:creator>
		<pubDate>Sat, 20 Nov 2004 21:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2838</guid>
		<description>&lt;strong&gt;Criticizing Wikipedia; the Problem with Open Editing&lt;/strong&gt;

&lt;p&gt;Jason Scott has &lt;a href=&quot;http://ascii.textfiles.com/archives/000060.html&quot; rel=&quot;nofollow&quot;&gt;an interesting critique&lt;/a&gt; of &lt;a href=&quot;http://en.wikipedia.org/wiki/Main_Page&quot; rel=&quot;nofollow&quot;&gt;Wikipedia&lt;/a&gt;, from the standpoint of a contributor. He isn&#039;t criticizing the , from the standpoint of a contributor. He isn&#039;t criticizing the &lt;a href=&quot;http://w...&lt;/p rel=&quot;nofollow&quot;&gt;
</description>
		<content:encoded><![CDATA[<p><strong>Criticizing Wikipedia; the Problem with Open Editing</strong></p>
<p>Jason Scott has <a href="http://ascii.textfiles.com/archives/000060.html" rel="nofollow">an interesting critique</a> of <a href="http://en.wikipedia.org/wiki/Main_Page" rel="nofollow">Wikipedia</a>, from the standpoint of a contributor. He isn&#8217;t criticizing the , from the standpoint of a contributor. He isn&#8217;t criticizing the <a href="http://w...</p rel="nofollow"></a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Scott</title>
		<link>http://ascii.textfiles.com/archives/808/comment-page-1#comment-2833</link>
		<dc:creator>Jason Scott</dc:creator>
		<pubDate>Sat, 20 Nov 2004 06:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://ascii.textfiles.com/?p=808#comment-2833</guid>
		<description>Brilliant. You know, you&#039;re the first person to give me feedback (others have read thing and talked to me in other channels) to nail, exactly on the head, where my problems would not be obvious or would be insignificant to the audience. You are correct; from the outside, to someone who is looking for basic information, a lot of Wikipedia will be &#039;good enough&#039;. Mistakes made will not be any more intensely different than anywhere else, that is, shallow take on the topic, common misperceptions (that are in a lot of sources) and so on.

To a toolmaker and tooluser, that is, an information gatherer and disseminator, a researcher who is specifically trying to better the world by showing their findings, I find it very, very problematic, as I spend a lot of time in the sausage factory. And therefore my problems are completely on a different plane from yours and likely many readers of this weblog, or users of Wikipedia.

While a newspaper might report on a race car driver&#039;s work in a way the race car driver wouldn&#039;t, that doesn&#039;t mean that the final stuff doesn&#039;t have some use, even though it omits details the race car driver wouldn&#039;t in describing his work. And the race car driver would be miserable working for the newspaper.

That&#039;s really interesting!
</description>
		<content:encoded><![CDATA[<p>Brilliant. You know, you&#8217;re the first person to give me feedback (others have read thing and talked to me in other channels) to nail, exactly on the head, where my problems would not be obvious or would be insignificant to the audience. You are correct; from the outside, to someone who is looking for basic information, a lot of Wikipedia will be &#8216;good enough&#8217;. Mistakes made will not be any more intensely different than anywhere else, that is, shallow take on the topic, common misperceptions (that are in a lot of sources) and so on.</p>
<p>To a toolmaker and tooluser, that is, an information gatherer and disseminator, a researcher who is specifically trying to better the world by showing their findings, I find it very, very problematic, as I spend a lot of time in the sausage factory. And therefore my problems are completely on a different plane from yours and likely many readers of this weblog, or users of Wikipedia.</p>
<p>While a newspaper might report on a race car driver&#8217;s work in a way the race car driver wouldn&#8217;t, that doesn&#8217;t mean that the final stuff doesn&#8217;t have some use, even though it omits details the race car driver wouldn&#8217;t in describing his work. And the race car driver would be miserable working for the newspaper.</p>
<p>That&#8217;s really interesting!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
