I’ve observed two issues with certain type of images on lemm.ee.
The first issue relates to external avatars, both user and community. In the Android app Connect they are no longer loading and just show a spinner. Only the avatars of users and communities on lemm.ee itself are loading. It doesn’t occur on web. And when using my lemmy.world account in Connect, all external avatars do load correctly. I think this started after the upgrade to 0.19.4.
The second issue is with metadata image, the og:image a page declares. This isn’t always shown on lemm.ee. As an example a post I made with my lemm.ee account on a lemmy.world community.
https://lemm.ee/post/31969605 - Next to the title it just shows a generic external link icon.
https://lemmy.world/post/15406863 - Same post but now via lemmy.world shows the image that the target webpage defined as its og:image correctly.
Hey! Thanks for the report.
I think the first issue is not something I can help with - probably the Connect app needs to fix something on their side.
For the second issue, see my comment here: https://lemm.ee/post/34118135/12479638
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.
