We are almost feature complete for the next release of RSS Bandit
and it is about time we started getting some feedback from our users. You can obtain the installer from
. The major new features and bug fixes are listed below. There will be a comprehensive list of bug fixes and new features in the announcement for the final release.
UPDATE: There was an issue when upgrading from v22.214.171.124 to the Jubilee beta which is now fixed.
New Features in Progress
Major Bug Fixes
- Podcast inbox - This will be the similar to the podcast inbox of applications such as Doppler Radio or Juice Receiver which will allow users to keep track of pending and downloaded podcasts.
- Revamping the search feature - We're moving the implementation of feed search to Lucene.Net from our custom feed search implementation which should make it faster and provide richer search options
Major Bug Fixes in Progress
- Feed items appear in wrong feed folders - we now apply a set of heuristics to prevent this problem from surfacing ever again. I'm pretty sure this problem is due to bugs in HTTP Pipelining. However it is unclear whether the bugs are in the .NET Frameworks HTTP library, proxy servers that RSS Bandit is passing through or the Web servers that the application is fetching feeds from.
- Relative Links in Atom 1.0 feeds appear incorrectly - now that this is fixed the links Tim Bray and Sam Ruby's feeds now work correctly
- Atom feeds from the Blogger beta site show no posts when viewed in RSS Bandit - this was just a dumb bug on my part.
- Sites with malformed cookies cause feeds not to be fetched - Specifically, fetching cookies from sites such as Windows Live Spaces results in the "An error has occurred when parsing Cookie header". Now we just ignore the error and soldier on.
RSS Bandit needs administrator privileges on first run - the fix for this was so esoteric it boggles my mind.
- RSS Bandit stops downloading feeds after a while - This was actually two bugs. The first was that the application stopped automatically downloading feeds if any of them timed out while being fetched. The other was that feeds with whitespace in the URLs were not being updated.