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!

  • little_hoarseOP
    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_hoarseOP
        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.

          • little_hoarseOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 years ago

            That seems unsustainable with more and more people joining. Especially on the “All” feed.

            • 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.