If I want to hide read posts, what causes something to be read? It does not seem to be just scrolling by it as in other similar apps.
If I want to hide read posts, what causes something to be read? It does not seem to be just scrolling by it as in other similar apps.
Posts are marked as read when you interact with them (vote/save/reply/etc) or tap them to view the comments.
We have an issue open for marking read on scroll. The trouble with that feature is that the API only supports marking a single post as read at a time, so we either have to fake it locally or spam the API. The former is problematic because it either introduces what amounts to a memory leak as we track every read post or results in posts being displayed as read and then popping back up when the cache evicts that info. The latter is obviously unacceptable and constitutes extremely poor API citizenship.
We’re currently working with the Lemmy devs to get a batch mark read endpoint, which will let us implement this feature without either of those problems.
Oh, that would explain why other apps such as Bean and Avery become unresponsive if I scroll a lot of unread posts. Thanks for the detailed explanation. I would have no problem with implementing this locally until lemmy has a solution at the API level. If those read marks could be in iCloud, that would be a bonus.
We’re hoping that Lemmy will add a way to mark posts as read in batches - this would mean that we could locally store ~50 posts as being read at a time, then notify Lemmy of those changes with a single request. This would be the ideal solution for us, and we’re working with the Lemmy devs to make this happen.
Storing read posts entirely locally would certainly be possible, but doing it well would take up a significant amount of our development time. We are currently prioritising other highly-requested changes (supporting Lemmy v0.19.0, image uploading, and a better search tab to name a few) in the next few updates whilst we work things out with Lemmy :)