[Bug] Previous and next posts incorrectly marked as read (sh.itjust.works)

submitted 1 year ago* (last edited 1 year ago) by threelonmusketeers@sh.itjust.works to c/summit@lemmy.world

7 comments fedilink hide all child comments

After entering and exiting a post in the feed, the previous and next posts are incorrectly marked as read.

This bug seems to be specific to when "swipe between posts" is enabled.

top 7 comments

sorted by: hot top new old

[-] idunnololz@lemmy.world 2 points 1 year ago

Thank you for reporting this bug. Will fix in the next release.

[-] threelonmusketeers@sh.itjust.works 2 points 11 months ago* (last edited 11 months ago)

Will fix in the next release

I'm on 1.71.3 (version code 288), and I think this bug is still present.

After entering and exiting a post in the feed, everything looks fine at first, but when I refresh the feed, the posts on either side are incorrectly marked as read.

Edit: Now it seems that the bug is gone, despite no change in the version number. Very strange...

[-] threelonmusketeers@sh.itjust.works 2 points 1 year ago

Thanks, that's great!

[-] threelonmusketeers@sh.itjust.works 1 points 10 months ago

Hello, just wanted to report that this bug is present in 1.72.1, version code 295.

I also found that if I manually mark a post in the feed as unread, that post becomes "immune" to being incorrectly marked as read by viewing an adjacent post.

Let me know if there is any other info which would be helpful for troubleshooting.

[-] idunnololz@lemmy.world 2 points 10 months ago* (last edited 10 months ago)

It looks like the underlying cause now is that the server auto-marks posts as read as soon as you fetch them and the app fetches the previous and next posts.

It looks like the API wasn't designed with this sort of use case in mind :/