<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
   <title>RSS4Lib</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/" />
   <link rel="self" type="application/atom+xml" href="http://www.rss4lib.com/atom.xml" />
   <link rel="license" type="application/rdf+xml" href="http://creativecommons.org/licenses/by-nc/3.0/us/rdf" />
   <id>tag:www.rss4lib.com,2011://1</id>
   <updated>2011-10-25T13:04:54Z</updated>
   <subtitle>Innovative ways libraries use RSS</subtitle>
   <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.34-en</generator>


<entry>
   <title>Google Reader&apos;s A-Changin&apos;</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2011/10/google-readers-a-changin.html" />
   <id>tag:www.rss4lib.com,2011://1.287</id>
   
   <published>2011-10-25T12:55:48Z</published>
   <updated>2011-10-25T13:04:54Z</updated>
   
   <summary>Google recently announced that they are soon to relaunch Google Reader with a new design and are &quot;going to bring Reader and Google+ closer together, so you can share the best of your feeds with just the right circles.&quot; Although...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="206" label="Google" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="284" label="Google Reader" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="6" label="rss" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="93" label="syndication" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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.]]>
      
   </content>
</entry>

<entry>
   <title>The Link to This Post Has a Half Life Measured in Hours</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2011/09/the-link-to-this-post-has-a-ha.html" />
   <id>tag:www.rss4lib.com,2011://1.286</id>
   
   <published>2011-09-08T16:17:40Z</published>
   <updated>2011-09-08T16:26:00Z</updated>
   
   <summary>A recent research report by Hillary Mason of Bit.ly 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...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="Syndication" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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?]]>
      
   </content>
</entry>

<entry>
   <title>Just How Dead is YOUR RSS Feed?</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2011/01/just-how-dead-is-your-rss-feed.html" />
   <id>tag:www.rss4lib.com,2011://1.285</id>
   
   <published>2011-01-13T20:14:00Z</published>
   <updated>2011-01-13T20:42:13Z</updated>
   
   <summary>There has been another incarnation of the &quot;RSS is dead&quot; meme in the past weeks, with posts at TechCrunch and GigaOM debating the point. The conclusion of these posts seems to be that RSS is continuing its gradual evolution from...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="283" label="feed" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="8" label="RSS" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="85" label="subscribers" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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).  ]]>
      
   </content>
</entry>

<entry>
   <title>Farewell, Bloglines, It&apos;s Been Swell</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/09/farewell-bloglines-its-been-sw.html" />
   <id>tag:www.rss4lib.com,2010://1.284</id>
   
   <published>2010-09-13T13:19:27Z</published>
   <updated>2010-09-13T13:45:06Z</updated>
   
   <summary>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...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
      <category term="Syndication" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="117" label="Bloglines" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="280" label="google reader" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="281" label="googleflow" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="6" label="rss" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="282" label="textbite" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="254" label="twitter" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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.]]>
      
   </content>
</entry>

<entry>
   <title>Survey Report on Librarians&apos; Use of Online Tools</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/08/survey-report-on-librarians-us.html" />
   <id>tag:www.rss4lib.com,2010://1.283</id>
   
   <published>2010-08-11T18:49:18Z</published>
   <updated>2010-08-11T20:33:49Z</updated>
   
   <summary>A recent survey of WebJunction users showed some interesting statistics on use of various online tools by librarians (the write-up is at at &quot;Library Staff Report Their Use of Online Tools&quot;). The trend from the survey indicates that social media...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="Syndication" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="6" label="rss" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="31" label="Surveys" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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.]]>
      
   </content>
</entry>

<entry>
   <title>Google Chrome Out of Beta sans RSS</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/05/google-chrome-out-of-beta-sans.html" />
   <id>tag:www.rss4lib.com,2010://1.282</id>
   
   <published>2010-05-25T20:04:51Z</published>
   <updated>2010-05-25T20:17:45Z</updated>
   
   <summary>Google Chrome for Mac came out of beta today (see &quot;Google Chrome for Mac: Ready, beta, now stable!&quot;) with many new features, but not with built-in RSS support. Even my first-generation iPhone can do better than that (granted, with a...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="278" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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>.]]>
      
   </content>
