<?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 for lotect</title>
	<atom:link href="http://lotect.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://lotect.com</link>
	<description>low tech software architecture</description>
	<lastBuildDate>Tue, 20 Mar 2012 22:24:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on proposal for a blog comment/cms system by Quora</title>
		<link>http://lotect.com/2012/03/05/proposal-for-a-blog-commentcms-system/comment-page-1/#comment-74</link>
		<dc:creator>Quora</dc:creator>
		<pubDate>Tue, 20 Mar 2012 22:24:31 +0000</pubDate>
		<guid isPermaLink="false">http://lotect.com/?p=78#comment-74</guid>
		<description>&lt;strong&gt;What&#039;s the best technology to build a web platform like Facebook as of October 2011?...&lt;/strong&gt;

I&#039;ll take a higher level view. As for why - to escape the vendor lockin, to scale to provide redundancy, to avoid government imposed, censorship or other shutdowns. As for how, give everyone their own blog (or realistically rely on existing services)....</description>
		<content:encoded><![CDATA[<p><strong>What&#8217;s the best technology to build a web platform like Facebook as of October 2011?&#8230;</strong></p>
<p>I&#8217;ll take a higher level view. As for why &#8211; to escape the vendor lockin, to scale to provide redundancy, to avoid government imposed, censorship or other shutdowns. As for how, give everyone their own blog (or realistically rely on existing services)&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Human Rights Day tweet by malatmals</title>
		<link>http://lotect.com/2011/12/10/human-rights-day-tweet/comment-page-1/#comment-73</link>
		<dc:creator>malatmals</dc:creator>
		<pubDate>Thu, 15 Dec 2011 20:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://lotect.com/?p=73#comment-73</guid>
		<description>test comment yadayada</description>
		<content:encoded><![CDATA[<p>test comment yadayada</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on re: Proposal: A new kind of blog comment system by admin</title>
		<link>http://lotect.com/2010/08/22/re-proposal-a-new-kind-of-blog-comment-system/comment-page-1/#comment-26</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 23 Aug 2010 03:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://lotect.com/?p=44#comment-26</guid>
		<description>Re: 2 I agree he&#039;s pushed us off into the fringe where it&#039;s harder to maintain/follow connections. I was doing twitter searches on his name @davewiner to see what other people were saying in reply. This works to some degree but degrades over time as other conversations get mixed in.

Re: 4 On a search page twitter itself does now have a show conversation link to show how they are related. Here&#039;s a picture of &lt;a href=&quot;http://img.skitch.com/20100823-bffc8i77b3rde2ajgnae7fwhye.jpg&quot; rel=&quot;nofollow&quot;&gt;one&lt;/a&gt;. This conversation could and did go on for quite a long time. The thing is Dave didn&#039;t start a conversation on Twitter so there really is no thread for it. A couple more conversations he had on the topic are &lt;a href=&quot;http://skitch.com/malatmals/dufeq/davewiner-twitter-search&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. Twitter may not be the solution but it has elements of the solution.

5. Generally yes but one thing Dave didn&#039;t really play to is that some posts get thousands of comments and the noise can be overwhelming. I started looking into solutions to blog comments and found http://aboutecho.com/ But if you look at someone using it (Leo Laporte) look - this &lt;a href=&quot;http://leoville.com/buzz-kill&quot; rel=&quot;nofollow&quot;&gt;post&lt;/a&gt; has 1543 &quot;comments&quot;.  

So I don&#039;t know there are complexities here deeper than are apparent at first sight. I think too the ideal solution depends on your blog/followers/your tolerance for pain/your subject. I want my journals peer reviewed but most my blog posts don&#039;t need to be. I can manage all my commenters easily. Words that come to mind which could be elements of the solution are threads, forums, crowdsourcing, ranking, weighting. Maybe Dave&#039;s blog is at a point where he could get some people to moderate for him. Some of his ideas are great and could spawn whole programs - maybe a forum could handle that coordination better. I feel bad he has to waste his time moderating a bunch of off-topic unhappy irrelevant posts. I mean some of the posts especially if they&#039;re long I have a habit of glossing over myself. I&#039;m going to research this a little more and see if I can&#039;t find some tools/methodology that could help.</description>
		<content:encoded><![CDATA[<p>Re: 2 I agree he&#8217;s pushed us off into the fringe where it&#8217;s harder to maintain/follow connections. I was doing twitter searches on his name @davewiner to see what other people were saying in reply. This works to some degree but degrades over time as other conversations get mixed in.</p>
<p>Re: 4 On a search page twitter itself does now have a show conversation link to show how they are related. Here&#8217;s a picture of <a href="http://img.skitch.com/20100823-bffc8i77b3rde2ajgnae7fwhye.jpg" rel="nofollow">one</a>. This conversation could and did go on for quite a long time. The thing is Dave didn&#8217;t start a conversation on Twitter so there really is no thread for it. A couple more conversations he had on the topic are <a href="http://skitch.com/malatmals/dufeq/davewiner-twitter-search" rel="nofollow">here</a>. Twitter may not be the solution but it has elements of the solution.</p>
<p>5. Generally yes but one thing Dave didn&#8217;t really play to is that some posts get thousands of comments and the noise can be overwhelming. I started looking into solutions to blog comments and found <a href="http://aboutecho.com/" rel="nofollow">http://aboutecho.com/</a> But if you look at someone using it (Leo Laporte) look &#8211; this <a href="http://leoville.com/buzz-kill" rel="nofollow">post</a> has 1543 &#8220;comments&#8221;.  </p>
<p>So I don&#8217;t know there are complexities here deeper than are apparent at first sight. I think too the ideal solution depends on your blog/followers/your tolerance for pain/your subject. I want my journals peer reviewed but most my blog posts don&#8217;t need to be. I can manage all my commenters easily. Words that come to mind which could be elements of the solution are threads, forums, crowdsourcing, ranking, weighting. Maybe Dave&#8217;s blog is at a point where he could get some people to moderate for him. Some of his ideas are great and could spawn whole programs &#8211; maybe a forum could handle that coordination better. I feel bad he has to waste his time moderating a bunch of off-topic unhappy irrelevant posts. I mean some of the posts especially if they&#8217;re long I have a habit of glossing over myself. I&#8217;m going to research this a little more and see if I can&#8217;t find some tools/methodology that could help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on re: Proposal: A new kind of blog comment system by John E. Bredehoft</title>
		<link>http://lotect.com/2010/08/22/re-proposal-a-new-kind-of-blog-comment-system/comment-page-1/#comment-25</link>
		<dc:creator>John E. Bredehoft</dc:creator>
		<pubDate>Mon, 23 Aug 2010 01:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://lotect.com/?p=44#comment-25</guid>
		<description>I addressed some of these issues in &lt;a href=&quot;http://empoprise-bi.blogspot.com/2010/08/if-you-dont-discuss-blog-post-at-post.html&quot; rel=&quot;nofollow&quot;&gt;my own blog post&lt;/a&gt;, but didn&#039;t do a point-by-point response to Winer&#039;s proposal. So in response to YOUR point-by-point response:

1. Agreed. I recently got back from nearly a week of traveling, and missed a lot of news during that period (I was lucky to happen to hear about the Intel-McAfee deal). I wouldn&#039;t want to miss the ability to react to something because I was on a really long bike ride.

2. This is my major problem with Winer&#039;s proposal. My interpretation of Winer&#039;s preferred reaction is for everyone to write their own blog posts in response, like you did and like I did. But it&#039;s difficult to find all of the blog posts that touch upon a particular topic (yours is the third one that I found on Winer&#039;s post, and I don&#039;t know if I&#039;ll find many more), and it&#039;s hard to have a discussion in a bunch of silos. 

3. Having the perfect comment is akin to having the perfect blog post - and if you&#039;re going to wait until it&#039;s perfect, you might as well just publish a book.

4. Frankly, I&#039;m not that hot on Twitter as a conversational medium either. You say later in your post that Twitter is effective &quot;with good tools&quot; - perhaps you can put enough lipstick on that pig, but if you need &quot;good tools&quot; to get Twitter to work, then Twitter isn&#039;t suitable for that purpose. Also regarding comment length, it&#039;s interesting to note that there are services like Kapost which do the very thing that Winer abhors - namely, allow you to write a long, detailed comment that could be promoted by the blog owner into a post on the blog itself.

5. See my comments on point 2. While a conversation at point B is a valid way to react to something at point A, isn&#039;t there a greater benefit (and a greater chance of results) if the conversation occurs at point A itself?</description>
		<content:encoded><![CDATA[<p>I addressed some of these issues in <a href="http://empoprise-bi.blogspot.com/2010/08/if-you-dont-discuss-blog-post-at-post.html" rel="nofollow">my own blog post</a>, but didn&#8217;t do a point-by-point response to Winer&#8217;s proposal. So in response to YOUR point-by-point response:</p>
<p>1. Agreed. I recently got back from nearly a week of traveling, and missed a lot of news during that period (I was lucky to happen to hear about the Intel-McAfee deal). I wouldn&#8217;t want to miss the ability to react to something because I was on a really long bike ride.</p>
<p>2. This is my major problem with Winer&#8217;s proposal. My interpretation of Winer&#8217;s preferred reaction is for everyone to write their own blog posts in response, like you did and like I did. But it&#8217;s difficult to find all of the blog posts that touch upon a particular topic (yours is the third one that I found on Winer&#8217;s post, and I don&#8217;t know if I&#8217;ll find many more), and it&#8217;s hard to have a discussion in a bunch of silos. </p>
<p>3. Having the perfect comment is akin to having the perfect blog post &#8211; and if you&#8217;re going to wait until it&#8217;s perfect, you might as well just publish a book.</p>
<p>4. Frankly, I&#8217;m not that hot on Twitter as a conversational medium either. You say later in your post that Twitter is effective &#8220;with good tools&#8221; &#8211; perhaps you can put enough lipstick on that pig, but if you need &#8220;good tools&#8221; to get Twitter to work, then Twitter isn&#8217;t suitable for that purpose. Also regarding comment length, it&#8217;s interesting to note that there are services like Kapost which do the very thing that Winer abhors &#8211; namely, allow you to write a long, detailed comment that could be promoted by the blog owner into a post on the blog itself.</p>
<p>5. See my comments on point 2. While a conversation at point B is a valid way to react to something at point A, isn&#8217;t there a greater benefit (and a greater chance of results) if the conversation occurs at point A itself?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

