The item list is fetched 50 at a time, and only the list's Load more button asked for more. A swipe or j stops at the last item loaded, so after 50 items the reader bounced on every swipe until a reload brought a fresh page of unread ones. Turning to within five of the end now fetches the next page behind. Its offset counts what is still unread on the Unread tab: the items read here have left the server's unread list, and Load more's flat 50 a page skipped as many unread items as had been read. A refresh (a return from the background, a live update) always asks for the first page, as the kept list it fills is one, where it used to ask for whatever page Load more had last reached. A page appended after new items arrived no longer repeats ones already loaded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14 KiB
14 KiB