<?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"
	>
<channel>
	<title>Comments on: The future of Comment Timeout</title>
	<atom:link href="http://jamesmckay.net/2007/04/the-future-of-comment-timeout/feed/" rel="self" type="application/rss+xml" />
	<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/</link>
	<description>because there are few things that are less logical than business logic</description>
	<pubDate>Fri, 21 Nov 2008 12:40:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: James</title>
		<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1402</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sun, 03 Jun 2007 22:37:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1402</guid>
		<description>Thanks for all the feedback, folks -- the first alpha versions of the new plugins are now available (though I decided on the name Link Limits rather than The Black Hole in the end). AJ: nice suggestion, I've included it as an option in version 2.0.</description>
		<content:encoded><![CDATA[<p>Thanks for all the feedback, folks &#8212; the first alpha versions of the new plugins are now available (though I decided on the name Link Limits rather than The Black Hole in the end). AJ: nice suggestion, I&#8217;ve included it as an option in version 2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim McCormack</title>
		<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1366</link>
		<dc:creator>Tim McCormack</dc:creator>
		<pubDate>Wed, 23 May 2007 21:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1366</guid>
		<description>I like the approach Erdla Jonsdottir's tutor outlined -- keep the modules small, well-defined, and powerful (I've also heard this described as "Unix" :-P).  The tentative plan to split it into three plugins sounds good -- I'd like to use several of those, but probably not all three.</description>
		<content:encoded><![CDATA[<p>I like the approach Erdla Jonsdottir&#8217;s tutor outlined &#8212; keep the modules small, well-defined, and powerful (I&#8217;ve also heard this described as &#8220;Unix&#8221; <img src="http://jamesmckay.net/wp-content/plugins/more-smilies/MSN-Messenger/msn_tongue.png" alt="-P" class="wp-smiley" /> ).  The tentative plan to split it into three plugins sounds good &#8212; I&#8217;d like to use several of those, but probably not all three.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erdla Jonsdottir</title>
		<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1338</link>
		<dc:creator>Erdla Jonsdottir</dc:creator>
		<pubDate>Sat, 12 May 2007 07:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1338</guid>
		<description>I've just installed your plugin - thankyou!

 - On general principles I'd agree that splitting the plugin up is a good idea. I do some coding myself and am painfully familiar with "scope creep" I try to remind myself of something that a tutor of mine once said.

"I'd rather have a set of simple programs each of which does its job superbly than one program where you have to wade through 5 menus just to save the file."

There is perhaps something about people who write software that makes us want to put in all the sparkling good ideas into version 2? So we add in lots of extra features (and if you are me lots of  extra bugs :sad: ) and then after it is debugged  we wind up wondering why the end user clicked all the "wrong" options and is now making endless support requests. 

Having said that I like the suggestion made by "AJ" very much. 

(PS: "My" blog is run by several people I am not sure if that comes under the heading of "personal blog" my apologies if it does not)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just installed your plugin - thankyou!</p>
<p> - On general principles I&#8217;d agree that splitting the plugin up is a good idea. I do some coding myself and am painfully familiar with &#8220;scope creep&#8221; I try to remind myself of something that a tutor of mine once said.</p>
<p>&#8220;I&#8217;d rather have a set of simple programs each of which does its job superbly than one program where you have to wade through 5 menus just to save the file.&#8221;</p>
<p>There is perhaps something about people who write software that makes us want to put in all the sparkling good ideas into version 2? So we add in lots of extra features (and if you are me lots of  extra bugs  <img src="http://jamesmckay.net/wp-content/plugins/more-smilies/MSN-Messenger/msn_sad.png" alt="sad" class="wp-smiley" />  ) and then after it is debugged  we wind up wondering why the end user clicked all the &#8220;wrong&#8221; options and is now making endless support requests. </p>
<p>Having said that I like the suggestion made by &#8220;AJ&#8221; very much. </p>
<p>(PS: &#8220;My&#8221; blog is run by several people I am not sure if that comes under the heading of &#8220;personal blog&#8221; my apologies if it does not)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Schultz</title>
		<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1334</link>
		<dc:creator>James Schultz</dc:creator>
		<pubDate>Wed, 09 May 2007 15:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1334</guid>
		<description>I think that splitting into three plugins is the way to go.  I love the comment timeout feature, but I don't really need the other two.  If they were separate, I could easily get just what I need.</description>
		<content:encoded><![CDATA[<p>I think that splitting into three plugins is the way to go.  I love the comment timeout feature, but I don&#8217;t really need the other two.  If they were separate, I could easily get just what I need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJ</title>
		<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1296</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Thu, 03 May 2007 04:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1296</guid>
		<description>Hi,
I just started using the plugin and I think it's a great idea. One feature I would like to have is either have reject or put the comments to an old post into the moderation queue instead of rejecting them altogether.
With a lot of traffic coming in from the search engines, one never knows when a user stumbles upon an old post.

Thanks for the plugin :)</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I just started using the plugin and I think it&#8217;s a great idea. One feature I would like to have is either have reject or put the comments to an old post into the moderation queue instead of rejecting them altogether.<br />
With a lot of traffic coming in from the search engines, one never knows when a user stumbles upon an old post.</p>
<p>Thanks for the plugin <img src="http://jamesmckay.net/wp-content/plugins/more-smilies/MSN-Messenger/msn_smiley.png" alt=")" class="wp-smiley" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jay1951</title>
		<link>http://jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1271</link>
		<dc:creator>jay1951</dc:creator>
		<pubDate>Thu, 26 Apr 2007 09:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamesmckay.net/2007/04/the-future-of-comment-timeout/#comment-1271</guid>
		<description>I think this is a great idea because it would make trouble shooting much easier.

Right now I'm not using this because it turns off all comments and my blog is only 1 week old.</description>
		<content:encoded><![CDATA[<p>I think this is a great idea because it would make trouble shooting much easier.</p>
<p>Right now I&#8217;m not using this because it turns off all comments and my blog is only 1 week old.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
