TL;DR: Lemmy upgrade some time early in the new year. I also recently enabled image proxying, let me know if you noticed.
I thought I’d make a quick post just to explain the plan for updating Lemmy.nz to the latest Lemmy version and another recent change to image proxying.
Lemmy upgrade
Some of you make have noticed that Lemmy 0.19.8 just came out, and yet we are still on Lemmy 0.19.5.
There have been various bugs in 0.19.6 and 0.19.7 that while not critical, there was also no reason to rush the upgrade and I decided to wait for 0.19.8 which had a fix for some thumbnails not working that was broken in I think 0.19.6.
My plan is to give a little time to see if others have issues, and then upgrade to 0.19.8. Most likely this will be early in the new year. I don’t believe there should be any significant downtime so I will probably just do it when I am ready. Before I do, I’ll do a test run and see how long it takes, then decide then.
As always, I’ll post on the Lemmy.nz Matrix chat before I do it, and if I am having any issues.
Image proxying
You may have noticed I have enabled imaged proxying some 3 or 4 weeks back. This means all images are loaded from the Lemmy.nz server instead of whichever instance is hosting it. Personally I have found there to be significantly less instances of an image not loading. I have also noticed some images load a bit slower than before, which I think is if the image is not already cached then Lemmy.nz has to download it, then you have to download it from Lemmy.nz, so this tends to happen more on smaller communities.
However, overall I feel like the experience is improved with image proxying turned on (even if it has doubled CPU usage of the server).
As always, happy to answer any questions and hear your feedback 🙂
within the db, been on postgres 16. It didn’t take too long, maybe 3 min on my small db
lemmy-1 | 2024-12-14T22:46:57.114874Z INFO lemmy_db_schema::schema_setup: Running Database migrations (This may take a long time)...Ah yip, thanks for the heads up. I’ll do a test run fist and see how long that takes, our database is pretty big but it will depend on specifically what is being migrated.