<?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: Tumbleblogs and reblogging</title>
	<atom:link href="http://michael.biven.org/2008/01/28/tumbleblogs-and-reblogging/feed/" rel="self" type="application/rss+xml" />
	<link>http://michael.biven.org/2008/01/28/tumbleblogs-and-reblogging/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 04:09:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: whitneymcn</title>
		<link>http://michael.biven.org/2008/01/28/tumbleblogs-and-reblogging/#comment-105</link>
		<dc:creator>whitneymcn</dc:creator>
		<pubDate>Tue, 29 Jan 2008 19:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://michael.biven.org/2008/01/28/tumbleblogs-and-reblogging/#comment-105</guid>
		<description>Hey, Michael -

Joe Lazarus (on his Tumblog, of course) came right out and asked &lt;a href="http://joelaz.com/post/24732775" rel="nofollow"&gt;why reblog plugins are uncommon or nonexistent&lt;/a&gt; for the bigger blogging tools.

At first I was a bit skeptical, but quickly realized that I was overcomplicating the idea and it looks like I ended up thinking the same thing that you are.

I was actually thinking of bastardizing RSS for the data -- basically having a "reblog URL" that's a single-item RSS feed -- though I'm not sure that's the best idea.  It has the benefit of pulling the entire post content (as a Tumblr reblog does), as well as retaining all the information you need to automatically provide attribution.

With a format defined, a Wordpress plugin then seems very manageable:  each post has a reblog link/button/what-have-you similar to a trackback link.  You modify the WP post page to accept a reblog URL, pull the content from the URL and prepopulate the post page correctly.  (If you wanted to go crazy with the unsupported fun, you could even go the URI scheme route and have something like reblog:http://example.com/the-post-title/reblog/ to try to eliminate the copy/paste step.)

I'm going to try to play around with a test plugin a bit over the next couple of weeks, but I'm also very curious to see how you end up integrating the ideas you've outlined into what you're already doing.

- Whit</description>
		<content:encoded><![CDATA[<p>Hey, Michael -</p>
<p>Joe Lazarus (on his Tumblog, of course) came right out and asked <a href="http://joelaz.com/post/24732775" rel="nofollow">why reblog plugins are uncommon or nonexistent</a> for the bigger blogging tools.</p>
<p>At first I was a bit skeptical, but quickly realized that I was overcomplicating the idea and it looks like I ended up thinking the same thing that you are.</p>
<p>I was actually thinking of bastardizing RSS for the data &#8212; basically having a &#8220;reblog URL&#8221; that&#8217;s a single-item RSS feed &#8212; though I&#8217;m not sure that&#8217;s the best idea.  It has the benefit of pulling the entire post content (as a Tumblr reblog does), as well as retaining all the information you need to automatically provide attribution.</p>
<p>With a format defined, a Wordpress plugin then seems very manageable:  each post has a reblog link/button/what-have-you similar to a trackback link.  You modify the WP post page to accept a reblog URL, pull the content from the URL and prepopulate the post page correctly.  (If you wanted to go crazy with the unsupported fun, you could even go the URI scheme route and have something like reblog:http://example.com/the-post-title/reblog/ to try to eliminate the copy/paste step.)</p>
<p>I&#8217;m going to try to play around with a test plugin a bit over the next couple of weeks, but I&#8217;m also very curious to see how you end up integrating the ideas you&#8217;ve outlined into what you&#8217;re already doing.</p>
<p>- Whit</p>
]]></content:encoded>
	</item>
</channel>
</rss>
