From 41f7627baee212ce4a4a75126109d9569c790dd0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 31 Mar 2015 12:12:21 -0400 Subject: todo --- doc/todo/podcatching_handling_updated_files.mdwn | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/todo/podcatching_handling_updated_files.mdwn diff --git a/doc/todo/podcatching_handling_updated_files.mdwn b/doc/todo/podcatching_handling_updated_files.mdwn new file mode 100644 index 000000000..998b084a6 --- /dev/null +++ b/doc/todo/podcatching_handling_updated_files.mdwn @@ -0,0 +1,17 @@ +Files in feeds can be updated, and if this update includes changing the +url, `importfeed` will treat this as a new file. This results in `foo.mp3` +having a `2_foo.mp3` added next to it. + +This seems to happen especially commonly with feeds using FeedBurner. +Saw several with same size, different checksum and url. + +To detect this, `importfeed` could store the item's guid in the metadata +of the key. Where it currently builds a `Map URLString Key` of all +known items, it could instead build a `Map (Either URlString GUID) Key`. + +This would at least prevent the duplication, when the feed has guids. + +It would be even nicer if the old file could be updated with the new +content. But, since files can be moved around, deleted, tagged, etc, +that only seems practical at all if the file is still in the directory +where `importfeed` created it. -- cgit v1.2.3