You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you check to see if this issue already exists?
Is this only a feature request? Do not put multiple feature requests in one issue.
Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
Is your proposal related to a problem?
Currently when reading through posts on an active community, by the time I get to the bottom and hit "Next Page" more posts and comments are made, pushing many of the Page 1 posts onto Page 2, making me see half the same posts again.
This is rather annoying, since it means means it's possible to miss posts entirely if they happen to move between pages at the wrong time.
Describe the solution you'd like.
Reddit seems to cache a single post order until you do a full page refresh or your session gets too old. It's unclear to me if this is a client-side session thing or if the server actually keeps track of the historical post order for the user.
Describe alternatives you've considered.
A client could potentially make multiple page requests at a time and resort / deduplicate posts itself, however backend integration in the API would definitely be preferred for performance.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Requirements
Is your proposal related to a problem?
Currently when reading through posts on an active community, by the time I get to the bottom and hit "Next Page" more posts and comments are made, pushing many of the Page 1 posts onto Page 2, making me see half the same posts again.
This is rather annoying, since it means means it's possible to miss posts entirely if they happen to move between pages at the wrong time.
Describe the solution you'd like.
Reddit seems to cache a single post order until you do a full page refresh or your session gets too old. It's unclear to me if this is a client-side session thing or if the server actually keeps track of the historical post order for the user.
Describe alternatives you've considered.
A client could potentially make multiple page requests at a time and resort / deduplicate posts itself, however backend integration in the API would definitely be preferred for performance.
Additional context
No response
The text was updated successfully, but these errors were encountered: