no archival of already fetched articles/items?

[Simply-Jeff]

I don't really know if it's a bug, or just a feature not yet implemented but,

feedr only displays the items/articles that are present in the RSS feed during the latest refresh. Previously fetched articles disappear when they are no longer included in the feed's XML, even though Feedr has already seen and fetched them. ¹

This makes it difficult to use Feedr with feeds that expose only a small number of recent items, like The Verge feed, which only shows latest 10 articles, and a lot of articles are posted every day, so i can miss a lot of articles. ²

Example

Using The Verge RSS feed:
The feed exposes only a limited number of recent articles (just 10),

Initial fetch:

A B C D E F G H I J
Feedr shows:
A B C D E F G H I J
Later, after new articles are published, the feed contains:
D E F G H I J K L M
Feedr now shows:
D E F G H I J K L M
Articles A, B, and C disappear completely, despite having been fetched previously.

Expected Behavior:

Once an article has been fetched and stored locally, it should remain available in Feedr regardless of whether it still exists in the current RSS feed output.

Initial fetch:
A B C D E F G H I J
Later refresh:
D E F G H I J K L M
Expected local archive:
A B C D E F G H I J K L M

New articles should be shows as usual, while previously fetched articles ³ should remain accessible unless explicitly removed by the user or a configured retention policy like a month,

###Feature Request
Store and archive previously fetched feed entries locally, independent of whether they remain present in subsequent RSS feed responses.

Optionally, it would be great if retention settings could be added later which can be configure in feedr config to control how many articles are kept or for how long.

My setup

I use arch linux specifically Omarchy 3.8.0 distro, installed feedr through yay⁴, and using this config.toml

[general]
max_dashboard_items = 100
auto_refresh_interval = 0
refresh_enabled = false
refresh_rate_limit_delay = 2000

[network]
http_timeout = 15
user_agent = "Mozilla/5.0 (compatible; Feedr/1.0; +https://github.com/bahdotsh/feedr)"

[ui]
tick_rate = 100
error_display_timeout = 3000
theme = "dark"
compact_mode = "auto"

Context

I'm new to RSS, so i don't know much, and i been using feedr for the past 2 weeks, and added RSS feeds to all the news sites and blogs i follow, and replaced newsletters, out of all the terminal RSS readers feedr was the best one for me, and also (bulletty)[https://github.com/CrociDB/bulletty], it has a nice UI with a sidebar grouping feeds by folders, and a really nice clean article reader UI but its not maintained anymore, but bulletty does archive fetched articles.

I also don't make many github issues, so excuse my phrasing,

Footnotes

1. As said above I'm new to feeds so i don't really know how feeds work, but I'm pretty sure I'm right about this. ↩

2. I check for articles every 1-2 days and see latest + older articles up to a week older, and save em for later or bookmark before i started using RSS, and now just star the ones i like in feedr, and for high-volume news websites and feeds like the verge which likely posts more than 10 articles every day (i never counted), i lose more than 10 articles every time i check in feedr, and i cant browse/scroll through the older articles to find the ones i like, because feedr only shows the latest 10 articles, and almost all 10 articles are just posted in few hrs, so the verge's RSS feed is basically useless, an same for many other RSS feeds ↩

3. by previously fetched articles i mean all the articles which were loaded in feedr, read or even unread, like all the articles ever fetched after adding a feed. ↩

4. i tried using cargo installation method, but it wasn't showing the latest v0.8.0, maybe a bug or fault on my machine. ↩