https://bugs.gpodder.org/show_bug.cgi?id=1107

--- Comment #6 from sideral <[email protected]> 2010-09-02 13:33:35 BST ---
(In reply to comment #5)
> (In reply to comment #4)
> > I do understand this concern.  That's why I proposed a
> > user-configurable timeout value (defaulting to a period such as 30
> > days) after which old episodes would be deleted.
>
> I would not want to add this as a configurable option. Maybe a field
> in the database that marks the time when the episode disappeared

This should be reset when the episode reappears.  A more useful property could
be "time when the episode was last seen", to be updated every time the episode
is found in the feed.

> and a clean-up of old episodes that have not been seen for 10 days
> would work just as well without the added configuration option (which
> adds another attack vector for misconfiguration bugs). How long do
> episodes disappear from a feed in your experience?

They disappear for hours or days, not weeks.  Under the assumption that users
update their feeds at least once a week, a fixed period of 10 days would be
fine.

> How long do other feed readers keep old episodes around?

KDE's Akregator makes expiry user configurable: limit number of articles
(defaults to 1000 articles) or limit age of articles (defaults to 60 days);
both limits can be defined globally or per feed.

Web-based feed readers (Bloglines and Google Reader) keep episodes around
basically forever.

> > Also, you forgot to address my other concern (from comment #1):
> > Another side effect of gPodder forgetting about disappearing items
> > too soon is that such items will not be deleted from an MP3 player
> > during synchronization should they happen to still be on the MP3
> > player.
>
> That's a separate issue. gPodder could very well check for
> extrasneous, unknown files on the MP3 player (or at least in the
> per-podcast folders on the MP3 player) and show them and offer to
> delete them as well. Having the episode hidden in the database does
> not fix this problem - it only makes it happen slightly less often.

Agreed.

-- 
Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
gPodder-Bugs mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-bugs

Reply via email to