The thing to do is ask about these things on Mastodon - people might answer, features like this might already be in the works.
I tend to just open up the browser interface and scroll down will I don't recognise things, then read upwards. I've wondered about writing a took to do that, the idea being that if I do so and find it useful then I can offer it to others, and then if it becomes popular then it might get integrated into the code. It is, after all, open source. My problem is that I can't see how the interface would work. "Displayed" is not the same as "have read", and if i's been a while then it might be along way back.
It's things like this that let to the "Things you might have missed" feature in Twitter. Does Mastodon need something similar? Personally, I prefer it as it is, but I can see how others might want something different.
Similarly, I have thought about writing something, but lack of time and engagement have meant that I've never got around to looking at it.
The interface works well with the Twitter clients I've used, usually involving showing a count of unread messages which decreases as one scrolls up. All can be marked as read by scrolling to the top (e.g. by tapping on the count). I suspect it might be harder to manage given the federated nature, though.
I tend to just open up the browser interface and scroll down will I don't recognise things, then read upwards. I've wondered about writing a took to do that, the idea being that if I do so and find it useful then I can offer it to others, and then if it becomes popular then it might get integrated into the code. It is, after all, open source. My problem is that I can't see how the interface would work. "Displayed" is not the same as "have read", and if i's been a while then it might be along way back.
It's things like this that let to the "Things you might have missed" feature in Twitter. Does Mastodon need something similar? Personally, I prefer it as it is, but I can see how others might want something different.