Their image link goes to a site that has a barrier between the link and the image (a cloudflare “are you human” captcha), so the embedded image does not properly load unless you actually go to the link in a browser.
Only a direct link with nothing else around it actually works when embedded into a reply, otherwise it’s blank/a broken image icon. Imgur links tend to be the same way unless you make damn sure you have the true, direct URL for the image.
Image loaded in external browser after checking the human box:
Personally, I find it best to just save and reupload the image to Lemmy. Guaranteed to work for everyone.
Not exactly, though! At least for me, opening the comment via browser is enough. As in, the embed loads when it does not in my client (Sync). Does Lemmy (the web client) have some smarts for resolving the true image URL?
The website interface itself for this thread also shows the image as a blank reply for me. At least Yiffit’s and Lemmy.World’s (which afaik is the default Lemmy uses). The url going through your instance might be something Sync is doing. The OP’s link goes straight to the image yarn url.
Hmm, it works with other instances. Probably an issue with some fork. Perhaps it treats all links as being on Lemmy and tries to cache them via ActivityPub, which obviously fails.
Did you embed that image manually or did you use a graphical editor?
I’m asking because I’m seeing more and more seemingly empty posts, and just now I’m noticing that there’s an image there, but the URL is wrong. Yours points to my home instance, but of course the image doesn’t exist there: https://sopuli.xyz/api/v3/image_proxy?url=https%3A%2F%2Fy.yarn.co%2Fcc4c71fc-cacd-44f6-aaaf-9aa5d757fb35_text.gif
I’m assuming that https://y.yarn.co/Fcc4c71fc-cacd-44f6-aaaf-9aa5d757fb35_text.gif is the correct link, but that gives
<Error> <Code>NoSuchKey</Code> <Message>Key not found</Message> </Error>Their image link goes to a site that has a barrier between the link and the image (a cloudflare “are you human” captcha), so the embedded image does not properly load unless you actually go to the link in a browser.
Only a direct link with nothing else around it actually works when embedded into a reply, otherwise it’s blank/a broken image icon. Imgur links tend to be the same way unless you make damn sure you have the true, direct URL for the image.
Image loaded in external browser after checking the human box:
Personally, I find it best to just save and reupload the image to Lemmy. Guaranteed to work for everyone.
Not exactly, though! At least for me, opening the comment via browser is enough. As in, the embed loads when it does not in my client (Sync). Does Lemmy (the web client) have some smarts for resolving the true image URL?
Weird, it loads for me in sync, but there have definitely been times where images don’t load. There must be something else going on
The website interface itself for this thread also shows the image as a blank reply for me. At least Yiffit’s and Lemmy.World’s (which afaik is the default Lemmy uses). The url going through your instance might be something Sync is doing. The OP’s link goes straight to the image yarn url.
Right, so opening the comment in browser takes me to the commenter’s home instance, (lemmy.sdf.org), where it does load:
https://lemmy.sdf.org/comment/17416807
It does not load on my home instance (sopuli):
https://sopuli.xyz/post/21909152/14297245
Maybe a regression in Lemmy since the two instances are not on the same version (0.19.3 works, 0.19.8 does not)? Or a backend configuration thingy?
Maybe? I’m not getting the image to load properly even there, myself, in Jerboa or the instance’s own site on a browser.
Perhaps it’s a federation issue? Or a combination of version and federating the content between higher version instances?
deleted by creator
The first F after the domain belongs to the %2 and has to be removed from your result.
Thanks. Man, I’m a web dev. I should’ve been able to work that out!
I know webdevs who might not even have gotten as far as you did, so 🤷
Hmm, it works with other instances. Probably an issue with some fork. Perhaps it treats all links as being on Lemmy and tries to cache them via ActivityPub, which obviously fails.