<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

  <channel>
    <title>RSS category of Luke Hutteman's public virtual MemoryStream</title>
    <link>http://www.hutteman.com/weblog/cat_rss.html</link>
    <description>Get a complete rss feed (all categories) at &lt;a href="http://www.hutteman.com/weblog/rss.xml"&gt;http://www.hutteman.com/weblog/rss.xml&lt;/a&gt;</description>
    <dc:language>en-us</dc:language>
    <dc:creator>luke@hutteman.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2006-08-02T23:50:31-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.33" />
    <admin:errorReportsTo rdf:resource="mailto:luke@hutteman.com"/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
    

    <item>
      <title>SharpReader 0.9.7.0</title>
      <link>http://www.hutteman.com/weblog/2006/08/02-250.html</link>
      <description>SharpReader 0.9.7.0 is now available at sharpreader.net. Changes since the last version are: Run internal browser in restricted security zone in order to make IE responsible for blocking restricted content, instead of just doing so by parsing and stripping tags. Allow embedded CSS styles in item descriptions (was previously disabled because of javascript exploits that are now caught because of... (128 words)</description>
      <guid isPermaLink="false">250@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>SharpReader 0.9.7.0 is now available at <a href="http://www.sharpreader.net">sharpreader.net</a>.
<p>Changes since the last version are:
<ul>
	<li>Run internal browser in restricted security zone in order to make IE responsible for blocking restricted content, instead of just doing so by parsing and stripping tags.</li>
	<li>Allow embedded CSS styles in item descriptions (was previously disabled because of javascript exploits that are now caught because of the security zone).</li>
	<li>Support both &lt;commentRSS&gt; as well as &lt;commentRss&gt; as there was some <a href="http://wellformedweb.org/news/wfw_namespace_elements/"> confusion</a> as to the proper capitalization of this element.</li>
	<li>Fixed linebreak handling for some feeds.</li>
	<li>Improved handling of relative urls in atom feeds (like <a href="http://www.intertwingly.net">Sam Ruby</a>'s feed for instance).</li>
	<li>Now displaying enclosure links at the bottom of the item description.</li>
	<li>Fixed installer to no longer complain if only .NET 2.0 is installed.</li>
</ul>
]]></content:encoded>
              <category>RSS</category>
              <category>SharpReader</category>
      
      <dc:date>2006-08-02T23:50:31-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2006/08/02-250.html#comments</comments>
      
    </item>
    <item>
      <title>NASA &amp; RSS</title>
      <link>http://www.hutteman.com/weblog/2006/01/27-244.html</link>
      <description>I'm not exactly sure why, but someone forwarded me the feedvalidator results of a NASA RSS feed, and they fail miserably. There's empty &amp;lt;pubDate&amp;gt;s, javascript &amp;lt;link&amp;gt;s, unencoded HTML in the &amp;lt;description&amp;gt; that's not valid XML and therefore makes the entire document invalid, etc. Quite frankly, coming from NASA, I found it somewhat amusing... I mean, it's not like this stuff... (67 words)</description>
      <guid isPermaLink="false">244@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>I'm not exactly sure why, but someone forwarded me the <a href="http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.nasa.gov%2Frss%2Fnasa_labfeatures.rss">feedvalidator results</a> of a <a href="http://www.nasa.gov/rss/nasa_labfeatures.rss">NASA RSS feed</a>, and they fail miserably.</p>

<p>There's empty &lt;pubDate&gt;s, javascript &lt;link&gt;s, unencoded HTML in the &lt;description&gt; that's not valid XML and therefore makes the entire document invalid, etc.</p>

<p>Quite frankly, coming from NASA, I found it somewhat amusing... I mean, it's not like this stuff is exactly rocket science, is it?</p>]]></content:encoded>
              <category>RSS</category>
      
      <dc:date>2006-01-27T23:39:27-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2006/01/27-244.html#comments</comments>
      
    </item>
    <item>
      <title>Subscribed to Digg? better get written permission</title>
      <link>http://www.hutteman.com/weblog/2005/12/03-241.html</link>
      <description>For all of you who are subscribed to Digg's RSS feed: it looks like you now need written permission in order to use an aggregator. From their new TOS: 8. you will not use any robot, spider, scraper or other automated means to access the Site for any purpose without our express written permission. for some reason they chose not... (180 words)</description>
      <guid isPermaLink="false">241@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>For all of you who are subscribed to <a href="http://www.digg.com/">Digg</a>'s <a href="http://digg.com/rss/index.xml">RSS feed</a>: it looks like you now need written permission in order to use an aggregator. </p>

<p>From their new <a href="http://digg.com/tos">TOS</a>:</p>

<blockquote>
8. you will not use any robot, spider, scraper or other automated means to access the Site for any purpose without our express written permission.
</blockquote>

<p>for some reason they chose not to enforce this rule in their <a href="http://www.digg.com/robots.txt">robots.txt</a> though.</p>

<p>Oh, and if you, in an effort to stay fully compliant to their TOS, plan to just manually check their site instead, realize that registration is now required:</p>

<blockquote>
As a condition to using Services, you are required to register with Digg and select a password and screen name ("Digg User ID"). 
</blockquote>

<p>I guess <a href="http://www.slashdot.org/">slashdot</a> doesn't have to worry about <a href="http://www.alexa.com/data/details/traffic_details?&range=2y&size=large&compare_sites=slashdot.org&y=t&url=digg.com">digg overtaking them</a> anymore.</p>

