Some feeds use day-based stamps, i.e. new articles always show up at 00:00:00Z of the posting day, while others have a higher timestamp precision. This makes Feediverse lose posts from the former if the latter has posts.
The workaround is to mkdir ~/.feediverse instead of having a single config there, split them up per feed (initially, everything identical except the feeds top-level element will have only one entry each; they’ll differ in updated too once run) and then in the cronjob do /bin/mksh -c 'set -o pipefail; rv=0; for f in ~/.feediverse/*.cfg; do ~/Repos/Upstream/Feediverse/feediverse.py -v -c "$f" 2>&1 | logger -t "rss2mstdn:${f##*/}" || rv=1; done; (( rv == 0 )) || print E: rss2mstdn failed' (i.e. invoke it once per config file).
The code fix would be to move the timestamp insides the per-feeds elements.
Some feeds use day-based stamps, i.e. new articles always show up at
00:00:00Zof the posting day, while others have a higher timestamp precision. This makes Feediverse lose posts from the former if the latter has posts.The workaround is to
mkdir ~/.feediverseinstead of having a single config there, split them up per feed (initially, everything identical except thefeedstop-level element will have only one entry each; they’ll differ inupdatedtoo once run) and then in the cronjob do/bin/mksh -c 'set -o pipefail; rv=0; for f in ~/.feediverse/*.cfg; do ~/Repos/Upstream/Feediverse/feediverse.py -v -c "$f" 2>&1 | logger -t "rss2mstdn:${f##*/}" || rv=1; done; (( rv == 0 )) || print E: rss2mstdn failed'(i.e. invoke it once per config file).The code fix would be to move the timestamp insides the per-
feedselements.