Bug: timeline "new toots" counter is often wrong

Environment:

• OS:
  iOS 16.3.1
• IceCubesApp version:
  IceCubesApp 1.5.12

Description

First off, I ❤️ IceCubes, it has come so far so fast!
Maintaining timeline position is very important to me, and I see some reports here of opportunities for improvement [ability to restore position, etc]. I notice the position sometimes jumping back or ahead a toot or two when the app is brought back into focus and simultaneously auto-loading the timeline.

My issue is that the counter seems to get badly confused when I leave and return to the app, seemingly particularly when it was unloaded due to some iOS constraint and simultaneously there are new toots autoloaded in the timeline.

The symptom is simple:
Let's say I say 74 toots remaining in the timeline counter. I watch a video, save it to photos, send it to a friend in another app. Eventually returning to Ice Cubes, sometimes the counter is now completely missing. The timeline is still in the correct place [plus or minus a few toots] and the scrollbar clearly shows many toots to go, but the counter is missing.
Or ... the counter appears but it is a different number, such as (just now) "3". Presumably indicating 3 more toots have been found on the timeline.

It would be excellent if the counter were always accurate.

To that end, I'd like to suggest a behavior I've noticed in some other apps with long scrolling timelines, and really appreciate:

1. The counter is always present if there are unread toots.
2. The counter is the color it is now if we are looking at new toots.
3. If we scroll backwards (ie scroll down, away from new toots) the counter becomes a "greyed out/darker" version of its active color, while continuing to keep accurate count. This way one has a handy refresher/reminder of where one is in the relative flow of the timeline.

Cheers

No file or test is named. Reproduce the counter disappearing or changing after backgrounding and reopening IceCubesApp on the reported iOS and app versions, then trace the timeline unread-counter behavior across app lifecycle and autoloading. Done means the counter remains visible when unread toots exist and accurately reflects their count while scrolling.