todo
This commit is contained in:
parent
0a6933771d
commit
86b66758c2
1 changed files with 17 additions and 0 deletions
17
doc/todo/podcatching_handling_updated_files.mdwn
Normal file
17
doc/todo/podcatching_handling_updated_files.mdwn
Normal file
|
@ -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.
|
Loading…
Add table
Reference in a new issue