RSSOwl 2.2 released

This new version provides an easy way to unsubscribe from Google Reader as Google decided to stop this service end of June. Please find more details in this FAQ entry.
In addition, you can now export a feed as CSV file (File | Save as...) and among some bugfixes, some new share providers where added (Google Plus, Pocket).
I would like to send out a big thank you for the donations that where submitted over the past weeks!

Updated instructions how to build RSSOwl

It was about time to provide up to date instructions how to build RSSOwl using Eclipse. Head over to rssowl-target and find the instructions in the summary. We are encouraging other developers to provide pull requests on our GitHub project page!

Google Reader is powering down...

You have likely read by now that Google is planning to shutdown their Google Reader service by summer. If you love synchronization (I do!), consider to sign this petition to keep it alive. Please stay tuned for upcoming announcements how RSSOwl will support synchronization in the future and how you can import your subscriptions safely. Please keep in mind that Google Reader will still continue to work for some months.

RSSOwl 2.1.6 is available

This bugfix release resolves an issue when synchronizing articles with attachments with Google Reader.

Find more Feeds should work again

The service to find feeds based on keywords should work again now, apologies for the down time. You can search for feeds by keyword from the tools menu (Find more Feeds).

RSSOwl on Windows 8

As you might have heard, Windows 8 is around the corner. I went ahead and did a test how RSSOwl works on this new OS. As you can see from the screenshot below, thanks to the native UI library RSSOwl is using, the app adapts to the new theme easily:

RSSOwl 2.1.4 is out

This bugfix release resolves an issue when synchronizing articles to Google Reader and receiving an error "Bad Request (400)". This could happen when RSSOwl synchronized several hundred articles in one chunk to Google. As such this issue was only showing up for power users. If you have never seen this problem, you can stay on 2.1.2.