<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for spugbrap's old wordpress blog</title>
	<atom:link href="http://spugbrap.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://spugbrap.wordpress.com</link>
	<description>Dave's old wordpress.com blog (Current blog is located at: http://www.spugbrap.com/blog)</description>
	<lastBuildDate>Wed, 18 Oct 2006 19:38:22 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on spugbrap&#8217;s new blog by Clint</title>
		<link>http://spugbrap.wordpress.com/2006/10/07/spugbraps-new-blog/#comment-3</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Wed, 18 Oct 2006 19:38:22 +0000</pubDate>
		<guid isPermaLink="false">http://spugbrap.wordpress.com/2006/10/07/spugbraps-new-blog/#comment-3</guid>
		<description>For picture tagging, apparantly you can put the tags inside JPGs themself using either EXIF or ITPC, I think ITPC.  Christian is doing this.  I will be doing this in the future.  FlickR auto-recognizes these and adds tags appropriately.  It makes more sense for meta-data to live in the actual file it is meta of, rather than separately, where a program (like my flickr uploader that I wrote) must exist to couple the meta-data with the data itself.

I hear you on the geek vs personal / blog vs multiblog debate.  I chose one, but use tag heirarchies.

One thing Wordpress supports is a custom homepage for your blog.  I&#039;ve thought about implementing one which asks &quot;which &#039;blog&#039; do you want to read?  Clint&#039;s media blog, Clint&#039;s politics blog, Clint&#039;s technology blog, etc.&quot;

In effect, it would make 1 blog into several &quot;virtual blogs&quot;...

What I would REALLY like would be categories with checkboxes, like some BitTorrent trackers have (check out http://www.myspleen.com).  Simply check and uncheck the categories you are interested in, hit save, either a cookie is sent to your browser if you are not logged in, or it is saved to your wordpress account if you are logged in, and future visits to the blog would display only the categories you are interested in.   With grey AJAX links to expand posts you aren&#039;t interested in.  That would rule!</description>
		<content:encoded><![CDATA[<p>For picture tagging, apparantly you can put the tags inside JPGs themself using either EXIF or ITPC, I think ITPC.  Christian is doing this.  I will be doing this in the future.  FlickR auto-recognizes these and adds tags appropriately.  It makes more sense for meta-data to live in the actual file it is meta of, rather than separately, where a program (like my flickr uploader that I wrote) must exist to couple the meta-data with the data itself.</p>
<p>I hear you on the geek vs personal / blog vs multiblog debate.  I chose one, but use tag heirarchies.</p>
<p>One thing WordPress supports is a custom homepage for your blog.  I&#8217;ve thought about implementing one which asks &#8220;which &#8216;blog&#8217; do you want to read?  Clint&#8217;s media blog, Clint&#8217;s politics blog, Clint&#8217;s technology blog, etc.&#8221;</p>
<p>In effect, it would make 1 blog into several &#8220;virtual blogs&#8221;&#8230;</p>
<p>What I would REALLY like would be categories with checkboxes, like some BitTorrent trackers have (check out <a href="http://www.myspleen.com)" rel="nofollow">http://www.myspleen.com)</a>.  Simply check and uncheck the categories you are interested in, hit save, either a cookie is sent to your browser if you are not logged in, or it is saved to your wordpress account if you are logged in, and future visits to the blog would display only the categories you are interested in.   With grey AJAX links to expand posts you aren&#8217;t interested in.  That would rule!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
