Earlier today I wanted to post a PNG file that was 7 Mb and burggit basically got stuck uploading. I ended up resizing it so it would be under 4 Mb and that solved it but ideally I would like to preserve the size and quality as much as possible.

That got me thinking of using webp instead but I’m not sure how compatible lemmy is with it (not to mention 3rd party apps). Could an admin enlighten me on what format I should try to use for still images? Much appreciated.

  • Burger@burggit.moe
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 year ago

    Did you get a weird json error? If so, that’s why. Lemmy is hardcoded to automatically timeout the upload within 10s. There’s a GitHub issue where they’re wanting to use the nonblocking endpoint for uploading images (https://github.com/LemmyNet/lemmy/issues/2460) but it looks like that might be a bit.

    Still image webps are fine I think. But you can always use shota.nu that @Disabled@burggit.moe kindly setup and embed them using ![](your.url.here) for larger images/video. Ensure you’re using the direct link to the image though.

    E: I guess webps suck in general follow what Nazrin said.

    • Sheep@burggit.moeOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      No json error that I could see, it just was stuck uploading forever.

      Last time I tried using shota.nu and linking directly to the images in the URL field, a lot of posts ended up having broken/non-loading images. Are you saying I should be using the post body instead?

        • Sheep@burggit.moeOP
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Ah, I think that might have been the issue. I just checked the URLs I posted weren’t direct image links even though they ended in the image extension. I’ll try with the direct link next time and see if that fixes the problem. Thanks!

        • Burger@burggit.moe
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          If you’re talking multiple images like a gallery. You’ll want to post the next set in the body after the first one you put in the URL bar, I think. I’ve never done multiple images before so I’m just going off of memory.

      • Disa@burggit.moeM
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        here’s an example of an embeded shota.nu image:

        and here’s an image as to how I did that:

        As far as images not loading, Shota.nu had a slightly rough start, did a decent chunk of fiddling the first like 2 days it was up, it should be more reliable now. It’s possible the images you saw that were having trouble loading was during a brief period of downtime or while I was having some troubles with it that I was trying to fix. They also might not have been the direct image links (which have /ss/ before the file name) those seem to have some trouble embedding properly in Lemmy.

        • Sheep@burggit.moeOP
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          They also might not have been the direct image links (which have /ss/ before the file name) those seem to have some trouble embedding properly in Lemmy.

          This turned out to be the issue I think. I used url instead of direct_url in the config I made for sharex so I was posting the normal url. I’ll be trying to use shota.nu direct links from now on and see how it works!

  • Nazrin@burggit.moe
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Lemmy sucks at webp’s. Use JPG with the quality slider all the way up.

    You can also ask yourself -> What is the screen resolution that this image will be viewed on? There’s no point having a 4k vertical image if 4k screens are vertically only 2160 pixels high.

    Also, try out https://imagecompressor.com/

    • Sheep@burggit.moeOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      That’s true but I always try my best to preserve the original size because I hate downscaling artifacts. I suppose using JPG is the best option if webp is going to have compatibility issues. Thanks for the compressor link!