Is there any way to stop the auto-refreshing of the home page in lemmy? I can’t read more than a post or two before a new flood pushes everything down.

  • Menachem@midwest.socialEnglish
    18·
    2 years ago

    Unfortunately not. I made a post about it a few days ago and apparently it’s an unintended behavior that will be fixed, it was just never an issue before since there were so few users lol

    • Menachem@midwest.socialEnglish
      14·
      2 years ago

      Also, the giant flood of posts you’re seeing is actually ANOTHER bug that happens as your instance federates with another; look close and you’ll see many of them are actually quite old. Refresh the page and those will disappear

        • ABlackWaltz@beehaw.orgEnglish
          6·
          2 years ago

          I do something similar - I’ve subscribed to a few communities now that have popped up at the top of my feed because I thought “oh, this looks cool”

  • Drew Got No Clue@lemmy.worldEnglish
    2·
    2 years ago

    I don’t think so. What kind of sorting are you using that pushes things down so quickly? New?

    Anyway, I guess you could use the RSS feed…

    • pickledgrits@lemmy.worldOPEnglish
      3·
      2 years ago

      It is faster with New, but I’ve used Hot as well. At any rate, I’ll just hang out until it’s fixed.

    • samick1English
      2·
      2 years ago

      If I select “All” it starts loading new content at the top and pushing everything else down, which is frustrating if you’re just scrolling and trying to read post titles. It’s also kinda cool that it loads new stuff in real time… just wish it were an option I could turn off.

  • Horselover Fat@lemmy.worldEnglish
    2·
    2 years ago

    I’m surprised this is the only post I found about this issue when I searched “pause feed”. I understand that it’s nice to see new posts added when you select “new” sorting, but on the other options is doesn’t really make sense.

  • Katana314@lemmy.worldEnglish
    1·
    2 years ago

    One of my ideas for a frontend change, something I’ll probably never bother coding, is a scroll maintainer; when content is being added, it looks at what the current “centered element” is on the page, and attempts to scroll you so that that remains in the exact same spot on the screen.

    I don’t know how successful or even practical that might be - and it takes me long enough to set up test codebases for my workplace.