</entry>

<entry>
   <title>RSS Replay:  Read a Blog Archive at your Leisure</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/04/rss-replay-read-a-blog-archive.html" />
   <id>tag:www.rss4lib.com,2010://1.281</id>
   
   <published>2010-04-26T17:41:06Z</published>
   <updated>2010-04-26T17:55:52Z</updated>
   
   <summary>Found a new-to-you blog that you want to read, but you don&apos;t want to get sucked into it for the next few hours? RSS Replay looks like the tool for you. Give it an RSS feed and how often you...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="49" label="feeds" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="274" label="PageRank" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="276" label="slow reading" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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>]]>
      
   </content>
</entry>

<entry>
   <title>FreeMyFeed:  A Really (Poor) Clever Idea</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/01/freemyfeed-a-really-poor-cleve.html" />
   <id>tag:www.rss4lib.com,2010://1.280</id>
   
   <published>2010-01-18T16:47:45Z</published>
   <updated>2010-09-28T12:46:48Z</updated>
   
   <summary>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...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
      <category term="Reviews" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="271" label="https" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="8" label="RSS" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="272" label="security" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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.]]>
      
   </content>
</entry>

<entry>
   <title>Upgrade Complete</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/01/upgrade-complete.html" />
   <id>tag:www.rss4lib.com,2010://1.279</id>
   
   <published>2010-01-14T01:57:13Z</published>
   <updated>2010-01-14T02:19:04Z</updated>
   
   <summary>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....</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="About the Blog" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      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.
      
   </content>
</entry>

<entry>
   <title>Upgrading RSS4Lib</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/01/upgrading-rss4lib.html" />
   <id>tag:www.rss4lib.com,2010://1.278</id>
   
   <published>2010-01-14T01:05:13Z</published>
   <updated>2010-01-14T01:07:10Z</updated>
   
   <summary>I&apos;m doing a long-overdue upgrade of Movable Type tonight. Back, I hope, soon....</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="About the Blog" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      I&apos;m doing a long-overdue upgrade of Movable Type tonight.  Back, I hope, soon.
      
   </content>
</entry>

<entry>
   <title>Farewell to Full-Text Feeds?</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/01/farewell-to-fulltext-feeds.html" />
   <id>tag:www.rss4lib.com,2010://1.277</id>
   
   <published>2010-01-11T18:31:50Z</published>
   <updated>2010-01-11T18:47:10Z</updated>
   
   <summary>I&apos;ve noticed over time that the number of people who &apos;consume&apos; RSS4Lib on RSS4Lib.com has declined steadily over the years. Yet the number of feed subscribers is still steadily increasing (see today&apos;s subscriber report and has recently broken 2000). At...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="Syndication" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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.]]>
      
   </content>
</entry>

<entry>
   <title>RSS Readers Not Dead Yet</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2010/01/rss-readers-not-dead-yet.html" />
   <id>tag:www.rss4lib.com,2010://1.276</id>
   
   <published>2010-01-07T01:54:55Z</published>
   <updated>2010-01-07T02:23:16Z</updated>
   
   <summary>ReadWriteWeb says, &quot;5 Reasons Why RSS Readers Still Rock.&quot; To summarize the post, here are the five reasons RSS readers are still relevant, according to RWW: Control over Information Flow Evolving User Interfaces Tracking Twitter Mobile News Categorized News This...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="Syndication" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="6" label="rss" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="86" label="serendipity" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="93" label="syndication" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="255" label="Twitter" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![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.]]>
      
   </content>
</entry>

