that’s not true. this particular behavior has been implemented several years ago:
Author: Andrew Dolgov <[email protected]>
Date: Sun Jul 12 01:29:36 2015 +0300
queryFeedHeadlines: move to array-based arguments, optionally check if first element changed when paginating
you just got lucky with new articles being added or didn’t notice it. i remember posting about the reason behind this but since i can’t find that post either (duh!) i guess there’s no harm in repeating it.
tt-rss does pagination in terms of SQL LIMIT/OFFSET. when you scroll down, it calculates how many articles are currently loaded and requests a bunch more starting from X.
this approach has several problems but arguably the most obvious one was what happens when new articles have been added to current view perspective. frontend keeps counting articles showed when X was the first one, but backend counts from Y, so some articles get silently skipped.
forcing pagination to stop in this situation (i.e. making user reload the feed) was the least painful (i.e. easiest to implement) solution to this.
a proper way to solve this (and several other minor issues related to race conditions) would be reworking pagination entirely somehow but i have no idea how to do that and don’t really want to bother anyway since current approach works, most of the time.