<?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: Types of Aggregators</title>
	<atom:link href="http://www.tenreasonswhy.com/weblog/2003/08/types-of-aggregators/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tenreasonswhy.com/weblog/2003/08/types-of-aggregators/</link>
	<description>Unclarifying the issues since 2000</description>
	<lastBuildDate>Sun, 10 Jul 2011 04:49:46 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Frederick Emrich</title>
		<link>http://www.tenreasonswhy.com/weblog/2003/08/types-of-aggregators/comment-page-1/#comment-244</link>
		<dc:creator>Frederick Emrich</dc:creator>
		<pubDate>Wed, 27 Aug 2003 20:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.tenreasonswhy.com/weblog/?p=534#comment-244</guid>
		<description>Yes, the benefit for me of integration would be one-click publishing.  I have to admit I am somewhat technologically hobbled because I am using an Earthlink account.  Earthlink uses the basic, minimal version of PERL required to run Movable Type.  This means that some features of MT (like Trackback) don&#039;t work correctly on my system.  This appears to be true of one-click publishing as well.  I could switch ISPs, but this would involve some complications I&#039;d rather avoid.  But without the one-click option, I&#039;m basically cutting and pasting urls when I use an aggregator.  I know, it&#039;s still better than blind surfing, but I can&#039;t help thinking how useful it could be to design an aggregator to work hand-in-glove with the weblog software.
Your point about flexibility is certainly valid, of course.  Perhaps what we are seeing here is the difference between a tech-savvy user (Greg) and a user who muddles through the tech stuff (me).  If my past record is any indication, I&#039;ll poke around for a while and eventually figure out a reader setup that meets my needs.
I&#039;ll check out SharpReader and see if I can get it to work for me.  Thanks for the suggestion.
</description>
		<content:encoded><![CDATA[<p>Yes, the benefit for me of integration would be one-click publishing.  I have to admit I am somewhat technologically hobbled because I am using an Earthlink account.  Earthlink uses the basic, minimal version of PERL required to run Movable Type.  This means that some features of MT (like Trackback) don&#8217;t work correctly on my system.  This appears to be true of one-click publishing as well.  I could switch ISPs, but this would involve some complications I&#8217;d rather avoid.  But without the one-click option, I&#8217;m basically cutting and pasting urls when I use an aggregator.  I know, it&#8217;s still better than blind surfing, but I can&#8217;t help thinking how useful it could be to design an aggregator to work hand-in-glove with the weblog software.<br />
Your point about flexibility is certainly valid, of course.  Perhaps what we are seeing here is the difference between a tech-savvy user (Greg) and a user who muddles through the tech stuff (me).  If my past record is any indication, I&#8217;ll poke around for a while and eventually figure out a reader setup that meets my needs.<br />
I&#8217;ll check out SharpReader and see if I can get it to work for me.  Thanks for the suggestion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.tenreasonswhy.com/weblog/2003/08/types-of-aggregators/comment-page-1/#comment-243</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Tue, 19 Aug 2003 18:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.tenreasonswhy.com/weblog/?p=534#comment-243</guid>
		<description>Hmm. I don&#039;t see any significant benefit to having content aggregation integrated with my weblog authoring tool. So enlighten me -- what&#039;s the benefit?
The only benefit I can think of is improving the ease of publishing an item in the aggregator to your weblog, but that doesn&#039;t require much. E.g. &lt;a href=&quot;http://www.sharpreader.net&quot; rel=&quot;nofollow&quot;&gt;SharpReader&lt;/a&gt; has a &lt;a href=&quot;http://www.hutteman.com/weblog/2003/04/17-68.html&quot; rel=&quot;nofollow&quot;&gt;BlogThis URL&lt;/a&gt; plug-in for Movable Type that lets you right-click on an item and send it to your &quot;Post to MT Weblog&quot; page.
Besides, I think what will improve the ease of publishing items from an aggregator to a weblog isn&#039;t necessarily direct integration of the two tools -- which likely locks you into one vendor&#039;s product -- stability of the specs and APIs that are caught up in the personality wars.
Aggregation and authoring are separate (but perhaps loosely related) processes. I&#039;d rather be able to use the aggregator of my choice with the weblog authoring tool of my choice through stable interfaces.
</description>
		<content:encoded><![CDATA[<p>Hmm. I don&#8217;t see any significant benefit to having content aggregation integrated with my weblog authoring tool. So enlighten me &#8212; what&#8217;s the benefit?<br />
The only benefit I can think of is improving the ease of publishing an item in the aggregator to your weblog, but that doesn&#8217;t require much. E.g. <a href="http://www.sharpreader.net" rel="nofollow">SharpReader</a> has a <a href="http://www.hutteman.com/weblog/2003/04/17-68.html" rel="nofollow">BlogThis URL</a> plug-in for Movable Type that lets you right-click on an item and send it to your &#8220;Post to MT Weblog&#8221; page.<br />
Besides, I think what will improve the ease of publishing items from an aggregator to a weblog isn&#8217;t necessarily direct integration of the two tools &#8212; which likely locks you into one vendor&#8217;s product &#8212; stability of the specs and APIs that are caught up in the personality wars.<br />
Aggregation and authoring are separate (but perhaps loosely related) processes. I&#8217;d rather be able to use the aggregator of my choice with the weblog authoring tool of my choice through stable interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Kleymeyer</title>
		<link>http://www.tenreasonswhy.com/weblog/2003/08/types-of-aggregators/comment-page-1/#comment-242</link>
		<dc:creator>Alan Kleymeyer</dc:creator>
		<pubDate>Tue, 19 Aug 2003 18:10:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.tenreasonswhy.com/weblog/?p=534#comment-242</guid>
		<description>The RU aggregator is not for me either. But how many other weblog services even offer an aggregator? Radio has some great technology and the aggregator issue is easily resolved. SocialDynamX is on its way to &lt;a href=&quot;http://www.socialdynamx.net/faqs&quot; rel=&quot;nofollow&quot;&gt;resolving it&lt;/a&gt;.
</description>
		<content:encoded><![CDATA[<p>The RU aggregator is not for me either. But how many other weblog services even offer an aggregator? Radio has some great technology and the aggregator issue is easily resolved. SocialDynamX is on its way to <a href="http://www.socialdynamx.net/faqs" rel="nofollow">resolving it</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederick Emrich</title>
		<link>http://www.tenreasonswhy.com/weblog/2003/08/types-of-aggregators/comment-page-1/#comment-241</link>
		<dc:creator>Frederick Emrich</dc:creator>
		<pubDate>Tue, 19 Aug 2003 04:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.tenreasonswhy.com/weblog/?p=534#comment-241</guid>
		<description>I tend to agree, with the caveat that I did like the way that RUl provided a reader integrated with weblog.  That wasn&#039;t enough to get me to go with Radio--I much prefer Movable Type.  But I am still frustrated at getting a reader that integrates smoothly with my current setup.  Any suggestions for a reader that a not-particularly-tech-oriented-but-literate-with-a-good-manual blogger could integrate with MT?
</description>
		<content:encoded><![CDATA[<p>I tend to agree, with the caveat that I did like the way that RUl provided a reader integrated with weblog.  That wasn&#8217;t enough to get me to go with Radio&#8211;I much prefer Movable Type.  But I am still frustrated at getting a reader that integrates smoothly with my current setup.  Any suggestions for a reader that a not-particularly-tech-oriented-but-literate-with-a-good-manual blogger could integrate with MT?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

