Lemmy NSFW

I’ve read the cloud engineering headache write up from a few different Lemmy servers now so I no longer can remember which ones are on CDNs and which ones aren’t. Are you backed by anything in particular? Once you are on object storage you are likely to find a surprising egress bill if you aren’t caching the images and other content at a higher CDN tier.

You should also more or less immediately get lifecycle policies setup in your object store to tier older posts into cheaper storage. It’s 10-20 minutes of learning effort that stands to save you thousands of dollars. The trade offs with storage classes are usually cheaper storage as reads get more expensive. Since Lemmy promotes fresh content there is likely a balance you can strike in your lifecycle policies to drive storage costs down for older content that is unlikely to be loaded a ton of times.

Hey, I've noticed two things since the downtime and migration.

1. NSFW is no longer automatically checked on submissions. I can deal with that, but it used to be automatic here.

2. When I submit a new entry, the submission hangs with a spinning wheel. But I notice that the actual submission goes through. Don't know why the web server just hangs like that. But it is annoying.

Thanks for all your hard work!

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.