<p><b>UPDATE:</b> They changed their TOS to allow RSS aggregators to automatically access their site. Search engine spiders officially still need written permission though, and registration is still required for use of their "services" (where services are defined to, among other things, include text, images and articles).</p>]]></content:encoded>
              <category>RSS</category>
      
      <dc:date>2005-12-03T09:22:38-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2005/12/03-241.html#comments</comments>
      
    </item>
    <item>
      <title>eBay supports RSS - kind of...</title>
      <link>http://www.hutteman.com/weblog/2005/11/13-236.html</link>
      <description>Arturo Zacarias (eBay) writes: RSS [...] is a technology that makes it easy to see updated headlines from websites or pages that you like. This year we have been working to incorporate this technology for members to utilize on eBay. [...] eBay Stores sellers are now able to set up a &quot;feed&quot; that will send out a regularly updated summary... (316 words)</description>
      <guid isPermaLink="false">236@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<a href="http://www2.ebay.com/aw/core/200511.shtml#2005-11-10143920">Arturo Zacarias (eBay) writes:</a>

<blockquote>
RSS [...] is a technology that makes it easy to see updated headlines from websites or pages that you like. This year we have been working to incorporate this technology for members to utilize on eBay.

<p>[...] eBay Stores sellers are now able to set up a "feed" that will send out a regularly updated summary of the most recently-listed items in their Store to people who subscribe to it. [...]

<p>If you're a Store owner who is interested in providing listings via RSS feeds, go to "Manage My Store > Listing Feeds (within Store Marketing)". Click on "Distribute your listings via RSS" and click "Apply". The RSS button should appear on the lower left hand side of your Store.

<p>[...]

<p>We are working to add RSS to other areas as well in the coming months, so stay tuned. 
</blockquote>

<p>Let me get this straight - they've been working for 10 months on the ability to generate a (really) simple xml file for a store, and they didn't even get around to allowing people to subscribe to search results?

<p>Though I can see some people might be interested in subscribing to an individual store, I think subscribing to search results is way more interesting. If I'm for instance looking to buy a used iPod, I could subscribe to a feed for some ebay electronics store, but I'd much rather subscribe to a search-feed for "iPod" and get results for all stores, as well as for individual sellers.

<p>He said they're "working to add RSS to other areas as well in the coming months", so hopefully search is coming up too at some time, but given how long it took for them to implement it for stores, there's no telling how long this will take.

<p>In the mean time though, there's always <a href="http://www.rssauction.com">rssauction.com</a> (or is it? it seems to be down at the moment).]]></content:encoded>
              <category>RSS</category>
      
      <dc:date>2005-11-13T23:36:24-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2005/11/13-236.html#comments</comments>
      
    </item>
    <item>
      <title>Feeds, well-formed XML and Vista</title>
      <link>http://www.hutteman.com/weblog/2005/11/04-235.html</link>
      <description>The Microsoft RSS Blog just announced that Vista will only accept RSS feeds that are well-formed XML. I agree with Nick, who commented &quot;This is the right thing to do, and I'm glad you're doing it - thanks&quot;. I'd like to add some emphasis to that statement though: &quot;This is the right thing to do, and I'm glad you're doing... (225 words)</description>
      <guid isPermaLink="false">235@http://www.hutteman.com/weblog/</guid>
      <content:encoded><![CDATA[<p>The Microsoft RSS Blog just announced that <a href="http://blogs.msdn.com/rssteam/archive/2005/11/03/489065.aspx">Vista will only accept RSS feeds that are well-formed XML</a>.
</p><p>
I agree with <a href="http://nick.typepad.com">Nick</a>, who commented "This is the right thing to do, and I'm glad you're doing it - thanks". I'd like to add some emphasis to that statement though: "This is the right thing to do, and I'm
glad <b><i>you're</i></b> doing it - thanks". 
</p><p>
See, neither <a href="http://www.feeddemon.com/">Nick's aggregator</a> nor <a href="http://www.sharpreader.net">mine</a> requires well-formed XML. This is because there are a lot of non-well-formed feeds out there, and the typical aggregator user doesn't care about <a href="http://www.w3.org/TR/REC-xml/#dt-wellformed">XML specs</a>, they just want to see the feed content. And if you're requiring well-formed XML, something as small as a single "&amp;" in a single post will invalidate the entire feed, for as long as that post remains in the feed (which can be weeks depending on the update frequency of the feed).
</p><p>
Microsoft being more strict than us has the following positive results though:
<ul>
<li>It will most likely reduce the number of invalid feeds out there, making it easier for <i>everyone</i> to parse feeds.</li>
<li>Microsoft gets positive press for "doing the right thing".</li>
<li>For those feeds that still break, it may be another reason for people to look for alternative aggregators that <i>can</i> read that feed they're interested in.</li>
</ul>
Maybe there's an <a href="http://diveintomark.org/archives/2004/01/08/postels-law">exception to Postel's law</a> after all.
</p>
]]></content:encoded>
              <category>RSS</category>
              <category>SharpReader</category>
      
      <dc:date>2005-11-04T18:55:39-05:00</dc:date>
            <comments>http://www.hutteman.com/weblog/2005/11/04-235.html#comments</comments>
      
    </item>


  </channel>
</rss>
