summaryrefslogtreecommitdiff
path: root/FAQ.md
diff options
context:
space:
mode:
authorfox <[email protected]>2018-12-14 19:48:40 +0000
committerfox <[email protected]>2018-12-14 19:48:40 +0000
commit6945b1baa27d338b87c2068543996c0699c4d374 (patch)
treec370133db2a19dd742eea67e24e8acbe5964f92a /FAQ.md
parent343426fd0c50bd73f2bd3fb54dcdbf307959d141 (diff)
Update page 'FAQ'
Diffstat (limited to 'FAQ.md')
-rw-r--r--FAQ.md17
1 files changed, 7 insertions, 10 deletions
diff --git a/FAQ.md b/FAQ.md
index 8bf4c73..11c1d89 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -52,16 +52,13 @@ Usually, it’s <code>lock/update\_daemon.lock</code>. You can also remove
In short, you may and will see articles with date older than the cutoff
for purging. Here’s why:
-- Starred articles are not purged.
-- Purging is done based on article import date internal to tt-rss which
-could be different from the date specified in the original feed (e.g.
-article has date 01-01-1970, but it was imported today).
-- When tt-rss sees articles still exist in the feed it bumps the import
-date because otherwise the articles will get purged and reimported
-periodically causing annoyingly reappearing duplicates. This is mostly
-relevant for rarely updated feeds.
-- Purging is performed when the feed is updated hence disabled updates
-= no purging.
+- starred articles are not purged;
+- purging is done based on article import date internal to tt-rss, which
+could be different from the timestamp specified by the feed (i.e.
+article says it was published on 01-01-1970 but it was imported today);
+- tt-rss bumps import date every time article is encountered in the feed, otherwise
+it will get purged and imported again on every feed update causing constantly reappearing duplicates;
+- purging is performed when the feed is updated hence disabled updates = no purging;
Please see these forum threads for more information: