First of all, love the design and overall user experience. Are the user requests proxied through the Thunder server though? Everything loads so much slower compared to other apps.

  • @darklightxiM
    4•1 year ago

    Hey! There are no servers that Thunder proxies to, it sends everything directly to the instance you are on. The main issue with slowness will usually come because the instance you are in is experiencing server issues or timeouts because of too much traffic

    If you are not logged in, it will default to the lemmy.world instance, which is currently experiencing a lot of delays (at least when I am using that instance)

    Which instance are you on? You can try a different smaller instance if you have an account elsewhere and see if the slowness still persists. If it does persist, then it may then be an issue with Thunder and you can open up a GitHub issue on it!

    • @[email protected]OP
      1•1 year ago

      Thank you for the comment. It’s good to know that there’s no middleware between the user and the server. However I’m pretty sure the slowness is not caused by the server as I’ve been testing with other apps at the same time(wefwef, liftoff), only Thunder exhibits such behavior with the same server(sh.itjust.works).

      • @darklightxiM
        3•1 year ago

        Hmm, in that case it could be Thunder then. Thunder loads 20 posts at a time, so depending on the other apps and how many they tend to load up, that could be a difference.

        It could also be because the feed contains a lot of images, which causes Thunder to do some calculations that it needs to determine width/height calculations to pre-allocate the correct space on display to reduce things shifting around.

        If you could determine a bit more details, it would be helpful for me to look deeper into the issues and find a fix! I would suggest trying to load up a feed with mainly texts vs images, and see if theres a big difference between the loading times

        • @[email protected]OP
          1•1 year ago

          That’s my theory as well, I suspect Thunder is trying to load too much data at one time. I’ll do more tests to see if there’s a pattern behind this.