AutoDiscoveryHallOfShame

This is a table of popular RSS feed sources and their autodiscovery support. The hope is that services which do not support autodiscovery or which support it incorrectly can be shamed into supporting it, while those that are supporting it can be celebrated and revered as gods. Autodiscovery is very easy for these services to support, so let's do it folks.

1. Blosxom hangs its files off of the CGI script. For example, http://www.bitbucketheaven.com/cgi-bin/blosxom.cgi has its RSS file at http://www.bitbucketheaven.com/cgi-bin/blosxom.cgi/index.rss ↩
2. Flickr supports the following kinds of feeds, some of which support autodiscovery and some which don't: Feeds linked to a single user - supports autodiscovery, Feeds linked to an aggregation of all of a user's contacts - does not support autodiscovery, Feeds linked to a Flickr Tag - does not support autodiscovery, Feeds linked to a Flickr Group - supports autodiscovery, Feeds linked to a Flickr Group's Comments - supports autodiscovery ↩
3. Since Flickr supports many different kinds of feeds, their location is different based on their type. For the feeds linked to a single user, if you were at the user page http://www.flickr.com/photos/35468147429@N01/ then its Atom feed would be at http://www.flickr.com/services/feeds/photos_public.gne?id=35468147429@N01&format=atom_03 and its RSS feed would be at http://www.flickr.com/services/feeds/photos_public.gne?id=35468147429@N01&format=rss_200. For the feeds linked to an aggregation of all of a user's contacts, if you were at the page http://flickr.com/photos/friends/ then all of your contact's feeds would be aggregated in http://flickr.com/services/feeds/photos_friends.gne?user_id=36521982213@N01&format=atom_03&friends=0&display_all=1 for the Atom feed and http://flickr.com/services/feeds/photos_friends.gne?user_id=36521982213@N01&format=rss_200&friends=0&display_all=1 for the RSS feed; notice that user_id must be equal to the currently signed in user's ID and that you must have a cookie set for this user, i.e. be signed in. The user_id can be taken from the cookie or by scraping the page for the JavaScript variable global_nsid. For feeds linked to a Flickr Tag, if you were at http://flickr.com/photos/tags/amsterdam/ then the Atom feed would be at http://flickr.com/services/feeds/photos_public.gne?tags=amsterdam&format=atom_03 and the RSS feed would be at http://flickr.com/services/feeds/photos_public.gne?tags=amsterdam&format=rss_200. For feeds linked to a Flickr Group, if you were at http://flickr.com/groups/whedonesque/ then the Atom feed would be at http://flickr.com/groups_feed.gne?id=35468153735@N01&format=atom_03 and the RSS feed would be at http://flickr.com/groups_feed.gne?id=35468153735@N01&format=rss_200. For feeds linked to a Flickr Group's comments if you were at http://flickr.com/groups_topic.gne?id=6006, which is a single comment thread in a Flickr Group, then the Atom feed would be at http://flickr.com/groups_feed.gne?id=35468153735@N01&format=atom_03 and the RSS feed would be at http://flickr.com/groups_feed.gne?id=35468153735@N01&format=rss_200 ↩
4. By default, no feeds are supported for GreyMatter. However, optional plugins are available that can produce feeds ↩
5. They have autodiscover links in their template, but they point to the wrong location! ↩
6. Xanga builds its link to an RSS feed from the user's ID. For example, if you are at http://www.xanga.com/home.aspx?user=wdfphillz, where the user is wdfphillz, then the RSS feed would be at http://www.xanga.com/rss.aspx?user=wdfphillz ↩
7. Yahoo Groups rewrites the domain name from groups.yahoo.com to rss.groups.yahoo.com, keeps the rest of the existing path, and then adds /rss to the end. For example, if you are at http://groups.yahoo.com/group/talkinaboutarchitecture/ then the RSS feed is at http://rss.groups.yahoo.com/group/talkinaboutarchitecture/rss ↩