Death to the ‘feed:’ URI Scheme - by Wesley Moore

Death to the ‘feed:’ URI Scheme

Published on

Can people please stop using the ‘feed:’ URI scheme for links to feeds on web pages. Its annoying and unnecessary.

From what I can tell this URI scheme was proposed around Dec 2003 as an unofficial pre-draft RFC. The reasoning behind the proposal was:

…to provide a straightforward way for end users to subscribe to the data feed for a particular online resource while browsing the World Wide Web. The expectation is that clicking on a hyperlink that points at a “feed” URI will cause the Web browser to invoke the specified handler for the “feed” URI scheme which SHOULD provide the user with information about the data feed as well as the possess the ability to subscribe to the feed.

Fast forward to 2008 and all the major browsers have support for discovery of feeds specified by the link tag and a user interface to access them. Additionally they are able to auto-detect a feed when specified with the normal http URI scheme. With the built in support the browser is able to launch the appropriate feed reader on the system, be it within the browser or an external application. Thus removing the need for the URI to be specified with the ‘feed:’ scheme.

It seems use of the scheme really took off around the release of Safari 2, which included RSS support. When viewing a feed in Safari it presents the URI using the ‘feed:’ scheme, thus making its use highly visible.

I understand that using the scheme makes it easy at an operating system level to associate a particular application with the scheme but it should be entirely internal an invisible to the user. The reasons its use irks me is when adding a feed to Google Reader its necessary to copy and paste the link and then remove the ‘feed:’ at the start. Additionally Firefox removes the colon from http, meaning that has to be replaced too. Okay so I’m lazy but all the hassle can be avoided by simply linking to the feed with the normal ‘http:’ scheme.

As an example I’ll pick on the MildMannered Industries Blog solely because its the first example I could find. The link on the page1 (at the top) is feed://, which when copied via Copy Link Location in Firefox becomes feed://http//

The other issue I have stems from the terrible DNS or proxy (not sure which is to blame) setup here at work. When a request is made for a hostname or scheme that doesn’t exist the browser hangs for about 2 minutes before returning an error generated by the proxy. This happens in all browsers and means that if I click in a feed: link my browser hangs for 2 minutes, which is quite frustrating.

So my request to the wider Internet community: Please stop using ‘feed:’.

  1. The related link embedded in the <head> section is correct (I.e. without ‘feed:’)

Comment icon Stay in touch!

Follow me on Twitter or Mastodon, subscribe to the feed, or send me an email.