<?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: Surfacing</title>
	<atom:link href="http://thetarquin.com/BlagSwitch/2010/02/07/surfacing/feed/" rel="self" type="application/rss+xml" />
	<link>http://thetarquin.com/BlagSwitch/2010/02/07/surfacing/</link>
	<description>Pull it.  You know you want to.</description>
	<lastBuildDate>Tue, 21 Dec 2010 20:19:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: The Tarquin</title>
		<link>http://thetarquin.com/BlagSwitch/2010/02/07/surfacing/comment-page-1/#comment-3306</link>
		<dc:creator>The Tarquin</dc:creator>
		<pubDate>Tue, 16 Feb 2010 06:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://thetarquin.com/BlagSwitch/?p=398#comment-3306</guid>
		<description>Interesting ideas.  I like the simplicity of it, and the (theoretical) ease of crossposting once it gets all set up.  I cringe a little inside every time I have to create two copies of a post whenever I cross post.  To me, that means inelegance, versioning issues, wasted energy, etc.

Also, good call on the comment subscriptions.  I&#039;ll look into WP plugins to handle that.</description>
		<content:encoded><![CDATA[<p>Interesting ideas.  I like the simplicity of it, and the (theoretical) ease of crossposting once it gets all set up.  I cringe a little inside every time I have to create two copies of a post whenever I cross post.  To me, that means inelegance, versioning issues, wasted energy, etc.</p>
<p>Also, good call on the comment subscriptions.  I&#8217;ll look into WP plugins to handle that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Sullins</title>
		<link>http://thetarquin.com/BlagSwitch/2010/02/07/surfacing/comment-page-1/#comment-3305</link>
		<dc:creator>Chris Sullins</dc:creator>
		<pubDate>Mon, 15 Feb 2010 20:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://thetarquin.com/BlagSwitch/?p=398#comment-3305</guid>
		<description>I think I&#039;d explain it somewhere, and feature links, but not too prominently.  They would look like closely-related blogs.  Maybe even a horizontal header menu for which to include.

One major difficulty would be canonical urls for the crossover articles.  Perhaps everything would need to redirect to blog.chrissullins.com, and the index pages would be the only thing different (besides some url parameter that specifies which blog they came from, which would define the style but not be included in the canonical url).

On a side note, I would also want some way to notify users of replies to their comments.  ;)  Wordpress doesn&#039;t do such a great job there.</description>
		<content:encoded><![CDATA[<p>I think I&#8217;d explain it somewhere, and feature links, but not too prominently.  They would look like closely-related blogs.  Maybe even a horizontal header menu for which to include.</p>
<p>One major difficulty would be canonical urls for the crossover articles.  Perhaps everything would need to redirect to blog.chrissullins.com, and the index pages would be the only thing different (besides some url parameter that specifies which blog they came from, which would define the style but not be included in the canonical url).</p>
<p>On a side note, I would also want some way to notify users of replies to their comments.  <img src='http://thetarquin.com/BlagSwitch/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />   WordPress doesn&#8217;t do such a great job there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Tarquin</title>
		<link>http://thetarquin.com/BlagSwitch/2010/02/07/surfacing/comment-page-1/#comment-3303</link>
		<dc:creator>The Tarquin</dc:creator>
		<pubDate>Wed, 10 Feb 2010 06:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://thetarquin.com/BlagSwitch/?p=398#comment-3303</guid>
		<description>That&#039;s a really good idea.  And with a little bit of PHP trickery it shouldn&#039;t be terribly difficult.  Would you want the end user to be aware of the fact that both sets of content are actually hosted on the same blog?  Or would the same blog just seem totally different based on point-of-entry?</description>
		<content:encoded><![CDATA[<p>That&#8217;s a really good idea.  And with a little bit of PHP trickery it shouldn&#8217;t be terribly difficult.  Would you want the end user to be aware of the fact that both sets of content are actually hosted on the same blog?  Or would the same blog just seem totally different based on point-of-entry?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Sullins</title>
		<link>http://thetarquin.com/BlagSwitch/2010/02/07/surfacing/comment-page-1/#comment-3302</link>
		<dc:creator>Chris Sullins</dc:creator>
		<pubDate>Tue, 09 Feb 2010 22:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://thetarquin.com/BlagSwitch/?p=398#comment-3302</guid>
		<description>I&#039;ve been considering having a few different entry points into my blog based on url.  I&#039;d write all the posts on the same backend, but categorize them differently.  Then on the various entry points I would only include various categories.  So blog.azureabstraction.com would have different content than blog.chrissullins.com, though there might be some overlap.

Then again, I haven&#039;t really gotten around to writing many coding entries.  Someday.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been considering having a few different entry points into my blog based on url.  I&#8217;d write all the posts on the same backend, but categorize them differently.  Then on the various entry points I would only include various categories.  So blog.azureabstraction.com would have different content than blog.chrissullins.com, though there might be some overlap.</p>
<p>Then again, I haven&#8217;t really gotten around to writing many coding entries.  Someday.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