<entry>
   <title>RSS to Twitter Tools</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2009/12/rss-to-twitter-tools.html" />
   <id>tag:www.rss4lib.com,2009://1.275</id>
   
   <published>2009-12-31T16:18:25Z</published>
   <updated>2009-12-31T16:43:45Z</updated>
   
   <summary>Twitter makes it easy for you to post updates to your followers, or the world at large. It&apos;s well suited for quick updates, but less for &quot;bloggy&quot; content. How do you get your blog into Twitter without any particular effort?...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![CDATA[Twitter makes it easy for you to post updates to your followers, or the world at large.  It's well suited for quick updates, but less for "bloggy" content.  How do you get your blog into Twitter without any particular effort?  There are a variety of tools to help you do this.  Here's a quick overview of some of these tools.  Use one I don't mention?  Let me know in the comments -- I'll update the post as needed.  

All of these tools post on  your behalf, which means that they use your Twitter account login and password behind the scenes.  You provide the tool with your Twitter account login and password.  You may wish to set up a separate Twitter account just for your blog if you're concerned about sharing your Twitter login with a 3rd party.  

<h2>FeedNest</h2>
<p><a href = "http://feednest.com/">FeedNest</a>. This tool asks you for a bit more information about your feed than do others, so that users can search FeedNest and find your blog's content.  It asks you to describe your blog's content and give the name of the site.</p>

<h2>RSS Twitter</h2>
<p><a href = "http://feald.qcom/index/rsstwitter">RSS Twitter</a>.  A simple interface -- your Twitter account and your blog's RSS feed.</p>

<h2>TwitterFeed</h2>
<p><a href = "http://twitterfeed.com/">TwitterFeed</a>.  I've used this tool for this blog in the past.  It offers some statistics tracking for how your posts are read (by redirecting the links from Twitter tweets through its own server).</p>

<h2>Twitter Tools</h2>
<p><a href = "http://alexking.org/projects/wordpress">Twitter Tools</a> (WordPress plugin).  If you publish your blog with WordPress, there's a plugin that will automatically send a tweet to Twitter when you publish your blog post.</p>

<h2>Missing your Favorite?</h2>
<p>Leave a comment and let me know which tool you use.</p>]]>
      
   </content>
</entry>

