I have my “All” feed set to “Active” and I won’t even be scrolling or reloading it, all of a sudden 500 posts start rolling in at the top of the feed!

  • Jenga@beehaw.org
    link
    fedilink
    English
    arrow-up
    10
    ·
    2 years ago

    I assumed it happened when someone on your instance subscribed to a new community for that instance so it loads in all the posts since they are technically new. Definitely a bug

    • Frank Dew@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      2 years ago

      Interesting take on it. Another bug that I see often is a post with like 5 comments, but when I click on “comments” I don’t see any. Even mine in some cases! I’m not mad, I guess all of it will require some fine tuning to work flawlessly. Edit : I’ve found the problem. It the account settings I had unselected english in the languages list!

  • Frank Dew@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    2 years ago

    I saw that too, and most of the times it’s a lot of days old post in a specific community… maybe there are some problems with synch operations ? I don’t know.

  • Afteg@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 years ago

    Yeah honestly makes it kinda unusable when the page is constantly scrolling away from what im reading

  • planish@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 years ago

    Yeah stuff streams live to the client when it arrives on the server and the client is not putting it in the right place in the displayed list, just dumping it at the top.

    I heard the Lemmy devs are abandoning their whole websocket-based way of having the client and server interact, so that would probably sort it out if it ever happens.

    • little_hoarse@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 years ago

      i’m gunna guess it has something to do with the web socket connecting (from what i can see in the console) and not disconnecting when load is finished, so it just keeps loading whatever new content is available, instead of loading more when the user clicks reload

      • manitcor@lemmy.intai.tech
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 years ago

        yeah, if its dropping and checking every so-often you might get this, whats the overhead on keeping the socket open? I have used websockets very little.

        • little_hoarse@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 years ago

          no idea, i only know about side effects with react, where if you are fetching something, you should close the connection after it’s fetched, then re-open on component mount, unless you are going for a constantly updated type of application

          • manitcor@lemmy.intai.tech
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 years ago

            i think the intent is to constant update at least for one of these tabs, this is how mastadon currently works but its less bursty.

              • manitcor@lemmy.intai.tech
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                2 years ago

                im not sure what the user counts on on matadon vs lemmy, its working for them…for now. Note that over 2/3 of my traffic is coming from edge cache, these nodes, properly setup arent working as hard as it seems. The client side however.

  • Norrland4ever@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 years ago

    Borrowing the thread

    Mine is empty, when I log in after a day or so I still see 2, 3 day old posts. How do I get new ones?

    • cryball
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      2 years ago

      Those are all known bugs. Apparently the active/hot etc. aren’t updating properly after a server has been up for a while. Apparently the dev’s are already working on fixes.