<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Google green, My Library, Reader search</title>
	<link>http://www.makeyougohmm.com/20070908/4780/</link>
	<description>Technology, music, video, art, news, reviews and muse on the web</description>
	<pubDate>Sat, 11 Oct 2008 20:45:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: TDavid</title>
		<link>http://www.makeyougohmm.com/20070908/4780/#comment-633557</link>
		<author>TDavid</author>
		<pubDate>Sun, 09 Sep 2007 15:14:01 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20070908/4780/#comment-633557</guid>
		<description>I just added beta.bloglines.com to the approved reader list [see &lt;a href="http://www.makeyougohmm.com/tmp/beta-bloglines-1.jpg" rel="nofollow"&gt;screenshot here&lt;/a&gt;]. The images should pass fine now in their beta client but I suspect when the beta period is over, they'll drop back to bloglines.com and that has been on the approved list for years. As explained &lt;a href="http://www.makeyougohmm.com/20041021/1091/" rel="nofollow"&gt;back in October 2004&lt;/a&gt;, not trying to block &lt;i&gt;legitimate &lt;/i&gt; online aggregators and readers. I apologize for the inconvenience, Nathan.

While on this discussion though it's trivial for these online reader companies to cache the images locally and serve them using &lt;i&gt;their bandwidth&lt;/i&gt;. Ask yourself who has more money: a company like ask.com or me? Why most RSS readers are setup to steal bandwidth from others is beyond me. I don't hotlink without permission and neither should they. And yet it's somehow become acceptable in the RSS world for vendors to hotlink.

The problem with the setup here is it's too hard keeping up with all the different aggregators and readers out there; separating the good companies from the bad. The list is becoming too long :( I might have to rethink and do like most everybody else: just let every tom, dick and harry hotlink the images. The last time I tried that though, and you should know as a reader there are a lot of images in posts here, the bandwidth usage for this site increased dramatically. Might be time for another experiment though, just to see what happens.

What do you think?</description>
		<content:encoded><![CDATA[<p>I just added beta.bloglines.com to the approved reader list [see <a href="http://www.makeyougohmm.com/tmp/beta-bloglines-1.jpg">screenshot here</a>]. The images should pass fine now in their beta client but I suspect when the beta period is over, they&#8217;ll drop back to bloglines.com and that has been on the approved list for years. As explained <a href="http://www.makeyougohmm.com/20041021/1091/">back in October 2004</a>, not trying to block <i>legitimate </i> online aggregators and readers. I apologize for the inconvenience, Nathan.</p>
<p>While on this discussion though it&#8217;s trivial for these online reader companies to cache the images locally and serve them using <i>their bandwidth</i>. Ask yourself who has more money: a company like ask.com or me? Why most RSS readers are setup to steal bandwidth from others is beyond me. I don&#8217;t hotlink without permission and neither should they. And yet it&#8217;s somehow become acceptable in the RSS world for vendors to hotlink.</p>
<p>The problem with the setup here is it&#8217;s too hard keeping up with all the different aggregators and readers out there; separating the good companies from the bad. The list is becoming too long <img src='http://www.makeyougohmm.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> I might have to rethink and do like most everybody else: just let every tom, dick and harry hotlink the images. The last time I tried that though, and you should know as a reader there are a lot of images in posts here, the bandwidth usage for this site increased dramatically. Might be time for another experiment though, just to see what happens.</p>
<p>What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TDavid</title>
		<link>http://www.makeyougohmm.com/20070908/4780/#comment-633552</link>
		<author>TDavid</author>
		<pubDate>Sun, 09 Sep 2007 14:50:23 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20070908/4780/#comment-633552</guid>
		<description>Nathan - you using the new beta bloglines client maybe? It shows fine in the old bloglines. I just have to update the script because they are serving images from a different location. There should be no blocked images for approved readers. And if you do a refresh in your browser cache here you'll never see those images.</description>
		<content:encoded><![CDATA[<p>Nathan - you using the new beta bloglines client maybe? It shows fine in the old bloglines. I just have to update the script because they are serving images from a different location. There should be no blocked images for approved readers. And if you do a refresh in your browser cache here you&#8217;ll never see those images.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Weinberg</title>
		<link>http://www.makeyougohmm.com/20070908/4780/#comment-633551</link>
		<author>Nathan Weinberg</author>
		<pubDate>Sun, 09 Sep 2007 14:38:20 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20070908/4780/#comment-633551</guid>
		<description>T, the image in this post only shows as "Can't see this image? Original image at makeyougohmm.com" in Bloglines (and, because of caching, shows just that image when I visit the post.  Whatever you're using to block image hotlinking, you should either turn it off for new posts, or turn it off for feed readers.</description>
		<content:encoded><![CDATA[<p>T, the image in this post only shows as &#8220;Can&#8217;t see this image? Original image at makeyougohmm.com&#8221; in Bloglines (and, because of caching, shows just that image when I visit the post.  Whatever you&#8217;re using to block image hotlinking, you should either turn it off for new posts, or turn it off for feed readers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
