umputun
commented
2 years ago this was done based on two conditions:
- pubdate is prior to the first episode in the final feed
- number of episodes in the feed reach maximum
if both conditions are met, the episode won't be downloaded but will be set as processed. The reason for the second check is to prevent skipping episodes for the initial run. Worked fine as I have added the feed above and delivered only a couple of the recent episodes (the feed has some very old entries)
Adding a new yt channel into the system causes downloading and publishing multiple episodes into the final feed and sending multiple tg messages. This can be troublesome in case the system is already configured and run for some time. For example, the request to add this feed will bring all the episodes inside the
max_per_channel, and some of them like a year old.Those episodes will be out-of-order and will be added to the feed in the middle and to the end, but this behavior is strange and sort of confusing for the users and also unusual for the podcast clients.
I don't see a good solution here yet. Limiting any new feed and allowing the last episode only is not the best solution in the case of initial setup. Not allowing out-of-order episodes in general, is also not good because it can happen to the "normal" episodes in the existing feeds in some situations. Logically it makes sense to ignore all the episodes prior to the oldest ones in the feed, but this won't work properly for the initial setup either.