When scrolling through Lemmy, I often will see the same posts from the previous page - usually as the first links on the current page I’m on.

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      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.

      • Thehalfjew@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        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.

        • hedgehog@ttrpg.network
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          In an endlessly scrolling implementation, you’d just scroll up.

          Without endless scrolling, it could behave as follows:

          1. Moving back to page 1 takes the user to where they were on page 1 when they navigated away, with the same items visible
          2. 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.