minus-squareDaniyyel@lemm.eeOPtoSupport (lemm.ee)@lemm.ee•Issues with external avatars and metadata imageslinkfedilinkarrow-up1·20 days agoThanks for the reply. Regarding the avatars in Connect, I see that it tries to load https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2Fc6d6b005-8790-4d12-a11e-ef2cba2cb397.png?format=webp&thumbnail=64 , which indeed leads to a 404 error. The problem is in the additional query parameters added to the URL. Without them the image does load. It’s not just a URL encode issue, as the fully URL-encoded https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2Fc6d6b005-8790-4d12-a11e-ef2cba2cb397.png%3Fformat%3Dwebp%26thumbnail%3D64 also gives the same error. So it might just be a bug Lemmy itself. linkfedilink
Daniyyel@lemm.ee to Support (lemm.ee)@lemm.ee · 20 days agoIssues with external avatars and metadata imagesplus-squaremessage-squaremessage-square2fedilinkarrow-up16
arrow-up16message-squareIssues with external avatars and metadata imagesplus-squareDaniyyel@lemm.ee to Support (lemm.ee)@lemm.ee · 20 days agomessage-square2fedilink
Thanks for the reply. Regarding the avatars in Connect, I see that it tries to load https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2Fc6d6b005-8790-4d12-a11e-ef2cba2cb397.png?format=webp&thumbnail=64 , which indeed leads to a 404 error. The problem is in the additional query parameters added to the URL. Without them the image does load. It’s not just a URL encode issue, as the fully URL-encoded https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2Fc6d6b005-8790-4d12-a11e-ef2cba2cb397.png%3Fformat%3Dwebp%26thumbnail%3D64 also gives the same error. So it might just be a bug Lemmy itself.