Developer fighting 502s from Lemmys Servers.

  • 1 Post
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle












  • I would also like to add that there are PWAs (Progressive Web Apps).

    PWAs can be installed on most devices and share even more similarities with native apps (Native app = usually installed through app store). For example installed PWAs can be viewed in Fullscreen or work offline, even though they are still technically a webpage.

    So the advantage here is that you don’t need to use an App Store to have an app installed on your phone.

    And the main disadvantage is that the PWA can’t access most of the device’s APIs, that you could access through a native app. This means worse performance usually, no support for theming beyond dark/light (like Material You), no good access to on-device databases etc. This is also the reason why most apps aren’t PWAs.


  • Actually, I’m guessing wefwef is using the Js client, which usually returns a 503 or 500 when something goes to shit on the instance.

    I’m also developing an app for Lemmy and the only solution I found was to just keep request the data until the instance finally gives in to the pressure and works.

    So it’s less about “server is taking too long to respond” and more like “server responds instantly with a 503” because it’s overloaded and can’t handle any incoming requests.

    I’m also guessing a lot of traffic comes from comments since the way of loading those is kinda stupid. (You load only the top layer and then for each comment you request the children, which sums up to a huge number of requests).

    Lemmy should add more convenient APIs to reduce the amount of requests being made, maybe I’ll do that myself once I’m done with the app.

    Sorry for the long ass text.