Differences between v1.1.0.16 and v1.1.0.29 below.

• Sent Items folder created for comments posted from RSS Bandit via the CommentAPI.
  
  Joe Gregorio has a list of CommentAPI implementations which lists the sites that can be posted to from RSS Bandit.
  
  
• Added support for Chris Sells's commentRss proposal. If a website supports this feature then comments to a particular entry are shown beneath the item as threaded responses in much the same manner as email. Here is a screenshot showing a post on Chris Sells's blog and the comments displayed underneath the post. Other sites that support the wfw:commentRss element include Sam Ruby's blog, Phil Ringnalda's blog, and all the blogs at Weblogs @ ASP.NET.
  
  This should satisfy Shawn Morrissey's feature request from yesterday.
  
  
• A number of bugs related to connecting to the Web via a proxy server have been fixed.
  
  
• Can now navigate the homepage of a feed or check its Technorati link cosmos from the feed menu in the tree view.
  
  
• Offline mode which is great if you use RSS Bandit from a laptop like I do.
  
  
• Added support for an extensive amount of keyboard shortcuts.
  
  
• Added the ability to configure how long items are stored by RSS Bandit independent on whether they are still in the feed or not. This means that for news sites like Slashdot or BBC that refresh the stories in their feeds on a daily basis one can specify that RSS Bandit should keep the items around for as long as desired. This can be configured both per feed and for all feeds.
  
  
• Added option to configure which search engines are used when queries are entered into the search toolbar
  
  
• Problems with text on dialog boxes being hard to read on systems with Big Fonts (120 dpi) should be fixed.

With this release I'll be scaling back on working on RSS Bandit for the next month or two except for bug fixes. My next Extreme XML column will be about some of the inner workings of RSS Bandit and after that I'll spend the next month or two focusing on blogging software. The members of the BlogX GDN Workspace have spoken and I'll be working on dasBlog in the coming weeks. The main question is how to transfer the focus of the 300 or so members of the GDN Workspace (granted only about a dozen are active in any significant way) to working on dasBlog without a repeat of the current BlogX situation where the initial poject owner releases a promising code drop then loses interest. Ahhh, project management fun. :)