<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"  xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
      <title>RSS4Lib</title>
      <link>http://www.rss4lib.com/</link>
      <description>Innovative ways libraries use RSS</description>
      <language>en</language>
      <copyright>Copyright 2012, Ken Varnum</copyright>
      <creativeCommons:license>http://creativecommons.org/licenses/by-nc/3.0/us/</creativeCommons:license>
      <lastBuildDate>Tue, 20 Mar 2012 14:39:01 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 
      <atom:link href="http://www.rss4lib.com/index.xml" rel="self" type="application/rss+xml" />
      <image>
            <url>http://www.rss4lib.com/images/RSS4Lib-Logo-sm.jpg</url>
            <title>RSS4Lib</title>
            <link>http://www.rss4lib.com/</link>
      </image>

      
      <item>
         <title>Pinterest</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[<p>Pinterest (<a href = "http://www.pinterest.com/">http://www.pinterest.com/</a>)is the latest social media tool to emerge from the fringes to the spotlight. It's something of a social media bulletin board for interesting images. Once you set up an account (invitation only, but you can request an invitation -- mine came within hours), you are given a bookmarklet tied to your account so that can start pinning images you find on the web.  

<p>When you're on a page that has an image you want to "pin," you click the bookmarklet. Pinterest shows you thumbnails of all the images on that particular page. You select the thumbnail image you want and the board you want to add it to (you can create as many boards as you like).

<h2>Uses of Pinterest for Libraries</h2>

<p>Pinterest has some interesting uses for libraries:

<ul>
<li>Some libraries are putting up cover images of new books, best sellers, or interesting books from the collection. The Darien Public Library, unsurprisingly, was an early adopter. The <a href = "http://pinterest.com/darienlibrary/">library's Pinterest page</a> has lists of books on various themes (&quot;<a href = "http://pinterest.com/darienlibrary/best-books-for-babies-toddlers/">Best Books for Babies & Toddlers</a>,&quot; &quot;<a href = "http://pinterest.com/darienlibrary/newbery-medal-winners/">Newberry Medal Winners</a>,&quot; and a board for their &quot;<a href = "http://pinterest.com/darienlibrary/one-book-one-community-2012/">One Book, One Community</a>&quot; reading program -- images related to the books selected for adults and children.</li>
<li>Promoting images from special collections. The Bluffton University's archives have a <a href = "http://pinterest.com/blufftonuasc/">Pinterest board</a> with selected images from their special collections and archives, including images of <a href = "http://pinterest.com/blufftonuasc/beanies/">beanies</a> (the hats, not the stuffed toys) and <a href = "http://pinterest.com/blufftonuasc/time-capsule-covers/">time capsule covers</a>. The Staley Library (<a href = "http://pinterest.com/staleylibrary/millikin-university-history/">Millikin University</a>) has a set of images related to the <a href = "http://pinterest.com/staleylibrary/millikin-university-history/">university's history</a>.</li>
<li>Put up photos of your library's staff along with brief bios or areas of specialization. I haven't been able to find a library doing this, but surely there is. Anyone?</li>
<li>Create boards related to popular books. The Westerville, Ohio, library has boards for <a href = "http://pinterest.com/rebecca_oneil/hunger-games/"><cite>The Hunger Games</cite></a> and <a href = "http://pinterest.com/westervlibrary/inspired-by-memoirs-of-a-geisha-westerville-librar/"><cite>Memoirs of a Geisha</cite></a>.</li>

</ul>

<h2>Copyright Questions</h2>

<p>One of the interesting challenges faced by Pinterest is that of copyright. Pinterest works by copying a thumbnail image of whatever it is that you pin. When you pin an image, the original is linked from the thumbnail. While probably not, strictly speaking, allowed by copyright law, I suspect Pinterest is operating under the theory that if Google can cache a thumbnail of an image (or even of an entire web page) for its search tools, then they can do the same.

<p>Complications arise, though, when one Pinterest use copies an image from another. You can &quot;repin&quot; another user's image to one of your own boards. At that point, you've created another copy of the image on your board that links to the &quot;original&quot; -- that is, the thumbnail on someone else's board -- and not to the original artist's. There's been quite a kerfuffle about this of late. 

<p>There's a very nice summary of the issues around &quot;pinning&quot; things at the University of Minnesota's <a href = "http://blog.lib.umn.edu/copyrightlibn/2012/03/pinterest-copyright-and-terms-of-service.html">Copyright Librarian blog</a> (and a follow-up <a href = "http://blog.lib.umn.edu/copyrightlibn/2012/03/a-few-clarifications-on-pinteresttoscopyright.html">post</a>) that I encourage you to read. It summarizes the issues far better than I can.

<h2>Pinterest via RSS</h2>
<p>Pinterest doesn't document its RSS feeds well, but I stumbled across <a href = "http://sociable.co/social-media/how-to-generate-rss-feeds-for-a-pinterest-user-and-specific-pinterest-boards/">some instructions</a> for how they can be made. 
<ol>
<li>To get an RSS feed for <em>all</em> of a particular user's boards, add "feed.rss" to the end of the user's Pinterest page. So, for example, for RSS feed for the Darien Public Libraries Pinterest account is <a href = "http://pinterest.com/darienlibrary/feed.rss" target = "_blank">http://pinterest.com/darienlibrary/<strong>feed.rss</strong></a>.</li>
<li>To get an RSS feed for <em>a specific board</em>, remove the end "/" from the board's URL and then add ".rss". So the Darien Library's Best Books for Babies and Toddlers board has the feed <a href = "http://pinterest.com/darienlibrary/best-books-for-babies-toddlers.rss" target = "_blank">http://pinterest.com/darienlibrary/best-books-for-babies-toddlers<strong>.rss</strong></a>.
</ol>
Happy syndicating! (And don't ask about the potential for copyright issues when we you re-publish an RSS feed of a Pinterest board  that itself has copyrighted but unlicensed images on it.)]]></description>
         <link>http://www.rss4lib.com/2012/03/pinterest.html</link>
         <guid>http://www.rss4lib.com/2012/03/pinterest.html</guid>
         <category>RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">copyright</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">interactive</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">rss</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">sharing</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">syndication</category>
        
         <pubDate>Tue, 20 Mar 2012 14:39:01 -0500</pubDate>
      </item>
      
      <item>
         <title>Curators&apos; Codes to Standardize &apos;Hat Tips&apos; and &apos;Vias&apos;</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[<p>An interesting proposal was made at SXSW this week to standardize the way we bloggers, and other content aggregators and curators, make reference to those from whom we get interesting tidbits that spark a thought (a 'hat tip') or are the source of our post (a 'via'). The glyphs are called <a href = "http://curatorscode.org/">Curator's Codes</a>. They are Unicode characters meant to be a standard (if not a real one, a standard of practice) for giving where credit is due:</p>
<table border='1'>
<tbody>
<tr>
<th width='150px'>Symbol</th>
<th>Purpose</th>
<th>HTML Code</th>
</tr>
<tr>
<td><span style="font-size: 150%; font-family:sans-serif;text-decoration:none;" >&#x1525;</span></span><br/>[Unicode 1525]</td>
<td>Via</td>
<td>&lt;span style="font-family:sans-serif;text-decoration:none;"&gt;&amp;#x1525;&lt;/span&gt;</td>
</tr>
<tr>
<td><span style="font-size: 150%; font-family:sans-serif;text-decoration:none;" >&#x21ac;</span><br/>[Unicode 21ac]</td>
<td>Hat Tip</td>
<td>&lt;span style="font-family:sans-serif;text-decoration:none;"&gt;&amp;#x21ac;&lt;/span&gt;</pre></td>
</tr>
</table>


<p>The symbol itself is the link to the source. Curator's Codes could be rendered in line, much like a brief citation, or used as freestanding blocks. Or, really, in any way that's sensible to the author. As in, for example, the hat tip for this post:  <a href="http://www.nytimes.com/2012/03/12/business/media/guidelines-proposed-for-content-aggregation-online.html" target="_blank" style="font-family:sans-serif;text-decoration:none;" >&#x1525;</a>&nbsp;David Carr, "A Code of Conduct for Content Aggregators".

<p>What's the point? To quote the folks at <a href = "http://curatorscode.org/" style="font-family:sans-serif;text-decoration:none;">&#x1525;</a>&nbsp;Curators Code:</p>

<blockquote>While we have systems in place for literary citation, image attribution, and scientific reference, we don't yet have a system that codifies the attribution of discovery in curation as a currency of the information economy, a system that treats discovery as the creative labor that it is. </blockquote>

<p>As we madly link from thing to thing, and others, in turn, pick up our post and run with it, quoting here, paraphrasing there, it's all too easy for something one author says to be lost in the expounded thoughts of another. Making a simple, standard, way for authors to cite others is a good thing. And to quickly indicate the kind of citation -- are you quoting or paraphrasing, or giving credit to someone else who sparked a thought? Standardization may be a good answer. It could even lead to better machine parsing of interconnections between blog posts, tweets, Facebook, etc. -- if adopted.

<p><strong>Update 13 March 2012</strong>: There's an interesting contrarian view at <a href = "http://brooksreview.net/2012/03/curation-and-blogging/">The Brooks Review</a>. ]]></description>
         <link>http://www.rss4lib.com/2012/03/curators-codes-to-standardize.html</link>
         <guid>http://www.rss4lib.com/2012/03/curators-codes-to-standardize.html</guid>
         <category>Public Blogs</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Public Blogs</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
         <pubDate>Mon, 12 Mar 2012 13:08:15 -0500</pubDate>
      </item>
      
      <item>
         <title>The Paradox of RSS and Web Scale Discovery</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description>Web Scale Discovery systems (products like Summon, EBSCO Discovery Service, Primo Central, and so on) make their customers love them through their comprehensiveness.  These systems index hundreds of millions -- some approach a billion items -- from scholarly and popular sources, library catalogs, institutional repositories, and more. No matter how esoteric the topic you are looking for, you&apos;re almost certain to find something that&apos;s related. Or close to being related.

With their vast reach, these discovery systems open the door to being almost omniscient alert services. Their coverage is vast, so whenever something new is published on a topic, it is likely to find its way into the discovery index. The challenge, it turns out, is in letting people know when something new is available.

Discovery systems are primarily retrieval systems. They cast a wide net, and sort their results in relevance order. When something new is added to the index and the same search is run, the new items appears somewhere in the list. This is the challenge for any kind of current awareness system (whether it is RSS or email alerts). 

If the system simply runs the search again and provides an RSS feed of the 100 most relevant results, for most searches, the new material will be nowhere near the top and the feed will contain exactly what you have already seen. For many topics, the new items won&apos;t even make the relevancy cut and will be excluded.

If the system runs the search and provides an RSS feed in reverse chronological order (newest items on top), the newest items may well be so far down the relevancy ranking that they are, in fact, nearly irrelevant. Try a couple experiments.  Do a search in your favorite tool and move down to the 5,000th result. Is it the item you&apos;ve been looking for all your life? Almost certainly not. Do the same search, but resort by publication date (newest first). Is the top result relevant to your query? Again, probably not.

So what is needed is some sort of hybrid, database structure. The items from the original search result set that pass some relevancy threshold need to be saved. Whenever new items are added, these new items are compared to the existing list. If they are more relevant than items in the previously seen list, they are added to an alert, and the list of previously seen and previously alerted items grows. Figuring out which are new (to the user) items is not trivial. 

Discovery and RSS are almost inherently at odds with one another. Any ideas on how to build a usable RSS feed to stay apprised of a topic?
</description>
         <link>http://www.rss4lib.com/2012/03/the-paradox-of-rss-and-web-sca.html</link>
         <guid>http://www.rss4lib.com/2012/03/the-paradox-of-rss-and-web-sca.html</guid>
         <category>Syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">current awareness</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">primo central</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">SDI</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">summon</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">web scale</category>
        
         <pubDate>Tue, 06 Mar 2012 09:25:14 -0500</pubDate>
      </item>
      
      <item>
         <title>Google Reader&apos;s A-Changin&apos;</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[Google <a href = "http://googlereader.blogspot.com/2011/10/upcoming-changes-to-reader-new-look-new.html">recently announced</a> that they are soon to relaunch Google Reader with a new design and are "going to bring Reader and Google+ closer together, so you can share the best of your feeds with just the right circles." Although I am not a huge fan of Google+ (Aside from the coolness of Hangouts, I haven't seen a reason to convert from Twitter and Facebook; my social circles don't see to be active in Google+), one of the things that has griped me about Reader is that there has been no way to share RSS items with my Plus circles. If nothing else, that will soon change.

Something else that will change is that the Google Reader API (an unofficial, undocumented, and formally unsupported API) will at some point be phased out. This doesn't make a difference to users of the Google Reader web site, but does matter for anyone who has been using Google Reader to track what has been read in applications like FeedDemon and others. 

If you want to get your data from Google, they will continue to offer an <a href = "http://en.wikipedia.org/wiki/OPML">OPML</a> download of your feeds, but will be augmenting the list of subscribed feeds with your other personal data, including your shared items, friends, likes, and starred items. What you do with them then is your business.]]></description>
         <link>http://www.rss4lib.com/2011/10/google-readers-a-changin.html</link>
         <guid>http://www.rss4lib.com/2011/10/google-readers-a-changin.html</guid>
         <category>RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">Google</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">Google Reader</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">rss</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">syndication</category>
        
         <pubDate>Tue, 25 Oct 2011 08:55:48 -0500</pubDate>
      </item>
      
      <item>
         <title>The Link to This Post Has a Half Life Measured in Hours</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[A recent research report by Hillary Mason of <a href = "http://bit.ly">Bit.ly</a> explores the lifespan of a link shared through social media. Her findings are that links shared via Twitter, Facebook, etc., have remarkably short life spans. She measured the half-life of shared links (the amount of time it took for a link to receive half as many clicks as in the previous time period) and learned that, for most links, the half life is two-three hours. (The outlier exception is links shared from YouTube, where the half life of a shared link is a whopping 7.4 hours.)

Graphs and the full report are available on the <a href = "http://blog.bitly.com/post/9887686919/you-just-shared-a-link-how-long-will-people-pay">bitly blog</a>.

Of course, this post is immortal, because as we all know, blog posts never die. Right?]]></description>
         <link>http://www.rss4lib.com/2011/09/the-link-to-this-post-has-a-ha.html</link>
         <guid>http://www.rss4lib.com/2011/09/the-link-to-this-post-has-a-ha.html</guid>
         <category>Syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
         <pubDate>Thu, 08 Sep 2011 12:17:40 -0500</pubDate>
      </item>
      
      <item>
         <title>Just How Dead is YOUR RSS Feed?</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[There has been another incarnation of the "RSS is dead" meme in the past weeks, with posts at <a href="http://techcrunch.com/2011/01/03/techcrunch-twitter-facebook-rss/">TechCrunch</a> and <a href="http://gigaom.com/2011/01/04/sure-rss-is-dead-just-like-the-web-is-dead/">GigaOM</a> debating the point.  The conclusion of these posts seems to be that RSS is continuing its gradual evolution from being perceived as an end-user tool to being viewed as plumbing.  And this is probably a good thing. 

While I still consume most of my "blog-like" news and commentary via an aggregator, I rely more on recommendations through my social networks for learning what's new.  Perhaps that's because I've become lazy about actively following lots of sources, and prefer the crowd to do the filtering for me.  Perhaps its because the blogs and news sources I follow are less frequently updated (I know this blog falls in that category).  Whatever the reason, I know my consumption patterns have changed.  And I'll wager that most people feel  too busy to sift through everything published in every publication they like, and prefer instead to find like-minded individuals who share things of interest.  Again, much like I do.

Still, if you're curious to learn how your feed is consumed (and don't use Feedburner or the equivalent), take a look at <a href="http://www.rss4lib.com/feedstats/yourstats.pl">RSS4Lib's YourStats</a> log file analysis program.  If you upload your publication's log files and tell it what your RSS feed URL is, it will show you where your RSS feed is consumed -- providing a good guess at your RSS readership.  You may find the numbers surprising (high or low).  ]]></description>
         <link>http://www.rss4lib.com/2011/01/just-how-dead-is-your-rss-feed.html</link>
         <guid>http://www.rss4lib.com/2011/01/just-how-dead-is-your-rss-feed.html</guid>
         <category>RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">feed</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">RSS</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">subscribers</category>
        
         <pubDate>Thu, 13 Jan 2011 15:14:00 -0500</pubDate>
      </item>
      
      <item>
         <title>Farewell, Bloglines, It&apos;s Been Swell</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[Bloglines, the venerable RSS reader that I -- and tens of thousands of others -- have used since 2005 is shutting down on October 1, 2010.  Bloglines is making it easy to continue your feedreading habit elsewhere, replacing their front page with the 3 simple steps to export your folders and subscriptions in <a href="http://en.wikipedia.org/wiki/Opml">OPML</a> format:

<div align = 'center'><a href = "http://www.rss4lib.com/images/20100913/bloglines-farewell.png"><img src = "http://www.rss4lib.com/images/20100913/bloglines-farewell-sm.png" width = "400" height = "225" alt = "Exporting Bloglines subscriptions into OPML (click for larger version)" border = "0"></a></div>

The inevitability of this, in retrospect, seems enormous, and I'm surprised my fondness for Bloglines' simplicity has made me put up with its quirky behavior.  (Quirky, of course, means almost constant brief outages on their perpetual beta version.)  Bloglines' move into selling advertisements on its front page (see <a href = "http://www.rss4lib.com/2008/08/bloglines-succumbs-to-advertis.html">Bloglines Succumbs to Advertising</a> from September 2008) was obviously not enough to bring in the revenue needed to keep the service.  When your only serious competitor is Google, I suspect almost nothing can save you.

In the blog post <a href = "http://blog.ask.com/2010/09/bloglines-update.html">announcing the shut down</a>, the trend behind the  news is made clear:
<blockquote>
The real-time information RSS was so astute at delivering (primarily, blog feeds) is now gained through conversations, and consuming this information has become a social experience. As Steve Gillmor pointed out in <a href="http://www.techcrunchit.com/2009/05/05/rest-in-peace-rss/">TechCrunch</a> last year, being locked in an RSS reader makes less and less sense to people as Twitter and Facebook dominate real-time information flow. Today RSS is the enabling technology - the infrastructure, the delivery system. RSS is a means to an end, not a consumer experience in and of itself. As a result, RSS aggregator usage has slowed significantly, and Bloglines isn't the only service to feel the impact. The writing is on the wall.
</blockquote>

I made a <a href = "http://www.rss4lib.com/2009/09/google_chrome_30_no_rss_does_i.html">similar point</a> about the phase change in RSS from being a commodity in itself to being a transport mechanism in September 2009.  Just as soundbite reporting in television and radio news changed that medium, so has 'textbite' exchange of information on the Internet.  The overwhelming force of the conversation in Twitter and Facebook -- where the granularity of information exchange is much smaller and seems to permeate the Internet with greater fluidity -- has changed the game.  

I'm not giving up on my RSS feeds (from blogs, news services, and other sources), but I'm switching to the only other game in town:  Google Reader.]]></description>
         <link>http://www.rss4lib.com/2010/09/farewell-bloglines-its-been-sw.html</link>
         <guid>http://www.rss4lib.com/2010/09/farewell-bloglines-its-been-sw.html</guid>
         <category>Syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">Bloglines</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">google reader</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">googleflow</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">rss</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">textbite</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">twitter</category>
        
         <pubDate>Mon, 13 Sep 2010 09:19:27 -0500</pubDate>
      </item>
      
      <item>
         <title>Survey Report on Librarians&apos; Use of Online Tools</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[A recent survey of <a href="http://webjunction.org/">WebJunction</a> users showed some interesting statistics on use of various online tools by librarians (the write-up is at at "<a href="http://blog.webjunctionworks.org/index.php/2010/07/06/library-staff-report-their-use-of-online-tools/">Library Staff Report Their Use of Online Tools</a>").

The trend from the survey indicates that social media (such as Facebook) is making inroads on email as a communication tool.  Of particular interest to me is the finding that RSS feeds are used daily or weekly by only 24% of respondents and used never by 50%.  Blogs are used daily or weekly by only 27%, and never by 40%. 

I know I spend much less time reading blogs (and, as those of you who read RSS4Lib in its native blog for or via RSS might notice, writing for one). I do wonder how much RSS usage is un-noticed or un-recognized by respondents; as RSS (and XML in general) become the way data move, do its consumers care how the data appear where they're consumed?

The survey results highlight differences between academic and public librarians (academic  librarians are more likely to use online tools than their public counterparts) and a series of interesting differences between urban and rural librarians.]]></description>
         <link>http://www.rss4lib.com/2010/08/survey-report-on-librarians-us.html</link>
         <guid>http://www.rss4lib.com/2010/08/survey-report-on-librarians-us.html</guid>
         <category>Syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">rss</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">Surveys</category>
        
         <pubDate>Wed, 11 Aug 2010 14:49:18 -0500</pubDate>
      </item>
      
      <item>
         <title>Google Chrome Out of Beta sans RSS</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[Google Chrome for Mac came out of beta today (see "<a href="http://googlemac.blogspot.com/2010/05/google-chrome-for-mac-ready-beta-now.html">Google Chrome for Mac: Ready, beta, now stable!</a>") with many new features, but not with built-in RSS support.  Even my first-generation iPhone can do better than that (granted, with a redirect through an Apple server to parse the XML of the feed into something intelligible).  An RSS feed still displays as a jumble of text:

<div align="center">
<a href="http://www.rss4lib.com/images/20100525/20100525-chrome-no-rss.png"><img src="http://www.rss4lib.com/images/20100525/20100525-chrome-no-rss-small.png" alt="Click for large image of Google Chrome's RSS Display" title="Google Chrome's RSS Display" border="0"></a>
</div>

Not that I spend a lot of time reading RSS feeds in my browser, but if I click on one (intentionally or otherwise), I really ought not get gibberish.  If Google intends Chrome to be a serious competitor in a marketplace of choice for Internet Explorer, Firefox, or Safari, it really ought not leave users in the lurch.  This is very un-Google-like behavior.

This is just the most recent in my series of rants about Google Chrome and RSS <a href="http://www.rss4lib.com/2008/09/google_chrome_and_rss.html">here</a>, <a href="http://www.rss4lib.com/2009/09/google_chrome_30_no_rss_does_i.html">here</a>, and <a href="http://www.rss4lib.com/2009/12/google_chrome_beta_for_mac_and.html">here</a>.]]></description>
         <link>http://www.rss4lib.com/2010/05/google-chrome-out-of-beta-sans.html</link>
         <guid>http://www.rss4lib.com/2010/05/google-chrome-out-of-beta-sans.html</guid>
         <category>RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">Apple</category>
        
         <pubDate>Tue, 25 May 2010 16:04:51 -0500</pubDate>
      </item>
      
      <item>
         <title>RSS Replay:  Read a Blog Archive at your Leisure</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[Found a new-to-you blog that you want to read, but you don't want to get sucked into it for the next few hours?  <a href="http://rssreplay.heroku.com/">RSS Replay</a> looks like the tool for you.  Give it an RSS feed and how often you want it to give you a new post, and it will do the rest.  You can specify a new item from the backfile every day, every few days, or other intervals.   You can also set a PageRank filter  so you only see posts that have PageRanks above a specific threshold (all, good, great, or best).

This brings "slow reading" to a much different level!

<div align="center">
<a href="http://www.rss4lib.com/images/20100426/rss-replay.png"><img src="http://www.rss4lib.com/images/20100426/rss-replay-sm.png" width="400" height="196" alt="RSS Replay screen shot"></a>
</div>]]></description>
         <link>http://www.rss4lib.com/2010/04/rss-replay-read-a-blog-archive.html</link>
         <guid>http://www.rss4lib.com/2010/04/rss-replay-read-a-blog-archive.html</guid>
         <category>RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">feeds</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">PageRank</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">slow reading</category>
        
         <pubDate>Mon, 26 Apr 2010 13:41:06 -0500</pubDate>
      </item>
      
      <item>
         <title>FreeMyFeed:  A Really (Poor) Clever Idea</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[Have you even wanted to subscribe to an RSS feed in Firefox, Safari, Internet Explorer, Bloglines or Google Reader (or anywhere else, for that matter), but discover that the feed is inconveniently served from behind a login-protected server?  We all have, I think. Well, now a free web service allows you to do just that.  As convenient as it is, this is a spectacularly poor idea.

<a href="http://freemyfeed.com/">FreeMyFeed</a> handily takes care of those pesky login problems.  You give it your feed URL, your login, and your password.  It then gives you an alternate URL at FreeMyFeed that contains your login information in an encoded way.  FreeMyFeed then acts as a proxy, grabbing the feed without storing your login credentials on its own server, and passing it along to your reader:

<div align="center"><a href = "http://www.rss4lib.com/images/20100118/freemyfeed-lg.png"><img src="http://www.rss4lib.com/images/20100118/freemyfeed-sm.png" width="450" height="231" alt="FreeMyFeed account set up screen" title="Click for full-size version" border = "0"></a></div>

So I created a COMPLETELY FAKE login for this blog's feed.  The login does not exist, does not work, and is (of course) not a real login to anything:  username rss4lib and password temp1234.  The FreeMyFeed link that encodes this is:<br>
http://freemyfeed.com/feed/aHR0cDovL3d3dy5yc3M0bGliLmNvbS9pbmRleC54bWw6OnJzczRsaWI6OkxzUGcwWHRrRktDUytJdkFrUTFMN0RvNk5BPT0=

Well, it is encrypted, but there's usually a good reason that a feed is behind a login.  This takes those feeds and puts them out in the public, where any search engine find them, index them, and expose your organization's secure information.  End runs around reasonable security are poor choices.  I would recommend that, if your organization has RSS behind a login, that you work with your technical group to block FreeMyFeed from accessing your site.  

To their credit, there is a fairly explicit disclaimer of the risks on the FreeMyFeed front page, that includes a warning to be careful and not to share your personalized URL with anyone (other than the feed readers, of course).  So if you must use this tool, use it only on your own browser, not on an aggregator to minimize the sharing of an all-access URL to your feed.  Don't be tempted.]]></description>
         <link>http://www.rss4lib.com/2010/01/freemyfeed-a-really-poor-cleve.html</link>
         <guid>http://www.rss4lib.com/2010/01/freemyfeed-a-really-poor-cleve.html</guid>
         <category>Reviews</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">RSS Tools</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Reviews</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">https</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">RSS</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">security</category>
        
         <pubDate>Mon, 18 Jan 2010 11:47:45 -0500</pubDate>
      </item>
      
      <item>
         <title>Upgrade Complete</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description>Looks like the upgrade went smoothly.  Please let me know in the comments or by email to rss4lib@gmail.com if you see anything wonky that you want to report.</description>
         <link>http://www.rss4lib.com/2010/01/upgrade-complete.html</link>
         <guid>http://www.rss4lib.com/2010/01/upgrade-complete.html</guid>
         <category>About the Blog</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">About the Blog</category>
        
        
         <pubDate>Wed, 13 Jan 2010 20:57:13 -0500</pubDate>
      </item>
      
      <item>
         <title>Upgrading RSS4Lib</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description>I&apos;m doing a long-overdue upgrade of Movable Type tonight.  Back, I hope, soon.</description>
         <link>http://www.rss4lib.com/2010/01/upgrading-rss4lib.html</link>
         <guid>http://www.rss4lib.com/2010/01/upgrading-rss4lib.html</guid>
         <category>About the Blog</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">About the Blog</category>
        
        
         <pubDate>Wed, 13 Jan 2010 20:05:13 -0500</pubDate>
      </item>
      
      <item>
         <title>Farewell to Full-Text Feeds?</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[I've noticed over time that the number of people who 'consume' RSS4Lib on <a href = "http://www.rss4lib.com">RSS4Lib.com</a> has declined steadily over the years.  Yet the number of feed subscribers is still steadily increasing (see <a href = "http://www.rss4lib.com/feedstats/index.pl?startdate=2010-01-10&enddate=2010-01-10">today's subscriber report</a> and has recently broken 2000).  

At the same time, few articles I post are read on RSS4Lib.com more than 100 times the day they are published, and most are viewed only a few times a day after that.  (Selected items in the backfile, thanks to Google and Bing, get more traffic than recently published items once the new posts have aged a few days.)

I suspect this trend holds true across many blogs, whether they're produced for love or money.  (This one, to be clear, is not produced as a moneymaking venture.)  

Some are suggesting that the days of full-text feeds are numbered (see "<a href = 'http://www.centernetworks.com/say-bye-bye-to-full-rss-feeds'>Say Bye Bye to Full RSS Feeds</a> and <a href = 'http://technorati.com/blogging/article/rss-whats-the-deal-in-2010/'>RSS: What's the Deal in 2010?</a>," as examples).  I'm curious to know if these commercial prognosticators are correct -- will bloggers tend to pull people toward the richness of their sites, even if there is no particularly strong monetary incentive to do so?  Or will full-text feeds continue to be the way to go?  I suspect a trend toward full text feeds (for blogs that are works of avocation) and snippet feeds (for those that are more vocational).  And I'll wager that this will break down (to oversimplify greatly) into an academic/commercial divide.]]></description>
         <link>http://www.rss4lib.com/2010/01/farewell-to-fulltext-feeds.html</link>
         <guid>http://www.rss4lib.com/2010/01/farewell-to-fulltext-feeds.html</guid>
         <category>Syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
         <pubDate>Mon, 11 Jan 2010 13:31:50 -0500</pubDate>
      </item>
      
      <item>
         <title>RSS Readers Not Dead Yet</title>
         <author>rss4lib@gmail.com (Ken Varnum)</author>
         <description><![CDATA[ReadWriteWeb says, "<a href = 'http://www.readwriteweb.com/archives/5_reasons_why_rss_readers_still_rock.php'>5 Reasons Why RSS Readers Still Rock</a>."  To summarize the post, here are the five reasons RSS readers are still relevant, according to RWW:

<ol>
<li>Control over Information Flow</li>
<li>Evolving User Interfaces</li>
<li>Tracking Twitter</li>
<li>Mobile News</li>
<li>Categorized News</li>
</ol>

This post is in response to an earlier RWW post, "<a href = 'http://www.readwriteweb.com/archives/rss_reader_market_in_disarray.php'>RSS Reader Market in Disarray, Continues to Decline</a>," which engendered a lively discussion in the comments.  

Dave Winer, a pioneer of RSS, noted in the comments to the more recent post that RSS readers get one thing fundamentally wrong:  they treat feeds like email by telling you how many unread messages you have and encouraging you to read each one.  (I'm one of those weirdos who cannot stand having messages, especially unread ones, hanging around in my inbox.  Having a growing tally of unread RSS items pushes me right over the edge and is the main reason I stopped consuming my feeds in my mail application.) 

A number of automated tools offer filters for RSS feeds (many have been reviewed or discussed here).  Most of them rely on explicit, user-defined keywords.  Others, like Twitter, rely on one's peers to identify the interesting stuff.  However, I have yet to find a tool that offers the best of keyword filtering (letting through articles on topics that are of likely interest) while still surprising and delighting me with nearly, but not quite, on-topic posts.  That's an incredibly delicate, arbitrary, and undefinable balance to strike.]]></description>
         <link>http://www.rss4lib.com/2010/01/rss-readers-not-dead-yet.html</link>
         <guid>http://www.rss4lib.com/2010/01/rss-readers-not-dead-yet.html</guid>
         <category>Syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#category">Syndication</category>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">rss</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">serendipity</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">syndication</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">Twitter</category>
        
         <pubDate>Wed, 06 Jan 2010 20:54:55 -0500</pubDate>
      </item>
      
   </channel>
</rss>

