I was waiting for new versions, but the disk filled up faster than I expected. I'm moving 400GB image archive from local disk to object-storage. Unfortunately the process is very slow. It will take several hours.
Images are transcoded but thats not the problem. The problem is lemmy literally downloading every remote posts thumbnails to our archive. There is no option to opt out.
I looked at the images now and I will tell you for a fact that they are not being transcoded and saved. to transcode and save image to desired format you have to have set the following environment variable for the pictrs service in the docker-compose file: PICTRS__MEDIA__FORMAT=
When I look at your communities, I find images saved as png, jpeg, jpg, but not as webp. Saving images as webp/avif/jxl will result in an incredible reduction of storage requirements.
I wanted to ask if you are storing images after transcoding them or not. 400GB image archive seems quite a bit High to me.
If you are no,t I highly recommend that you transcode the images that the users upload, it will significantly reduce the size of your image library.
I recommend that you transcode to webp format. I tried making avif work but it wouldn't and jxl is still ways of.
Images are transcoded but thats not the problem. The problem is lemmy literally downloading every remote posts thumbnails to our archive. There is no option to opt out.
I looked at the images now and I will tell you for a fact that they are not being transcoded and saved. to transcode and save image to desired format you have to have set the following environment variable for the
pictrs
service in the docker-compose file:PICTRS__MEDIA__FORMAT=
When I look at your communities, I find images saved as png, jpeg, jpg, but not as webp. Saving images as webp/avif/jxl will result in an incredible reduction of storage requirements.
oh shit you are right! It used to be default but probably removed in new versions. I added it back. Thanks!