<?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: MIME types and feed: again</title>
	<atom:link href="http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/</link>
	<description>Musings on just about everything.</description>
	<pubDate>Fri, 05 Dec 2008 10:12:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Pete Hopkins</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1023</link>
		<dc:creator>Pete Hopkins</dc:creator>
		<pubDate>Wed, 10 Dec 2003 17:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1023</guid>
		<description>Danny --&lt;br&gt;&lt;br&gt;TypePad's RSS isn't self-referential. There's a link back to the site itself, but not any RSS file on the site.&lt;br&gt;&lt;br&gt;_pEt3
</description>
		<content:encoded><![CDATA[<p>Danny &#8211;</p>
<p>TypePad&#8217;s RSS isn&#8217;t self-referential. There&#8217;s a link back to the site itself, but not any RSS file on the site.</p>
<p>_pEt3</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Reinacker</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1022</link>
		<dc:creator>Greg Reinacker</dc:creator>
		<pubDate>Mon, 08 Dec 2003 18:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1022</guid>
		<description>Yeah, it's Content-type...however, to get IIS to send a specific content-type for a certain file, you need access to the IIS admin console.
</description>
		<content:encoded><![CDATA[<p>Yeah, it&#8217;s Content-type&#8230;however, to get IIS to send a specific content-type for a certain file, you need access to the IIS admin console.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Weakliem</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1021</link>
		<dc:creator>Gordon Weakliem</dc:creator>
		<pubDate>Mon, 08 Dec 2003 18:18:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1021</guid>
		<description>I don't get your comment on being unable to change MIME types on the server, isn't it just the Content-Type header, or is there more to it?
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t get your comment on being unable to change MIME types on the server, isn&#8217;t it just the Content-Type header, or is there more to it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xt1 blog :: Subscribing to RSS Feeds</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1020</link>
		<dc:creator>xt1 blog :: Subscribing to RSS Feeds</dc:creator>
		<pubDate>Mon, 08 Dec 2003 14:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1020</guid>
		<description>Pingback
</description>
		<content:encoded><![CDATA[<p>Pingback</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1019</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Sun, 07 Dec 2003 23:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/12/07/mime-types-and-feed-again/#comment-1019</guid>
		<description>I initially argued against the MIME approach because of the need to make the server-side change. But after checking with a couple of hosting providers I'm pretty sure only a small number of people would have real problems. &lt;br&gt;&lt;br&gt;Re. this approach and RSS - RSS 1.0 (Movable Type, TypePad and many more) already has a link to the channel URI. RSS 2.0 can use a namespace-qualified element. Or (as Joe put it) it is another good reason to upgrade to Atom.&lt;br&gt;&lt;br&gt;My my, it looks like users of other Userland versions of RSS will just have to buy Radio Userland...&lt;br&gt;
</description>
		<content:encoded><![CDATA[<p>I initially argued against the MIME approach because of the need to make the server-side change. But after checking with a couple of hosting providers I&#8217;m pretty sure only a small number of people would have real problems. </p>
<p>Re. this approach and RSS - RSS 1.0 (Movable Type, TypePad and many more) already has a link to the channel URI. RSS 2.0 can use a namespace-qualified element. Or (as Joe put it) it is another good reason to upgrade to Atom.</p>
<p>My my, it looks like users of other Userland versions of RSS will just have to buy Radio Userland&#8230;<br />
</p>
]]></content:encoded>
	</item>
</channel>
</rss>
