App version: 1.8.3 (installed from F-Droid)
Problem you may be having, or feature you want:
Several times, I have experienced the problem that some episode was added to a podcast feed which did not belong there. The authors realised that fact not long after and removed the episode entirely from the XML. The episode still remains in the feed in AntennaPod, which is a good standard behavior. But I want to have the option to entirely get rid of such erroneous episodes and delete them from the feed.
Suggested solution:
Such a feature could be named "Sync list with XML": It removes all episodes from the database list which no longer have a corresponding episode in the XML for this feed.
It should not be difficult to find these episodes, as the connection between the list and the XML already exists to keep track of new episodes. Titles or timestamps get already updated in the list. Therefore, the vital parts of this feature are already present.
This is a very useful feature. I have several feeds with one or more episodes per day. So my list is becoming very long. The problem is, old episodes stay in the list, although they are no longer available.
This feature should not be a button nor a checkbox to be invoked manually but should happen automatically on every sync. Where's the sense in listing expired episodes? The only exception should be that already downloaded episodes should stay in the list until deleted, because I can still listen to them.
One thing is worth noting: the deletion of an episode in the feed xml does not necessarily mean that the episode is _"expired"_ or _"invalid"._ Some podcast feeds only provide the latest 10 or 20 episodes at the time of fetching (as examples), but the previous episodes are playable.
Therefore, when the "Sync list with XML" function is introduced, it should be possible to configure the "Yes", "No" or "Default" options for each podcast source.
This would be a great feature
Most helpful comment
One thing is worth noting: the deletion of an episode in the feed xml does not necessarily mean that the episode is _"expired"_ or _"invalid"._ Some podcast feeds only provide the latest 10 or 20 episodes at the time of fetching (as examples), but the previous episodes are playable.
Therefore, when the "Sync list with XML" function is introduced, it should be possible to configure the "Yes", "No" or "Default" options for each podcast source.