Nah, it happens for me too. It doesn’t seem to happen (as much) using alternate frontends or apps, so I think it’s the actual front end that is freezing (on the server side) rather than the lemmy backend.
I have some tweaks to try and some instances are running multiple UI containers which I might try as well, just need a chance to test it all first before doing it on the live one, and there’s also a minor lemmy version to upgrade to as well. So many jobs 😆
Thanks for the support! One thing wouldn’t be so bad but I have another dozen I run on a home server, and I’ve been making some big changes so trying to tidy up that first (especially so I can free up the space for cloning Lemmy’s 300GB+ of data to do a test run). I’d hoping that work will be complete soon so I can create the lemmy test instance and try out some changes plus test the lemmy upgrade.
I’m going to try to work out the setup running multiple front end Lemmy containers because it’s super annoying when it freezes up. People shouldn’t have to switch frontends just to use Lemmy!
Things have come a long way in the 18 months+ since I started this instance. The default UI may freeze occasionally but back at the beginning there was a cron job to restart it each night so it didn’t run out of RAM (IIRC, Lemmy.world had to restart every 30 mins). It has come a long way.
Plus now there are tools like the one to check federation is working, the automod, the batching tool that helps us keep up to date with the Lemmy.world flood of federation, and more.
Nah, it happens for me too. It doesn’t seem to happen (as much) using alternate frontends or apps, so I think it’s the actual front end that is freezing (on the server side) rather than the lemmy backend.
I have some tweaks to try and some instances are running multiple UI containers which I might try as well, just need a chance to test it all first before doing it on the live one, and there’s also a minor lemmy version to upgrade to as well. So many jobs 😆
Good to know about the alternative frontends.
I don’t know how you do it, but I’m glad you do. 💛
Thanks for the support! One thing wouldn’t be so bad but I have another dozen I run on a home server, and I’ve been making some big changes so trying to tidy up that first (especially so I can free up the space for cloning Lemmy’s 300GB+ of data to do a test run). I’d hoping that work will be complete soon so I can create the lemmy test instance and try out some changes plus test the lemmy upgrade.
Just had the freeze problem and the alternative back end works fine. So, thanks for the tip!
I’m going to try to work out the setup running multiple front end Lemmy containers because it’s super annoying when it freezes up. People shouldn’t have to switch frontends just to use Lemmy!
Silver lining is I like this front end better (The old.lemmy one).
Oh nice! Yeah that can be pretty nostalgic.
Unfortunately I always get stuck with mod/admin activities on the alternative frontends so end up back on the default one.
Fingers crossed that one day a lemmy mod/admin will write a client for you.
I really like info-dense screens.
Things have come a long way in the 18 months+ since I started this instance. The default UI may freeze occasionally but back at the beginning there was a cron job to restart it each night so it didn’t run out of RAM (IIRC, Lemmy.world had to restart every 30 mins). It has come a long way.
Plus now there are tools like the one to check federation is working, the automod, the batching tool that helps us keep up to date with the Lemmy.world flood of federation, and more.
If you like data, you could check out: https://grafana.lem.rocks/d/bdid38k9p0t1cf/federation-health-single-instance-overview?orgId=1&var-instance=lemmy.world&var-remote_instance=lemmy.nz
You can play with the settings, that’s set to Lemmy.world to Lemmy.nz federation. Or visit https://grafana.lem.rocks/ to see the different dashboards.
Edit: I’m wondering now if you meant the compacted post view of old.lemmy.nz but hey now you have some info screens of federation data 😀