When using the in-app share button to share images, a file called “image_proxy” is shared, not the image itself. This started happening for me when I switched to lemmy.zip from lemm.ee - I just tested lemmy.zip in Thunder and it works as expected, so seems to be some combination of server+Boost causing the problem.

    • hoshikarakitaridia@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 month ago

      Often the images themselves are called image proxy as well when I download it. This indicates the filename assigned to the downloaded image mirrors the url path instead of the filename it should be, which I am going to speculate is something like “[…]/image/image_proxy.php?filename=image_name”

  • C8r9VwDUTeY3ZufQRYvq@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Yep, I’ve been having the same problem for a while now. I’ve seen other posts about it here and there, but I’m not sure how actively boost is actually being developed…

  • Toes♀@ani.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    27 days ago

    Some clients can’t handle the new lemmy feature for caching images on the instance. Hopefully its resolved soon.