The flood protection, was more badly broken than expected. But now it works as you’d expect.
The installer also didn’t properly reflect your selection about maintaining the ownership of protocols. Also fixed.
For those of you who don’t realize how huge this flood protection is, I’d like to tell my own tale of woes. Approxamitely once a month, one or more of my 50+ subscribed podcasts decides that all its content is new, and according to the rules PodBreeze is to download it all.
So far there’ve been one thing holding back these floods, namely the per feed property <b>Only download episodes whose published date/time is later than the last one downloaded</b>. I haven’t activated this for any of my feeds yet, since it might make me miss podcast episodes – simply a faulty time on the publishers machine could cause this.
With the new flood protection feature, no special logic is needed – no need to check for published timestamps anymore. Just activate the flood protection, and decide for yourself what to do with the “new” episodes.
This will save your bacon over and over 🙂 There’s nothing worse than discovering that PodBreeze has downloaded all episodes of a video podcast all over again, dragging all over activity on the (shared) broadband to a halt, and possibly even making you go above the download limit placed on you by your ISP.
I’d gotten reports of, and spotted myself, that PodBreeze created a temporary file in its home directory. I’m currently investigating why this is happening, but in the meantime the temp file(s) are deleted automatically at shutdown.
I’ve also modified the program to avoid problems with date/time formats reported by a user. All settings regarding time are now stored as integers, which in one case is more readable and in one less so.
The help file has been changed, splitting the settings page into one page per tab in the program.
- Normal version for installation on your hard disk
- USB version for installation on your USB MP3 player
- Update version for existing users