<entry>
   <title>Google Chrome Beta for Mac and RSS</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2009/12/google-chrome-beta-for-mac-and.html" />
   <id>tag:www.rss4lib.com,2009://1.274</id>
   
   <published>2009-12-08T17:34:44Z</published>
   <updated>2010-01-10T19:04:44Z</updated>
   
   <summary>Another version of Google Chrome (version 4.0), on a new platform (now for Mac OS 10.5 and up) and the same old news about RSS: support isn&apos;t there in the browser. Both RSS 2.0 and Atom feeds display inline in...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="RSS Tools" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![CDATA[Another version of Google Chrome (version 4.0), on a new platform (now for Mac OS 10.5 and up) and the same old news about RSS:  support isn't there in the browser.  Both RSS 2.0 and Atom feeds display inline in the browser as a huge jumble of text. (Get <a href = "http://www.google.com/chrome/">Chrome for Mac</a>.)  

<div align = "center">
<a href = "http://www.rss4lib.com/images/20091208/google-chrome-4-rss.png" title = "Large version of this screen shot" alt = "Large version of this screen shot"><img src = "http://www.rss4lib.com/images/20091208/google-chrome-4-rss-sm.png" title = "Screen shot of Google Chrome 4's interpretation of an RSS feed" alt = "Screen Shot" width = "450" height = "209" border = "0" /></a><br>(Click image for full size version)</a>
</div>

I've railed about the lack of RSS support for either rational inline display or for live bookmarks since the earliest versions of Chrome <a href = "http://www.rss4lib.com/mt.cgi?__mode=view&_type=entry&id=266&blog_id=1">here</a> and <a href = "http://www.rss4lib.com/mt.cgi?__mode=view&_type=entry&id=231&blog_id=1">here</a>.

Otherwise, a quick test of the new Chrome beta for Mac shows that it's fast and efficient, as I've come to expect from Chrome's Windows betas.  I'm not sure I'll trade over from either Safari or Firefox, even when Chrome does get RSS support, but Chrome is coming along.  ]]>
      
   </content>
</entry>

<entry>
   <title>Spectives:  A Nice Tool that Abuses Intellectual Property</title>
   <link rel="alternate" type="text/html" href="http://www.rss4lib.com/2009/12/spectives-a-nice-tool-that-abu.html" />
   <id>tag:www.rss4lib.com,2009://1.273</id>
   
   <published>2009-12-01T15:42:03Z</published>
   <updated>2009-12-01T15:47:54Z</updated>
   
   <summary>I found a new tool (via a review at ReadWriteWeb) that offers a visual presentation of changing RSS feeds: Spectives, a &quot;search for visual news.&quot; Conceptually, it&apos;s quite interesting. Its use of intellectual property is unfortunate. Spectives is focused on...</summary>
   <author>
      <name>Ken Varnum</name>
      <uri>http://varnum.org/ken</uri>
   </author>
   
      <category term="Reviews" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="27" label="copyright" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="209" label="creative commons" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="270" label="fail" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="269" label="intellectual property" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="6" label="rss" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.rss4lib.com/">
      <![CDATA[I found a new tool (via a review at <a href = "http://www.readwriteweb.com/archives/visual_rss.php">ReadWriteWeb</a>) that offers a visual presentation of changing RSS feeds:  <a href = "http://www.spectives.com/">Spectives</a>, a "search for visual news."  Conceptually, it's quite interesting.  Its use of intellectual property is unfortunate.

Spectives is focused on visual content.  It ignores plain text entries on a blog, highlighting those posts with images.  I created a <a href = "http://www.spectives.com/rss">collection called RSS</a> and added this blog's feed to it; Spectives pulled in the most recent posts that included images:

<div align = "center" style = "margin-top: 1em; margin-bottom: 1em;">
  <img src = "http://www.rss4lib.com/images/20091201/rss-collection.png" width = "450" height = "232" title = "Spectives RSS Collection (screenshot)" alt = "Spectives RSS Collection (screenshot)" border = "0">
</div>

Interestingly, Spectives ignores <a href = "http://www.rss4lib.com/2009/10/presentation_at_internet_libra.html">posts with embedded video</a> (at least, the UStream feed embedded in a recent post on this blog).  

Spectives' <a href = "http://www.spectives.com/">front page</a> offers a one-minute tutorial  right up front -- probably because the point of the tool is a bit vague, if intriguing -- and then lists  popular and featured collections.  The "<a href = "http://www.spectives.com/nature-photography">Nature Photography</a>" collection (under featured) offers pictures from five photography feeds; the "<a href = "http://www.spectives.com/celebrities">Celebrities</a>" collection pulls in feeds from 15 gossip/tabloid sites.  

While the tool is interesting, its mechanism for getting users to the source content is highly annoying.  Each collection (and search) comes with its own RSS feed that includes <strong>all</strong> the items in the source's feed, not restricting it to images.  Clicking to the full text of an item in the RSS feed takes you to the original site, which makes sense.  However, Spectives puts a translucent toolbar across the bottom of the page with a link "Back to Spectives" and a link to share the post on Twitter -- with a Spectives URL built in.  Here's a sample of my previous post, in its entirety, with a Spectives URL and my Creative Commons license, along with the Spectives toolbar.

<div align = "center" style = "margin-top: 1em; margin-bottom: 1em;">
  <a href = "http://www.rss4lib.com/images/20091201/spectives-toolbar.png"><img src = "http://www.rss4lib.com/images/20091201/spectives-toolbar-sm.png" width = "450" height = "454" title = "Spectives Toolbar Superimposed on RSS4Lib (screenshot)" alt = "Spectives Toolbar Superimposed on RSS4Lib (screenshot)" border = "0"></a><br>(Click image for full size version)
</div>

At the moment, this is probably in technical compliance with the Creative Commons license -- however, as the "advertise" link on the bottom of every Spectives web page indicates, the site is clearly trying to monetize other peoples' content.  In my opinion, Spectives' reproduction of my entire web site separated from my URL crosses an ethical, if not legal, line.  I am not a fan.]]>
      
   </content>
</entry>

</feed>

