blog.yaml

---
title: Superfeedr Blog
updated: 2009-06-23T10:05:53-07:00
feed_id: http://blog.superfeedr.com/
categories: 
    - term: Superfeedr
    - term: Feed Parsing
    - term: Songs from Finland
authors: 
    - name: Julien Genestoux
      email: julien@superfeedr.com
      uri: "http://twitter.com/julien51"
links:
    - href: http://blog.superfeedr.com/atom.xml
      rel: self
      title: 
      mime_type:
    - href: http://blog.superfeedr.com/
      rel: 
      title: 
      mime_type:
entries: 
    - id: blog.superfeedr.com:/feeeds/gospel/atom-or-rss-not-both
      title: RSS or Atom, not both!
      summary: ""
      published: 2009-06-23T00:00:00-07:00
      content: "<p><a href=\"http://en.wikipedia.org/wiki/RSS_(file_format\"><span class=\"caps\">RSS</span></a>) and <a href=\"http://www.atomenabled.org/developers/syndication/atom-format-spec.php\"><span class=\"caps\">ATOM</span></a> have very similar (if not identical) purposes. I don&#8217;t know any feed consumer that consumes only one type, yet, a lot of services are still providing both.</p>\n\n\n\t<p>Publishing both is useless, because it&#8217;s likely that services will end up polling both of them, to identify new content. It is very hard for them to be 100% sure that they actually contain (and will always contain) the same information. You know that <a href=\"http://blog.superfeedr.com/gospel/something-stupid/\">polling your blog or service is stupid</a>... don&#8217;t make twice as stupid.</p>\n\n\n\t<p>Yet, if you publish both <span class=\"caps\">ATOM</span> and <span class=\"caps\">RSS</span>, make our lives easier in two steps :</p>\n\n\n\t<ul>\n\t<li>Remove the extra <code>&lt;link href=\"...\"&gt;</code>, by keeping just Atom or <span class=\"caps\">RSS</span></li>\n\t</ul>\n\n\n\t<ul>\n\t<li>Add a 301 redirection from one to another, so that you&#8217;re not messing with your existing pollers (as they should probably follow redirections and be able to parse either format) : with Apache it&#8217;s as easy as: <code>RedirectMatch 301 /statuses/user_timeline/(.*)\\.rss http://twitter.com/statuses/user_timeline/$1.atom</code></li>\n\t</ul>\n\n\n\t<p>No more excuse for not doing it! Please note that I am not discussing whether you should keep <span class=\"caps\">ATOM</span> or <span class=\"caps\">RSS</span>. I&#8217;d go for Atom, but that&#8217;s a not the case for everybody.</p>"
      categories: 
          - term: Gospel
      links:
          - href: http://blog.superfeedr.com/feeeds/gospel/atom-or-rss-not-both
            rel: 
            title: 
            mime_type: