Closed CosmosAtlas closed 2 years ago
Thanks for your report. Here is a workaround for it, if works, just close the issue:
(setq elfeed-protocol-fever-update-unread-only t)
Can confirm the work around works for me. Thank you for the quick response!
eaf1329ff221098eb6d4709245010d070c89b173
(https://hub.docker.com/r/linuxserver/freshrss)
(docker image and tag)elfeed-protocol-xxx-feeds
empty:no
elfeed-log
NA
error backtrace
NA
Behavior
When currently using a fever feed from FreshRss,
update
won't show new items.Root cause
Upon inspection,
elfeed-protocol-fever-update
basically just fetches 50 new entries based on thelast-entry-id
. However, FreshRss generates its id by Unix time (some irrelevant discussion here, but covers how the id is implemented).So it means that, realistically, the update function will never generate new entry ids (given it only generates ids within 50/1000 of a second...)
Suggested fix
I'm not familiar with elisp enough to fix this personally, but below are some highlevel ideas.
init
Side Note
With
unread_item_ids
from fever, it would be possible to match with local database, so that read status can be synced the other way around as requested by #38 . Meaning that if a current unread item doesn't exists in fever's newunread_item_ids
it can be marked as read.