RSS: From Format to Plumbing to Nothing in 13 Years

Is RSS being forced out by technology companies that want more control over all aspects of the user interaction? That’s the contention of an article recently published in the Sydney Morning Herald (see “Apple Joins the War on RSS,” by Adam Turner, 1 August 2012, via the RSS Specifications blog). Turner points out how RSS is no longer a part of either Apple Mail or Apple Safari in the latest version of its operating system, Mountain Lion. He goes on to show how major Internet sites like Facebook and Twitter have been removing the in-built RSS feeds from their pages, making it harder to subscribe to information streams without subscribing to the service itself. Google Plus, Turner notes, never had RSS to start with.

When RSS started, it was a tool for individuals to use to track web sites and people they are interested in. In the early 2000s, sites tried to get you, the reader, to subscribe to their RSS feeds as a way to retain readership. By the late 2000s and first view years of the teens, RSS was less a selling point, but a fundamental part of any web site. It had evolved into an open, universal data exchange standard for web sites. Applications could easily sniff it out (through the headers, read only by applications but not seen by human users who didn’t view a page’s source, of web pages). Perhaps this change from shiny fixture on the kitchen counter to plumbing behind the wall was not a sign of its fundamental importance, as I posited previously.

As Turner points out, the HTML code to indicate the presence of an RSS feed is increasingly rarely even seen in a web page’s header. For example, look at the source of the RSS4Lib Twitter profile page or the RSS4Lib Facebook Page. No relative link in the document header to let an application know that there’s an RSS feed present.

While I regret the change in philosophy that has led popular social networking sites from making it harder for the content on the site to be used in other venues, I suppose I understand it. I imagine the Twitters and Facebooks of the world are thinking something along the lines of this: “If we can prevent that scourge of openness, RSS, from liberating individual user’s content, we can sell more ads or control more interactions.” In a commercial sense, that’s plausible, even if not wholly reflecting reality.

At the same time, if Apple no longer indicates that RSS feeds exist in pages that you visit in Safari (and if other browsers follow suit), that’s will drive a fundamental change in the way individuals discovery and access Internet content. Sure, discovery will happen, but it will happen through your social networks, mediated by major services. And it will happen in short-form: a few characters in a tweet, or a snippet on Facebook. It won’t happen in long-form, in a context that you (the consumer) manage. If information wants to be free, as the saying goes, it needs a path to follow. RSS seemed like it was that path. What’s next?

Getting in Their Face[book]s

Facebook Librarian is an extremely useful application to bring Facebook users (for many of us academic librarians, that translates to the overwhelming majority of our user population) and librarians together. Facebook, as we all know, is a social networking site. Its audience is largely college and post-college people, although there are both younger and older members. Heck, I’m one of those older Facebook users having graduated from school several years before the Web was born.
Facebook Librarian is an application that any Facebook member can add to their profile. Once added, it provides links to a range of resources, including WorldCat, Google Scholar, Internet Archive, Amazon, and so on. But that’s not the really interesting thing — this is: there’s an “Ask a Librarian” link in the application that will either link to a librarian at the user’s school (if one has signed up through Facebook Librarian) or elsewhere (another school’s librarian who volunteered to take questions from all comers). Plus, if a library creates a very simple HTML page and provides the URL of that page to Facebook Librarian, that “widget” is displayed within the application.
This works because college-aged Facebook members are generally associated with an educational institution and Facebook makes that association available to application developers. So if anyone at the University of Michigan with a Facebook account goes to the Facebook Librarian application, they will be able to “Ask a Librarian” (me, in this case) or search our library catalog, journals collection, database collection, or web site from within Facebook. Any library can both register to be a contact for a particular school and/or provide a library widget.
This is a very useful and truly wonderful example of putting the library where the users are.
Kudos to Brad Czerniak, who developed this application, a student at the Library and Information Science program at Wayne State University. You can read more about Facebook Librarian on his blog: Hawidu. Or, to try it yourself, go to http://apps.facebook.com/fblibrarian and click “Add to my profile.”