gPodder Bug Tracker – Bug 188
Add option to mark only the most recent episode as new after an update
Last modified: 2012-10-13 16:16:16 BST
If subscribed to a podcast that issues many episodes per day (such as Sky News headlines - video podcast http://skyscape.sky.com/skynewsradio/NEWS/dailyheads.xml), then typically you only want to download the latest episode, which supersedes all the older ones.
Please consider adding a "latest episode only" tick box to the dialogue box that offers properties for each subscription.
Then when Updating/checking for new episodes, only the latest should be shown for those subscriptions for which this tick box is selected. Equally when run from the command line (--maemo --run) only the latest episodes should be downloaded.
This will also allow Maemo users to use cron to grab the latest podcasts overnight.
Although I'm keeping this bug open, as it might be implemented with the new database, in case anyone wants to volunteer.
*** Bug 692 has been marked as a duplicate of this bug. ***
Ok, this might not be totally a dupe of bug 98, but it results in the same effect - you have a per-podcast setting that allows you to get rid of non-interesting podcast episodes (e.g. daily news podcast that you don't want to catch up with).
Feel free to add comments and wishes to the comments of bug 98. Thanks!
*** This bug has been marked as a duplicate of bug 98 ***
(In reply to comment #3)
> Ok, this might not be totally a dupe of bug 98, but it results in the same
> effect - you have a per-podcast setting that allows you to get rid of
> non-interesting podcast episodes (e.g. daily news podcast that you don't want
> to catch up with).
> Feel free to add comments and wishes to the comments of bug 98. Thanks!
> *** This bug has been marked as a duplicate of bug 98 ***
Just to add an extra bit from this duplicate bug:
I think an option to just download the 'x' number of newest podcasts for a feed would give more flexibility. See the above bug for more details of this implementation.
With respect I disagree that this is a duplicate of CRs 98 and 692. The feature I originally suggested only downloads the latest podcast which make sense when subscribed to news video feeds which are released four times a day. Instead of downloading unwanted episodes and then creating logic to manage their deletion, only the required episodes are downloaded in the first place.
This combined with a simple (easy for me to say, I know) update scheduler (there's a really simple one implemented in FeedCircuit which allows the user to request the program to update feeds once per day, for example) would mean that our podcasts can be automagically updated daily at say 5am, the IT can be grabbed and taken to breakfast and the latest news watched, without the usual bleary-eyed finger work and waiting for downloads. Great!
But hey, you're the boss, so if you close this one again and insist it really is a duplicate, then I'll keep my mouth shut and be grateful for what I've got :-)
Paul: Thanks for your feedback. I've changed the title accordingly. So, simply having an option that will only mark the latest episode as new when doing an update is okay? This way, when there have been e.g. 4 episodes released since the last feed update, only the most recent one is marked as new?
This way, if you update all four days, you will get a maximum of one episode every four days, and if you update twice per day, you will get a maximum of two episodes per day.
Removing assignment - this one is up for grabs, if anyone wants to implement it :)
Implemented in Git: http://gpodder.org/commit/236ee1f6
For now, only the Gtk UI has an interface to change the download strategy. The setting is per-podcast, and if set to "Only keep latest", only the most recent episode will be marked as new, and on startup, all episodes except for one will be deleted (if they don't have their "keep" flag set).
*** Bug 774 has been marked as a duplicate of this bug. ***