[posting here because it seems like that’s the right way instead of @'ing CARCOSA and other admins et al]

hi, I recently posted a 12.9MB PNG by mistake before realizing how big it was, deleting, and reposting with a much smaller JPEG.

deleted post: https://hexbear.net/post/1655031 replaced with: https://hexbear.net/post/1655036

now I’m feeling bad that I wasted almost 13 megs of space for an image that is now only linked in a deleted post.

so my question is two-fold,

  1. any way I could tell hexbear to nuke the image in my deleted post?

  2. distinct from an active feature that would let me delete the image, I’m wondering if we have some sort of system for finding unreferenced images and garbage collecting them. part of me is worried about someone spamming hexbear with large images

  • YearOfTheCommieDesktop [they/them]@hexbear.netEnglish
    4·
    8 months ago

    I wouldn’t worry about 13MB, unless you have the ability to contribute code that would help with the issue. My understanding is that lemmy and pictrs aren’t currently that tightly integrated, and that the little popup you get in the browser when you upload an image is currently the only way for you as the end user to fully delete an uploaded image from pictrs (there is a token returned when you upload that is what allows you to go back and delete securely, but last I checked it wasn’t saved anywhere yet, upstream is working on it). Admins have more options at their disposal but to my knowledge there isn’t any automatic garbage collection. (spamming uploads of big files would be annoying but ultimately would get rate limited before it could get too destructive, and I believe they’d have to be unique files as well otherwise they’d just get added as aliases to the existing image by pictrs)