I love the idea, but the implementation is abysmal.
Nearly three-fourths of the time I click RSS Menu, it beachballs because it's busy doing *something*. I only have about 30 RSS feeds, all set on the default half-hour update interval. I clicked the menu a bit ago, and the menu didn't drop down for 15 MINUTES. Then when I made one selection, it closed and beachballed again for 2 MINUTES.
To the developer, PLEASE learn what multithreading is and how to do it. Semaphores and locks and such are NOT hard. It is relatively simple to fire off a new thread that connects to the server, collects the data, and then feeds it into the GUI (if the GUI is being used at the time, it defers until the GUI thread is ready).
The GUI should exist in the main thread and simply spawn a new thread for each feed that's updating. That way the GUI is *always* responsive, and your updates will happen a LOT faster. Instead of 29 feed updates being stalled because one server missed a packet or is timing out, everything else just works. While normally opening a couple dozen network connections is a no-no in TCP, since these are all to different servers it's ENCOURAGED.