If it's just a private instance, your storage needs will be way less. We use object storage, so it's actually pretty cheap (like $5-10 a month iirc). We're not storing that all on the server disk.
I've been considering a private instance myself so that's good to know.
If you're federating with everything by default, would that not also federate all the images and take up space that way? Or are images always just referenced from their origin instance?
I'm running a quite small instance and currently the full media storage is 234GB. That being said I pay $3 per month for the storage on Cloudflare R2 so that's fine. You could get more for cheaper probably with a service like Backblaze B2.
The main database (non-media) currently takes up 36GB.
I'm on a private instance. My lemmy volume as a whole is currently 72G.
5 is probably a bit undersized and liable to cause pool timeouts. But like 15 should give you enough room depending on your provider's affordability. You can always delete old data periodically.
You can configure the maximum size of image you will federate. You could set it to essentially 0 and you will store like no images. Downside is you will have to fetch images from other instances, whose servers may not be close to you.
For reference, Feddit.dk has a 5MB image limit. My storage is only about ~60 GB
Often just nuking all image uploads made during a certain time period. Which is why old image threads in Lemmy have time periods littered with broken images.
I don’t understand why Lemmy needs to have a built-in image server at all. Reddit didn’t have one for the longest time and it was fine. Sure, I don’t think anyone would be particularly happy with going back to Imgur etc., but it doesn’t seem worth the trouble.
Admins can purge posts manually which actually deletes them. Or use tools like db0's lemmy-safety that tries to automatically search for CSAM and wipe it.
I think the problem here is the user didn't finish their post which means the photo was uploaded but not associated with a post and therefore not purgeable that way.
Often they delete all images during the time frame of a CSAM attack, as that has been the only real feasible way to ensure images weren't left behind. Though I think a few images have started using AI detection methods to remove images like that automatically (read up on that here and here), also Pict-rs now has a Log linking uploaded images to the user, so now images can be purged with the users.