1 * Since every item that is fetched (can) increase the feed
2 date when that feed is flushed, a subsequent run will only
3 write and thus overwrite the item if it has a newer
5 However, if one item occurrs several times in the same feed,
6 only the most recent one should be written.
8 IOW: date conflicts can only happen within a single run.
9 but we have no possibility to check items of a single
10 run. so check all that are stored.
12 Thus, only (over)write items if date > old date.
14 tests: item_duplicates: asc/desc feeds, check whether
15 stored item has contents/date/etc of most recent one.
16 * Make directories/items read-only.
17 * no date -> current date. write all items with date >=
19 * check whether dates are handled properly (timezones!)
20 * fix remaining bugs (see README)
21 * support lastBuildDate and pubDate for channels
22 * replace assertions by proper error handling
23 * clean state after a tag level is left, so we can pipe
24 multiple streams, one after another, into one instance.