The network Burggit is on is experiencing performance issues. I’d encourage everyone to use shota.nu for right now if you can. I talked to the host about this and evidently it’s an upstream issue with the datacenter.

The datacenter is refusing to help out with this and thinks everything is working fine so there’s plans for migrating to a new datacenter that are underway sometime soon. So in the meantime, I’m afraid we need to just grin and bear it.

Lemmy errors out if the NFS mount is nonresponsive. It doesn’t like not being able to access the huge swathe of pictures that are stored on the server. I’ve switched the NFS mount to TCP and have it retry the connection every second in an effort to mitigate the severe packet loss.

As I was composing this, the packet loss shot up to 90% so I don’t think even that will help…

That’s really all I can do for right now. I wish there was more that I could do to resolve this… 😔

  • @Mating6267
    1•5 months ago

    I’m on the same version.

    I’ve set it so that my home feed is set to “Subscribed” and then when I scroll normally, the app crashes.

    The crashing specifically happens when I am scrolling through the “Subscribed” feed while signed in to my Burggit account.

    This doesn’t happen on the “Everything” feed or any other feed in Burggit. This also doesn’t happen on any other lemmy site.

    Will test this out tomorrow on another device to check.

    • RA2lover
      2•5 months ago

      Can you check the current status of each community you’ve subscribed to? burggit removes content from communities whose instances have defederated but i haven’t seen this remove subscriptions from users (which would probably take significant additional effort to implement as doing it properly would require sending unsubscription requests to communities in newly defederated instances). I’m suspecting there’s an unhandled attempt to fetch content from one such community.

      • @Mating6267
        1•5 months ago

        I unsubscribed from one community from rqd2.net and it fixed my issue. But it’s weird that that fixed it since Burggit is still federated with rqd2

    • @BurgerOPMA
      1•5 months ago

      I tried setting subscribed to default like you had and am still not able to duplicate this. I forgot to point out that this is a fresh install, so maybe clearing data/reinstalling the app is in order?

      I primarily use Burggit in a PWA on mobile since it seems to work pretty darn well by default. I’m on Android 13 too if that matters.

      • @Mating6267
        1•5 months ago

        I’ve figured out the reason, but not exactly.

        The cause of this crash has something to do with the specific customization settings of my Sync app.

        my Sync backup file. Please try to Restore this backup file to your Sync app and see if you can reproduce the crash

        I don’t know exactly why the crash only happens on the “Subcribed” feed on Burggit and not in any other lemmy sites

        I unsubscribed from one community from rqd2.net and it fixed my issue. But it’s weird that that fixed it since Burggit is still federated with rqd2

        • @BurgerOPMA
          1•5 months ago

          Which community was it? I’m curious to see what data the server tries to return, assuming I can reproduce this on my end.

          E: I noticed that it’s running 0.19.0. Maybe try another server we’re fed’d with that runs an older version to see if this same behavior happens.

          • @Mating6267
            1•5 months ago

            Maybe try another server we’re fed’d with that runs an older version to see if this same behavior happens.

            I’m subscribed to other communities on the same server so it was weird that subbing to that one specific community crashes the app.

            • @BurgerOPMA
              1•5 months ago

              This appears to be an app issue, then. I scrolled through my subscribed feed on the Boost app and even found a post from that community, and no crashes occurred there. Nothing I can do about it, I’m afraid. I guess report the issue to the maintainer and hope that you don’t get banned for the contents of the report (lol)?

            • @BurgerOPMA
              1•5 months ago

              It outright crashes. The logs don’t show the instance trying to send anything when it happens, so it’s purely a client-sided issue… Do try another community from an instance that’s fed’d that runs an older version of Lemmy to see if it happens with that one too (If you can find one.)