Moving servers doesn’t neccessarily mean moving feeds, but I did so anyway, mainly to get rid of the .xml extensions. If your newsreader software is anywhere near sane, you shouldn’t really have noticed, since permanent redirects for the old feed URIs are in place.
Here are the new addresses – with direct subscription links for “Bloglines”:http://www.bloglines.com/ users:
h3. Excerpts only feeds
* RSS 1.0 excerpts – Used to reside at http://www.virtuelvis.com/feeds/index.rdf
* RSS 2.0 excerpts – Used to reside at http://www.virtuelvis.com/feeds/index.xml
* Subscribe directly to the excerpt feed in Bloglines
h3. Full-text feeds
* RSS 2.0 full-text – Used to reside at http://www.virtuelvis.com/feeds/rss20full.xml
* Atom 0.3 full-text – Used to reside at http://www.virtuelvis.com/feeds/atom.xml
* Subscribe to the “full-text feed in Bloglines”:http://www.bloglines.com/sub?url=http://virtuelvis.com/feeds/atom
h3. Bookmarks sideblog feeds
* RSS 2.0 bookmarks – Used to reside at http://www.virtuelvis.com/feeds/onroll.xml
* Atom 0.3 bookmarks – used to reside at http://www.virtuelvis.com/feeds/atomroll.xml
* Subscribe to the “bookmarks sideblog in Bloglines”:http://www.bloglines.com/sub?url=http://virtuelvis.com/feeds/bmatom
h3. Comments feed
* RSS 2.0 comment feed – Used to reside at http://www.virtuelvis.com/feeds/comments.xml
* Subscribe to the comments feed in Bloglines
h3. Which feed?
If your aggregator supports “Atom”:http://www.atomenabled.org/ you are *strongly* encouraged to use these. The RSS 1.0 and 2.0 feeds are legacy feeds, and new, planned feed features, such as related and via, *will only be added to the Atom feeds.*
h3. Future: Content negotiation
As you can see, I have a plethora of feeds, and I may add more and I plan on consolidating the public feed addresses. This means that, at some point in the future, the feeds will be consolidated into just a few URIs. What I have in mind is this:
* /feeds/comments (Yes, this has already moved for the last time, really)
My intention is using “Apache’s content negotiation features”:http://httpd.apache.org/docs/content-negotiation.html to serve the proper feed to the client. Which means that if your aggregator says it prefers
application/atom+xml, it will get Atom feeds. If it says it prefers
application/rss+xml, it will get RSS, and so on.
If you are the author of an aggregator, you’d better start sending appropriate
Accept: headers with your HTTP requests, unless you want to force your customers to get the deprecated RSS 2.0 documents.