Comment

Comment on Why does Lemmy (and reddit) show posts from previous page on next page?

I don’t know if it is lazy as much as it is a design choice - remember at one point Lemmy actually auto updated (which meant posts were pushed down while you were browsing) and it was an intentional design.

github.com/LemmyNet/lemmy/issues/2841#issuecommen…

source

Sort:hotnew top

jet@hackertalks.com ⁨1⁩ ⁨year⁩ ago
It’s a valid design choice. But it is to keep the programming simple. One might characterize that kind of choice as lazy. Especially in terms of user interface. But I’m not beating up on Lemmy. I’m just explaining to the original poster the trade-offs that people make.

source
- Swedneck@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
  one man’s lazy is another man’s efficient and pragmatic
  
  source
- Thehalfjew@lemmy.world ⁨1⁩ ⁨year⁩ ago
  It’s not necessarily lazy. If I want to go back to a particular post I saw on page 1 when I’m on page 2, but it was knocked off the front page, how would I find it? It’s no longer on page 1, so back would miss it. I’d have to go to 1 and then back again to 2 to find a post that moved.
  
  It gets even more complicated when the algorithm also changes post order.
  
  Sometimes simple with minor inconvenience is the best option.
  
  source
  - hedgehog@ttrpg.network ⁨1⁩ ⁨year⁩ ago
    In an endlessly scrolling implementation, you’d just scroll up.
    
    Without endless scrolling, it could behave as follows:
    
    Moving back to page 1 takes the user to where they were on page 1 when they navigated away, with the same items visible
    
    When automatically fetching new posts, either expand the page (pushing nothing off) or make it visually clear that pages will be pushed to the next page. Or just don’t fetch new posts automatically, and only reset the first / last post of a page if the user clicks Refresh.
    
    source