<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Mock-up discussion thread</title>
	<atom:link href="http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/feed/" rel="self" type="application/rss+xml" />
	<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/</link>
	<description>Massively collaborative mathematical projects</description>
	<lastBuildDate>Thu, 20 Jun 2013 08:44:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: bingolinn</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-6349</link>
		<dc:creator><![CDATA[bingolinn]]></dc:creator>
		<pubDate>Mon, 18 Jun 2012 00:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-6349</guid>
		<description><![CDATA[Заброс удочки Одним из главных условий результативной ловли является грамотный заброс удочки, ведь неумелое обращение со снастью может распугать всю рыбу &lt;a href=&quot;http://vipsoi.ru/&quot; / rel=&quot;nofollow&quot;&gt;Удилище Kosadaka Cinergy Tele Bolognese&lt;/a&gt; Удочка на карпа Карп, который водится почти во всех водоемах со слабым течением, отлично ловится весной и летом в солнечную]]></description>
		<content:encoded><![CDATA[<p>Заброс удочки Одним из главных условий результативной ловли является грамотный заброс удочки, ведь неумелое обращение со снастью может распугать всю рыбу <a href="http://vipsoi.ru/" / rel="nofollow">Удилище Kosadaka Cinergy Tele Bolognese</a> Удочка на карпа Карп, который водится почти во всех водоемах со слабым течением, отлично ловится весной и летом в солнечную</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mirtesky</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-3164</link>
		<dc:creator><![CDATA[Mirtesky]]></dc:creator>
		<pubDate>Sat, 21 May 2011 18:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-3164</guid>
		<description><![CDATA[]]></description>
		<content:encoded><![CDATA[<p>      &#8230;<br />
,    ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terence Tao</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-227</link>
		<dc:creator><![CDATA[Terence Tao]]></dc:creator>
		<pubDate>Tue, 04 Aug 2009 15:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-227</guid>
		<description><![CDATA[Well, ideally the wiki and the blog would be integrated, so that one could mirror a wiki page on the blog or vice versa (or even more ideally, there would be a single page object somewhere that both the wiki and the blog could access or edit, essentially simultaneously).  [This, incidentally, is one of the capabilities of Google Wave.]  But until such time, I guess the best option is to have a master page (on the wiki) for this sort of thing, and links to that page on the blog.  So I&#039;ve set up a wiki page now for all of the active projects, and on the blogroll on the right of the blog there are links to each of them.]]></description>
		<content:encoded><![CDATA[<p>Well, ideally the wiki and the blog would be integrated, so that one could mirror a wiki page on the blog or vice versa (or even more ideally, there would be a single page object somewhere that both the wiki and the blog could access or edit, essentially simultaneously).  [This, incidentally, is one of the capabilities of Google Wave.]  But until such time, I guess the best option is to have a master page (on the wiki) for this sort of thing, and links to that page on the blog.  So I&#8217;ve set up a wiki page now for all of the active projects, and on the blogroll on the right of the blog there are links to each of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Nielsen</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-148</link>
		<dc:creator><![CDATA[Michael Nielsen]]></dc:creator>
		<pubDate>Fri, 31 Jul 2009 13:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-148</guid>
		<description><![CDATA[Jason - I&#039;d like to wait until there&#039;s a bit more data on the use of the comment ratings.  It&#039;s possible, for example, that they may turn out to be unexpectedly helpful when people summarize blog discussion on the wiki, as a way of quickly identifying crucial comments.]]></description>
		<content:encoded><![CDATA[<p>Jason &#8211; I&#8217;d like to wait until there&#8217;s a bit more data on the use of the comment ratings.  It&#8217;s possible, for example, that they may turn out to be unexpectedly helpful when people summarize blog discussion on the wiki, as a way of quickly identifying crucial comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-135</link>
		<dc:creator><![CDATA[Scott]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 21:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-135</guid>
		<description><![CDATA[With regards to threading, I have a few comments.  I was a casual participant in miniPolymath1, and I can say that it became too much of a headache to follow everything.  Allowing depth-10 nesting of comments will certainly help, but I still think it will be intimidating for a casual reader to jump in simply based on the number of comments he has to sort through.

I am not sure that this is even feasible on these blogs, but I know how I would like to see comments (as a casual reader).  I imagine a bulletin board style layout.  At the top are a few links which look like
&quot;Taking John&#039;s idea from comment 10 further (59 comments)&quot; 
&quot;Taking Dan&#039;s idea from comment 19 further (30 comments)&quot;
&quot;Continuing on the ideas of comments 11-15 (100 comments)&quot;
Below these links is the original discussion of the problem.  People could continue to post observations which are disjoint from all the above links, such as fresh ideas, new approaches, and observations which apply across the board.
Clicking on &quot;Taking John&#039;s idea from comment 10 further&quot; would lead to another page with the same layout.  Again at the top we read &quot;Taking X&#039;s idea from comment n further&quot; and below these links we see the discussion, but this time the discussion is only concerned with John&#039;s idea.  You get the idea.

To achieve such organization, perhaps those who are working full time on the project (or whoever has agreed to occasionally summarize the findings) could create these links and then be the first to post on the newly created page with their summary.

I am no expert on manipulating blogs so I understand that this may not be as easy as I&#039;ve made it sound.  But this sort of layout would be most pleasing to the eye of the casual reader who may just want to work on the most popular attempts (gauged by the number of comments next to each link).  And it also allows more organization in the comments since we get to see the relative depth of the observation based on how many clicks into the thread we are.]]></description>
		<content:encoded><![CDATA[<p>With regards to threading, I have a few comments.  I was a casual participant in miniPolymath1, and I can say that it became too much of a headache to follow everything.  Allowing depth-10 nesting of comments will certainly help, but I still think it will be intimidating for a casual reader to jump in simply based on the number of comments he has to sort through.</p>
<p>I am not sure that this is even feasible on these blogs, but I know how I would like to see comments (as a casual reader).  I imagine a bulletin board style layout.  At the top are a few links which look like<br />
&#8220;Taking John&#8217;s idea from comment 10 further (59 comments)&#8221;<br />
&#8220;Taking Dan&#8217;s idea from comment 19 further (30 comments)&#8221;<br />
&#8220;Continuing on the ideas of comments 11-15 (100 comments)&#8221;<br />
Below these links is the original discussion of the problem.  People could continue to post observations which are disjoint from all the above links, such as fresh ideas, new approaches, and observations which apply across the board.<br />
Clicking on &#8220;Taking John&#8217;s idea from comment 10 further&#8221; would lead to another page with the same layout.  Again at the top we read &#8220;Taking X&#8217;s idea from comment n further&#8221; and below these links we see the discussion, but this time the discussion is only concerned with John&#8217;s idea.  You get the idea.</p>
<p>To achieve such organization, perhaps those who are working full time on the project (or whoever has agreed to occasionally summarize the findings) could create these links and then be the first to post on the newly created page with their summary.</p>
<p>I am no expert on manipulating blogs so I understand that this may not be as easy as I&#8217;ve made it sound.  But this sort of layout would be most pleasing to the eye of the casual reader who may just want to work on the most popular attempts (gauged by the number of comments next to each link).  And it also allows more organization in the comments since we get to see the relative depth of the observation based on how many clicks into the thread we are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Dyer</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-127</link>
		<dc:creator><![CDATA[Jason Dyer]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 14:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-127</guid>
		<description><![CDATA[So far I don&#039;t think the ratings are working very well. I&#039;ve read through the developing thread and so far the application of thumbs seems arbitrary; for example, why did this &lt;a href=&quot;http://polymathprojects.org/2009/07/27/proposal-deterministic-way-to-find-primes/#comment-34&quot; rel=&quot;nofollow&quot;&gt;comment from Gil&lt;/a&gt; get a thumbs down?

Additionally, we&#039;ve already discussed the importance of allowing mistakes and errors; the original screed from Dr. Gowers was to allow half-formed ideas, but I fear if people can start to get rated down that we will get less experimentation.

Finally if there&#039;s some sort of filter code to only view comments over a certain threshold, I fear it could make things more rather than less confusing, because often key insights have only made sense in the context of the (more minor) comments that preceded them.]]></description>
		<content:encoded><![CDATA[<p>So far I don&#8217;t think the ratings are working very well. I&#8217;ve read through the developing thread and so far the application of thumbs seems arbitrary; for example, why did this <a href="http://polymathprojects.org/2009/07/27/proposal-deterministic-way-to-find-primes/#comment-34" rel="nofollow">comment from Gil</a> get a thumbs down?</p>
<p>Additionally, we&#8217;ve already discussed the importance of allowing mistakes and errors; the original screed from Dr. Gowers was to allow half-formed ideas, but I fear if people can start to get rated down that we will get less experimentation.</p>
<p>Finally if there&#8217;s some sort of filter code to only view comments over a certain threshold, I fear it could make things more rather than less confusing, because often key insights have only made sense in the context of the (more minor) comments that preceded them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thlog</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-103</link>
		<dc:creator><![CDATA[thlog]]></dc:creator>
		<pubDate>Wed, 29 Jul 2009 02:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-103</guid>
		<description><![CDATA[Do you think it would be worthwhile to create a WordPress &quot;page&quot; for each project giving the problem statement and some background information and links?  Or do you want to keep that sort of information just on the Wiki?]]></description>
		<content:encoded><![CDATA[<p>Do you think it would be worthwhile to create a WordPress &#8220;page&#8221; for each project giving the problem statement and some background information and links?  Or do you want to keep that sort of information just on the Wiki?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan  O'Donnell</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-98</link>
		<dc:creator><![CDATA[Ryan  O'Donnell]]></dc:creator>
		<pubDate>Wed, 29 Jul 2009 00:47:43 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-98</guid>
		<description><![CDATA[Perhaps in this case many people would up-vote a &quot;reply&quot; comment explaining the error in the earlier argument.  Whether the earlier argument got a lot of up-votes or a lot of down-votes or both, I think it would indicate to the reader that something important may be in that comment.]]></description>
		<content:encoded><![CDATA[<p>Perhaps in this case many people would up-vote a &#8220;reply&#8221; comment explaining the error in the earlier argument.  Whether the earlier argument got a lot of up-votes or a lot of down-votes or both, I think it would indicate to the reader that something important may be in that comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terence Tao</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-84</link>
		<dc:creator><![CDATA[Terence Tao]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 18:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-84</guid>
		<description><![CDATA[I&#039;ve enabled CSS modification.  Looks like the spacing has taken effect.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve enabled CSS modification.  Looks like the spacing has taken effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Nielsen</title>
		<link>http://polymathprojects.org/2009/07/26/mock-up-discussion-thread/#comment-81</link>
		<dc:creator><![CDATA[Michael Nielsen]]></dc:creator>
		<pubDate>Tue, 28 Jul 2009 18:37:21 +0000</pubDate>
		<guid isPermaLink="false">http://polymathprojects.wordpress.com/2009/07/26/mock-up-discussion-thread/#comment-81</guid>
		<description><![CDATA[Thanks for this.  I added it to the CSS on a trial basis.  It seems like an improvement to me.

(I&#039;ve found that it doesn&#039;t always seem to take effect, though.  I assume that&#039;s probably some type of caching issue, and will disappear.)

Edit: I see what&#039;s going on.  It&#039;s displaying correctly in a kind of preview mode available to admins. But apparently we have to purchase the ability to modify the CSS, for general use.  I&#039;ll look into it.]]></description>
		<content:encoded><![CDATA[<p>Thanks for this.  I added it to the CSS on a trial basis.  It seems like an improvement to me.</p>
<p>(I&#8217;ve found that it doesn&#8217;t always seem to take effect, though.  I assume that&#8217;s probably some type of caching issue, and will disappear.)</p>
<p>Edit: I see what&#8217;s going on.  It&#8217;s displaying correctly in a kind of preview mode available to admins. But apparently we have to purchase the ability to modify the CSS, for general use.  I&#8217;ll look into it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
