<?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: Syndicating Your Blog at SQLServerPedia</title>
	<atom:link href="http://www.brentozar.com/archive/2009/01/syndicating-your-blog-at-sqlserverpedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brentozar.com/archive/2009/01/syndicating-your-blog-at-sqlserverpedia/</link>
	<description>Your technology pain-relief experts.</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:37:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brent Ozar</title>
		<link>http://www.brentozar.com/archive/2009/01/syndicating-your-blog-at-sqlserverpedia/comment-page-1/#comment-7111</link>
		<dc:creator>Brent Ozar</dc:creator>
		<pubDate>Thu, 29 Jan 2009 13:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2328#comment-7111</guid>
		<description>First, yeah, the duplicate content is going to be a problem.  I&#039;m going to have to build a separate RSS feed for non-syndicated posts at SSP, I think. 
 
Second, the &quot;related posts&quot; stuff doesn&#039;t show up in RSS.  I *can* enable that, but I haven&#039;t because I wasn&#039;t sure how the community would take that. I hate seeing stuff like that in my feeds.  What do you think? </description>
		<content:encoded><![CDATA[<p>First, yeah, the duplicate content is going to be a problem.  I&#039;m going to have to build a separate RSS feed for non-syndicated posts at SSP, I think. </p>
<p>Second, the &quot;related posts&quot; stuff doesn&#039;t show up in RSS.  I *can* enable that, but I haven&#039;t because I wasn&#039;t sure how the community would take that. I hate seeing stuff like that in my feeds.  What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Boek</title>
		<link>http://www.brentozar.com/archive/2009/01/syndicating-your-blog-at-sqlserverpedia/comment-page-1/#comment-7102</link>
		<dc:creator>Rob Boek</dc:creator>
		<pubDate>Wed, 28 Jan 2009 22:26:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2328#comment-7102</guid>
		<description>I have a few more thoughts. 
 
It seems like the syndicated bloggers are now coming through the main SSP feed. This is causing a lot of duplicate content for me as I am already subscribed to the individual blogs. I am interesting in getting SSP news, but I&#039;m not interesting in weeding through a ton of duplicate content just to get the occasional interesting new post. 
 
I understand your concern about syncing comments to SSP which is why I suggested linking back to the original post to see the comments. The &quot;related posts&quot; widget that you mentioned doesn&#039;t seem to show up in the SSP RSS feed anyway. </description>
		<content:encoded><![CDATA[<p>I have a few more thoughts. </p>
<p>It seems like the syndicated bloggers are now coming through the main SSP feed. This is causing a lot of duplicate content for me as I am already subscribed to the individual blogs. I am interesting in getting SSP news, but I&#039;m not interesting in weeding through a ton of duplicate content just to get the occasional interesting new post. </p>
<p>I understand your concern about syncing comments to SSP which is why I suggested linking back to the original post to see the comments. The &quot;related posts&quot; widget that you mentioned doesn&#039;t seem to show up in the SSP RSS feed anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Ozar</title>
		<link>http://www.brentozar.com/archive/2009/01/syndicating-your-blog-at-sqlserverpedia/comment-page-1/#comment-7101</link>
		<dc:creator>Brent Ozar</dc:creator>
		<pubDate>Wed, 28 Jan 2009 21:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2328#comment-7101</guid>
		<description>You bring up an interesting point.  We can sorta kinda do that - we can import the permalinks along with the blog.  So for example, if you clicked on the post name, you would go over to the original person&#039;s blog to read it and to post comments. 
 
The problem is that if we do that, you lose one of the biggest benefits: the &quot;related posts&quot; thing at the bottom of every post.  The idea is that new up-and-coming bloggers will be able to get their posts featured at the bottom of more well-known posters.  They would not have that ability if the post details were at each individual site. 
 
I do wish that something like IntenseDebate would have a unified set of comments across both SQLServerPedia and the original blogger&#039;s post, but then we have to worry about distributed spam tracking.  What if a poster lets spam comments in (and I see that happen all the time on individual blogs)?  I can&#039;t have the SSP comments chock full of spam. 
 
It&#039;s a drawback, and it&#039;s a compromise between individual blogging versus syndication.  I look at it this way: if you choose to go with another blogging host, like another SQL group of bloggers, then the question would be moot - there&#039;d only be one place for comments, and it wouldn&#039;t be the domain you owned.  That&#039;s how I sleep at night, anyway, ha ha ho ho. </description>
		<content:encoded><![CDATA[<p>You bring up an interesting point.  We can sorta kinda do that &#8211; we can import the permalinks along with the blog.  So for example, if you clicked on the post name, you would go over to the original person&#039;s blog to read it and to post comments. </p>
<p>The problem is that if we do that, you lose one of the biggest benefits: the &quot;related posts&quot; thing at the bottom of every post.  The idea is that new up-and-coming bloggers will be able to get their posts featured at the bottom of more well-known posters.  They would not have that ability if the post details were at each individual site. </p>
<p>I do wish that something like IntenseDebate would have a unified set of comments across both SQLServerPedia and the original blogger&#039;s post, but then we have to worry about distributed spam tracking.  What if a poster lets spam comments in (and I see that happen all the time on individual blogs)?  I can&#039;t have the SSP comments chock full of spam. </p>
<p>It&#039;s a drawback, and it&#039;s a compromise between individual blogging versus syndication.  I look at it this way: if you choose to go with another blogging host, like another SQL group of bloggers, then the question would be moot &#8211; there&#039;d only be one place for comments, and it wouldn&#039;t be the domain you owned.  That&#039;s how I sleep at night, anyway, ha ha ho ho.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Boek</title>
		<link>http://www.brentozar.com/archive/2009/01/syndicating-your-blog-at-sqlserverpedia/comment-page-1/#comment-7100</link>
		<dc:creator>Rob Boek</dc:creator>
		<pubDate>Wed, 28 Jan 2009 21:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2328#comment-7100</guid>
		<description>One issue I have with syndication is comments. The way it&#039;s setup right now, it seems like there are two separate places for comments. I think it would be much nicer if you could disable commenting on SQLServerPedia and somehow direct back to the original post for comments. 
 </description>
		<content:encoded><![CDATA[<p>One issue I have with syndication is comments. The way it&#039;s setup right now, it seems like there are two separate places for comments. I think it would be much nicer if you could disable commenting on SQLServerPedia and somehow direct back to the original post for comments.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 539/549 objects using disk: basic

Served from: www.brentozar.com @ 2012-02-09 05:33:12 -->
