I can’t upload any kind of image to Lemmy. Regardless of device I use, iPhone/Voyager or Mac/Firefox, I get this HTTP 403 error. The issue persists regardless of which wireless network I am connected to.

This is obviously a false positive. Is there someone I can talk to about unblocking me?

  • Darkassassin07@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Had someone ask how, so I’ll drop this here too:

    When you finish uploading to imgur, you’re brought to a full webpage with the image embedded in it like this:

    https://imgur.com/a/SzSKW5M

    You want to right-click on the image and select ‘open image in new tab’ which gives you this:

    https://i.imgur.com/GFTwYm3.jpg

    (if you’re on mobile first select ‘desktop site’ from the browsers options or you’ll get a low quality .webp version from the open image button. It’ll work, but many ppl hate it)

    Finally format it like this to embed it in a post/comment:

    ![](https://i.imgur.com/GFTwYm3.jpg)

    (I added backslashes to the front of that to prevent it embedding the link as an image and show you the formatting instead)

    • CreatureSurvive@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      For Imgur on mobile you can actually get the full quality image url by doing as you said, with one extra step:

      • request desktop site
      • tap image (opens full quality image)
      • long press image -> Copy Link

      This will provide a direct link to the full quality jpg/png rather than the low quality webp

      • Darkassassin07@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        That’s unnecessary. When viewing the page with ‘desktop site’ enabled, it already loads the full quality jpg/png. Tapping/clicking on it just expands that file to fill the screen, it doesn’t load a new file.

        Webp is only used on the mobile site.

        (at least that’s the results I get re-testing just now via chrome and forefox android)