Comment on Tuesday SOTD Thread - October 24, 2023
walden@sub.wetshaving.social 1 year agoYes, I restarted haha. I took a backup now that everything is working. It turns out the problem was caused by ME earlier today, changing the icon. I changed the banner, too (it’s Tabac now), but that didn’t hurt anything. Anyway, I had to modify the frickin’ database to get things working again. Ridiculous. Now I’m going to be nervous any time I want to change the banner/icon.
Your points regarding pict-rs (the software that handles pictures for lemmy) – to my knowledge nothing gets deleted. It’s a big of a problem long term, but like you said storage is cheap. One day we can even move all of that data and host is somewhere else if storage becomes a problem. Pict-rs is mostly clogged up by thousands/millions of thumbnails. It keeps thumbnails from every federated post in addition to the uploads from our users. Our pict-rs folder is currently sitting at 8-9GB.
HomeAwayFromHone@sub.wetshaving.social 1 year ago
Just poked around because I was curious, it does look like the config for pict-rs lets you specify a format to convert things to and a max size/quality: git.asonix.dog/asonix/pict-rs/src/…/pict-rs.toml#…
I’d suggest WebP with a quality of 85 and max dimensions of 3840x3840 (because 4k is 3840x2160).
That takes djundjila’s photo for today (a 4236x2677 jpeg) from 1.9Mb down to 360Kb for a 3840x2427 WebP.
You might also consider AVIF as that’s widely supported as well and looking like it’ll probably become the new standard but for now is a bit CPU intensive until CPUs start adding SIMD for it. Too bad JPEGXL lost momentum, it was kinda better (and less CPU intensive). But if the server doesn’t mind chewing on it …that same SotD as a quality 66 AVIF is just 160Kb, eg. less than a tenth the size.
For more info about quality settings: industrialempathy.com/…/avif-webp-quality-setting…
walden@sub.wetshaving.social 1 year ago
Nice, I’ll look into this stuff. Pretty cool.
The weird part is I downloaded a photo that had been uploaded here, and re-uploaded it as the icon/banner (it doesn’t let you use a URL for the icon/banner). So that picture exists multiple times in our storage. It also crashed pict-rs, which in turn doesn’t let Lemmy boot. Initially my browser downloaded a .webp, but I changed the URL in order to download it in .jpg. I don’t have a good program that can edit .webp. So, maybe the problem was that I saved it as a .jpg, when it fact it was a .webp? The banner worked just fine, so I’m not sure. I only cropped the banner image, whereas I resized the icon.
HomeAwayFromHone@sub.wetshaving.social 1 year ago
Sorry, I just peeked at the config options and have never run any of this so no idea about the interaction with Lemmy or how to troubleshoot that. What I’d do though is spin up a toy instance on another subdomain/locally in a container and try to reproduce it there. Maybe with a copy of the data from production if that’s easy enough to pull off.
But ya only in retrospect - I wouldn’t have expected changing the banner or icon to be a risky operation.