Yep I was able to reproduce the issue. Unfortunately the issue is only present in the release build and not debug builds so I did not catch it earlier. I am issuing an emergency release now.
I just tested it and it seems to work consistently for me. The way it's designed to work is any post you scroll past (eg. the post has to be scrolled completely off screen) will be marked as read. If you think it should work differently or if this is not what you see happening please let me know.
Also if you could share a video that would also be helpful for me to look into the issue since I can't reproduce it on my end.
Update
I reviewed the code for this and I found a minor flaw however it should still be marking all posts above a certain point as read, it's just the "line" it uses to figure out what to mark can be unpredictable. Eg. an item can be scrolled a off screen and still not marked as read until a certain amount of things have been scrolled on screen. I've updated the logic so it items scrolled off screen are instantly marked as read. This change will go out in the next update.
I'm shooting blanks!
anal-ytics
Maybe also include a current list of trending communities, similar to the daily post in !trendingcommunities@feddit.nl?
That's actually where I got the idea of a list of suggested communities from. The suggestions will be based on what is trending.
Sort the results by number of posts, or monthly average users, or by community with the most recent post. Exclude communities from dead or defederated instances. For example, when lemmyf.uk shuts down every instance they were federated with will retain local copies of their old communities. There is no reason to refer users to those ghost town communities.
Unfortunately both of these ideas would be difficult to implement on the client side without some sort of server side support. These features are better suited for the Lemmy server than a client :(. The client already allows you to sort the results however the way they are sorted isn't always intuitive.
I've begun collecting data for the trending communities feature. I will let it run for ~a week before I start using it in the app.
~~Update for users who downloaded the app from the Play Store: it looks like the app has been chosen for manual review. Usually when this happens it takes substantially longer to get the release approved by Google. I'll update this comment/post once the release is reviewed.~~
Update is approved. I'm rolling the update to beta users then to release ASAP.
No problem. Unfortunately it looks like this release is stuck in review. It probably got selected to be manually reviewed by a real person or something.
Thanks!
So that's why it's called boxing day
Yes. I am aware of the crash in the latest release. I am trying to get an emergency release out ASAP to fix the issue. You can see more information about it here: https://lemmy.world/post/21526783.