42
Is it planned to mark posts as read on scroll past them?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Jul 2023
42 points (95.7% liked)
Memmy - An iOS client for Lemmy
5065 readers
1 users here now
founded 1 year ago
MODERATORS
No we can’t really do it. What if someone scrolls really fast, then we have to mark like let’s say 20 posts as read. Each mark as read is a separate API call. We can’t make a call with all the posts, the lemmy API isn’t that advanced. If we tried to make that many api calls it would get rate limited and you’d get errors from the backend.
Ah. Would the lemmy api need something like mark this list of posts (in a single call) as read to do this?
Edit: I see the api has things like getComment and getComments.
So something like markPostsAsRead instead of just markPostAsRead so you can send a list.
Yep exactly, it would need to offer us an option to send a list of post ids at once to mark as read.
what about adding a button to mark a post as read? i would find that more convenient than needing to open each post in order to mark it as read.
I believe we’re looking into adding a swipe to mark as read feature for feed items.
I’m out of my element here, but Voyager has mark read on scroll. Is there something in their PWA that could be helpful to establish this in Memmy, or is it only a thing because it’s a PWA?
What voyager does isn’t something we want to do - imo it’s a little rude to spam requests to the server owners like what they are doing. (If you scroll really fast like i described in my comment above) We could do the same thing, and maybe we will at this point, but i don’t really want to. If it were a big company with lots of servers then it’d be one thing, but that’s not the case with Lemmy.
And would it not be possible to "cache" the read posts client side and only send a list every minute or so?
Edit: sorry, I thought this was a lemmy discussion community and not memmy. I guess the lemmy api would have to change for this feature to be supported