<?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: A Note on Commenting Policies</title>
	<atom:link href="http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/</link>
	<description>A First Things Blog</description>
	<lastBuildDate>Wed, 22 May 2013 14:58:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Michael</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87571</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 21 Jan 2013 04:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87571</guid>
		<description><![CDATA[Thanks for giving us some clarification. I’m curious what the problem the word limit is expected to solve. There’s many a long comment that I simply scroll past, but I’ve never felt that long comments prevented good exchanges. In fact, I think that many of the lengthy comments encourage deeper conversation. 

I wonder whether you have chosen to wrong tool to solve a problem that you haven’t articulated yet. 

It helps to know that there are several moderators, each of whom has different standards. It appears that I’m not alone in being puzzled that some of my comments have not been posted for no discernible reason. It is frustrating to craft a cogent reply and not be able to guess why it wasn’t posted. 

Two years ago, when a comment wasn’t posted, I could reread it and tell immediately where I had gone over the line. I could reword the comment and it would get posted, but that doesn’t happen anymore, and frankly, I no longer take the trouble to reword a comment. I figure that it is my ideas and not my wording that has been rejected. 

A few weeks ago, my comment was posted and then taken down later that day. The comment was a short sentence. It was neither insulting nor crude, but it criticized the premise of the article. 

There’s a shift in the moderation policy and more deeply in the approach to commenting that still hasn’t been explained. 

Over the years, I’ve learned much from the commenters as well as from the essayists. It’s shame that this door to free dialogue has narrowed.]]></description>
		<content:encoded><![CDATA[<p>Thanks for giving us some clarification. I’m curious what the problem the word limit is expected to solve. There’s many a long comment that I simply scroll past, but I’ve never felt that long comments prevented good exchanges. In fact, I think that many of the lengthy comments encourage deeper conversation. </p>
<p>I wonder whether you have chosen to wrong tool to solve a problem that you haven’t articulated yet. </p>
<p>It helps to know that there are several moderators, each of whom has different standards. It appears that I’m not alone in being puzzled that some of my comments have not been posted for no discernible reason. It is frustrating to craft a cogent reply and not be able to guess why it wasn’t posted. </p>
<p>Two years ago, when a comment wasn’t posted, I could reread it and tell immediately where I had gone over the line. I could reword the comment and it would get posted, but that doesn’t happen anymore, and frankly, I no longer take the trouble to reword a comment. I figure that it is my ideas and not my wording that has been rejected. </p>
<p>A few weeks ago, my comment was posted and then taken down later that day. The comment was a short sentence. It was neither insulting nor crude, but it criticized the premise of the article. </p>
<p>There’s a shift in the moderation policy and more deeply in the approach to commenting that still hasn’t been explained. </p>
<p>Over the years, I’ve learned much from the commenters as well as from the essayists. It’s shame that this door to free dialogue has narrowed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boonton</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87379</link>
		<dc:creator>Boonton</dc:creator>
		<pubDate>Fri, 18 Jan 2013 13:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87379</guid>
		<description><![CDATA[A far simplier solution I think would be to leave a placeholder behind for comments deleted by the moderators.  Provided the commenter wasn&#039;t spamming the thread with hundreds of posts, the message &quot;Post from X deleted&quot; would speak for itself.  

If the moderator was going overboard, it would make that publically visible.  If the writer is known as a trouble maker, no one will think anything of it.  In cases where the writer may have just let the tone slip away from him, he will be able to know he went beyond the line and would be able to adjust inhis future posts.]]></description>
		<content:encoded><![CDATA[<p>A far simplier solution I think would be to leave a placeholder behind for comments deleted by the moderators.  Provided the commenter wasn&#8217;t spamming the thread with hundreds of posts, the message &#8220;Post from X deleted&#8221; would speak for itself.  </p>
<p>If the moderator was going overboard, it would make that publically visible.  If the writer is known as a trouble maker, no one will think anything of it.  In cases where the writer may have just let the tone slip away from him, he will be able to know he went beyond the line and would be able to adjust inhis future posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Nickol</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87309</link>
		<dc:creator>David Nickol</dc:creator>
		<pubDate>Thu, 17 Jan 2013 23:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87309</guid>
		<description><![CDATA[&lt;i&gt;Alternative idea, create a page for rejected comments. &lt;/i&gt;

Boonton,

I have it on good authority that some of the comments that do not pass moderation really should never see the light of day anywhere. I like the idea of an alternative outlet, but asking the moderators to publish rejected comments elsewhere would put them in a position of deciding what&#039;s fit for First Things, what isn&#039;t up to snuff but is just okay, and what is so profane, libelous, crackpot, etc. that it will turn people against the Internet. 

I do have an unused web site that I am thinking of opening up to be used for continuing discussions that begin elsewhere. Of course, then &lt;i&gt;I&lt;/i&gt; would become a moderator and have to go through the same kind of suffering the moderators do here.]]></description>
		<content:encoded><![CDATA[<p><i>Alternative idea, create a page for rejected comments. </i></p>
<p>Boonton,</p>
<p>I have it on good authority that some of the comments that do not pass moderation really should never see the light of day anywhere. I like the idea of an alternative outlet, but asking the moderators to publish rejected comments elsewhere would put them in a position of deciding what&#8217;s fit for First Things, what isn&#8217;t up to snuff but is just okay, and what is so profane, libelous, crackpot, etc. that it will turn people against the Internet. </p>
<p>I do have an unused web site that I am thinking of opening up to be used for continuing discussions that begin elsewhere. Of course, then <i>I</i> would become a moderator and have to go through the same kind of suffering the moderators do here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boonton</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87281</link>
		<dc:creator>Boonton</dc:creator>
		<pubDate>Thu, 17 Jan 2013 20:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87281</guid>
		<description><![CDATA[Alternative idea, create a page for rejected comments.  Just nothing more than a dumping ground.  If a moderator dumps comments in there because they are &#039;too good&#039; in refuting a favored cause, it will be very clear and obvious.  On the other hand if they are all really poor comments dumped in there then no need to think about the issue anymore.]]></description>
		<content:encoded><![CDATA[<p>Alternative idea, create a page for rejected comments.  Just nothing more than a dumping ground.  If a moderator dumps comments in there because they are &#8216;too good&#8217; in refuting a favored cause, it will be very clear and obvious.  On the other hand if they are all really poor comments dumped in there then no need to think about the issue anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boonton</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87273</link>
		<dc:creator>Boonton</dc:creator>
		<pubDate>Thu, 17 Jan 2013 20:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87273</guid>
		<description><![CDATA[Thanks Anna,

I too get the feeling that sometimes comment moderation feels arbitrary or random...maybe moderators could agree to step into comment threads periodically and warn commentaters that their getting close to the line.  This way we can get a sense of just where the line is.  Or if nothing else do an autoemail alerting us that a comment was rejected.  Even if we don&#039;t know the reason we can get a feel for what does and doesn&#039;t make the cut.]]></description>
		<content:encoded><![CDATA[<p>Thanks Anna,</p>
<p>I too get the feeling that sometimes comment moderation feels arbitrary or random&#8230;maybe moderators could agree to step into comment threads periodically and warn commentaters that their getting close to the line.  This way we can get a sense of just where the line is.  Or if nothing else do an autoemail alerting us that a comment was rejected.  Even if we don&#8217;t know the reason we can get a feel for what does and doesn&#8217;t make the cut.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Nickol</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87269</link>
		<dc:creator>David Nickol</dc:creator>
		<pubDate>Thu, 17 Jan 2013 20:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87269</guid>
		<description><![CDATA[Since the contributors&#039; original posts are always well researched, cogently argued, and highly persuasive, comments agreeing with them are necessarily redundant. So only comments disagreeing with the original post should be passed through moderation. 

To be fair, comment length should be equal to the length of the original post. Limiting comments to a 600-word post to 300 words puts commenters at a disadvantage. 

Comments written during business hours should contain a brief description of the work the commenter is neglecting in order to express his or her opinion. 

Boldface and italics sometimes do not covey the desired degree of emphasis. Despite the fact that it is not standard HTML, some way should be found to code text in comments so it will blink blink blink. 

Under no circumstances should facetious comments pass moderation.]]></description>
		<content:encoded><![CDATA[<p>Since the contributors&#8217; original posts are always well researched, cogently argued, and highly persuasive, comments agreeing with them are necessarily redundant. So only comments disagreeing with the original post should be passed through moderation. </p>
<p>To be fair, comment length should be equal to the length of the original post. Limiting comments to a 600-word post to 300 words puts commenters at a disadvantage. </p>
<p>Comments written during business hours should contain a brief description of the work the commenter is neglecting in order to express his or her opinion. </p>
<p>Boldface and italics sometimes do not covey the desired degree of emphasis. Despite the fact that it is not standard HTML, some way should be found to code text in comments so it will blink blink blink. </p>
<p>Under no circumstances should facetious comments pass moderation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arty</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87259</link>
		<dc:creator>arty</dc:creator>
		<pubDate>Thu, 17 Jan 2013 19:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87259</guid>
		<description><![CDATA[I&#039;ll reiterate my suggestion from some time ago, that we ought to be required to start every posting with a one-sentence statement of the circumstances under which we&#039;d consider ourselves to have been proven wrong.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ll reiterate my suggestion from some time ago, that we ought to be required to start every posting with a one-sentence statement of the circumstances under which we&#8217;d consider ourselves to have been proven wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Rowe</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87256</link>
		<dc:creator>Jon Rowe</dc:creator>
		<pubDate>Thu, 17 Jan 2013 18:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87256</guid>
		<description><![CDATA[I don&#039;t mind the commenting length standard because it is objective.  Likewise a no curse word standard is objective as well.  As would be a standard of number of post limits per day (like 2 or 3).  I don&#039;t like the unexplained, arbitrary factor and have seen a few of my posts not put through, for what I see as not a good reason.  Though it&#039;s not something that I care too much about to make a big deal over.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t mind the commenting length standard because it is objective.  Likewise a no curse word standard is objective as well.  As would be a standard of number of post limits per day (like 2 or 3).  I don&#8217;t like the unexplained, arbitrary factor and have seen a few of my posts not put through, for what I see as not a good reason.  Though it&#8217;s not something that I care too much about to make a big deal over.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anna Williams</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87247</link>
		<dc:creator>Anna Williams</dc:creator>
		<pubDate>Thu, 17 Jan 2013 17:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87247</guid>
		<description><![CDATA[@Boonton, we&#039;ll consider a preview comment button. To answer your other questions:

Moderation is almost 100% manual -- the only automatic component is the spam-blocker, which sometimes is over-zealous (automatically blocking posts with too many hyperlinks, explicit language, or other common features of spam). But every comment is reviewed by one of us before it is posted. 

Because moderating is a duty shared by several staff members here, and because our standards (civility, relevance, and substantially advancing the engagement of the topic) can mean slightly different things to different people, quirks and inconsistencies like the ones you mentioned can arise. If a thread is devolving into unproductive and unilluminating arguments, or if it gets too far afield of the topic of the blog post, we may raise the standard of what we allow. However, due to time constraints and other reasons, we cannot explain individual moderating decisions. 

I hope this is helpful!]]></description>
		<content:encoded><![CDATA[<p>@Boonton, we&#8217;ll consider a preview comment button. To answer your other questions:</p>
<p>Moderation is almost 100% manual &#8212; the only automatic component is the spam-blocker, which sometimes is over-zealous (automatically blocking posts with too many hyperlinks, explicit language, or other common features of spam). But every comment is reviewed by one of us before it is posted. </p>
<p>Because moderating is a duty shared by several staff members here, and because our standards (civility, relevance, and substantially advancing the engagement of the topic) can mean slightly different things to different people, quirks and inconsistencies like the ones you mentioned can arise. If a thread is devolving into unproductive and unilluminating arguments, or if it gets too far afield of the topic of the blog post, we may raise the standard of what we allow. However, due to time constraints and other reasons, we cannot explain individual moderating decisions. </p>
<p>I hope this is helpful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boonton</title>
		<link>http://www.firstthings.com/blogs/firstthoughts/2013/01/16/commenting-policy/comment-page-1/#comment-87245</link>
		<dc:creator>Boonton</dc:creator>
		<pubDate>Thu, 17 Jan 2013 17:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstthings.com/blogs/firstthoughts/?p=55588#comment-87245</guid>
		<description><![CDATA[Character count would be helpful, but what about just a &#039;preview comment&#039; button?  At least that would alert the writer that he was about to post something that would be sliced in half!

Also can you clarrify a bit about how your moderation works? Is every comment approved manually? Do they auto-approve if a moderator doesn&#039;t touch them? It seems I have sometimes lost comments for days to moderation and I&#039;m not sure if it was me, my tone, or just quirks in the system?  If moderation is active then a little feedback from moderators would be helpful even if it can&#039;t be given for each rejected comment.

Finally let me say I don&#039;t object to the limit. It&#039;s frustrating when a thread has multiple people on one side and I&#039;m tring to cover each argument they make, but it has helped me trim down my arguments and make them more concise and biting!]]></description>
		<content:encoded><![CDATA[<p>Character count would be helpful, but what about just a &#8216;preview comment&#8217; button?  At least that would alert the writer that he was about to post something that would be sliced in half!</p>
<p>Also can you clarrify a bit about how your moderation works? Is every comment approved manually? Do they auto-approve if a moderator doesn&#8217;t touch them? It seems I have sometimes lost comments for days to moderation and I&#8217;m not sure if it was me, my tone, or just quirks in the system?  If moderation is active then a little feedback from moderators would be helpful even if it can&#8217;t be given for each rejected comment.</p>
<p>Finally let me say I don&#8217;t object to the limit. It&#8217;s frustrating when a thread has multiple people on one side and I&#8217;m tring to cover each argument they make, but it has helped me trim down my arguments and make them more concise and biting!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
