I’m trying to view Lemmy from the browser but have already seen most of the posts at the top, so to get new stuff I’m trying to look at all communities sorted by new. But as I scroll down the page keeps refreshing the posts automatically and pushing stuff I’ve already scrolled past into view again, and sometimes causing misclicks. Is there a way to disable that so I only get new posts when I refresh the page?

This problem is only going to get worse if the site gets busier.

  • kiwi@kale.social
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    1 year ago

    The lemmy ui is removing websockets in the next update replacing it with a REST API. I suspect that will stop any new posts from popping to the top after load.

    People seem to not want new posts and comments moving things around on their page anyway.

    https://github.com/LemmyNet/lemmy/issues/2841

  • sexy_peach@feddit.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    There is no auto refreshing, it probably is this behavior, which is a bug. Might get fixed with the next update, if we’re lucky :)

    • menachem@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      I don’t think it’s the same thing. It looks like that user is watching the site reload the entire list, and inaccurately at that (they’re looking at all by new but seeing days old posts in between minutes old ones?). What’s happening to me is that if I just sit at the top of the page I can watch as new posts come in live, one at a time. Which sounds cool in theory, but really hurts the browsing experience!

      • sexy_peach@feddit.de
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Okay I see so it really is auto refreshing. I don’t think there’s a fix for that at the moment. The problem, that posts are coming in too fast always was a far away wish on lemmy xD

        • Menachem@midwest.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          That’s concerning. There’ll be a ton of problems like that if Lemmy actually sees a mass migration happen. Top of the list: what’s stopping people from vote brigading posts with accounts from different instances? I’ve had to create 3 of them just to be able to consistently access the site as the first one didn’t work and the second (this one) saw excessive loading times for a few hours.

          • sexy_peach@feddit.de
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Top of the list: what’s stopping people from vote brigading posts with accounts from different instances?

            I’ve had different reddit accounts as well, wouldn’t this work there as well?

            In short, nothing. Admins could check from which the votes are coming from and block that badly moderated server.

            • menachem@lemmy.mlOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 year ago

              At least with Reddit it’s easily detectable (in theory, assuming anyone cared) without putting in the extra effort of IP masking. Here it seems like it’d be impossible to counter even if it were done by a complete layman. If someone has just one account on 5+ different instances they could make a huge difference by voting on their own posts without ever being detected.

              Honestly, now that I think about it, it’s probably already happening to great effect considering how few people there are voting.

              But yeah, oh well. Hopefully something works out.

          • sexy_peach@feddit.de
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Also unfortunately lemmy is still fairly beta software. We only have two full times devs and it’s not been long ago that they were implementing some of the standard features we’re using today.

            We have to work with what we have.

        • borari@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          So I just noticed this behavior while sitting at the top of the All/New feed on my instance. I noticed that the surge of “new” posts that came in were all pretty old, and all from one or two communities on another instance. I’m now wondering if maybe there’s some sort of race condition going on with the interaction between the database and the front-end, where these old posts are being considered “new” when they’re initially pulled in to the local instance db.

          • sexy_peach@feddit.de
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            when they’re initially pulled in to the local instance db.

            I know this, these posts are not pulled initially. Many times I have seen this with old posts that I had seen and voted on months ago.

            Soon lemmy will get html posts instead of websocket, I think that might fix it??