34
Thanks. This is one of the reasons we generally don't upgrade immediately :)
This doesn't look like a Lemmy issue, the image host is incorrectly reporting an image as an octet-stream. You can't even trust the file extension, because that image isn't even a jpeg.
$ wget https://image.civitai.com/[…]/00091-28-1440-864-2024-11-02-0.7.jpeg # clipped
$ file 00091-28-1440-864-2024-11-02-0.7.jpeg
00091-28-1440-864-2024-11-02-0.7.jpeg: PNG image data, 864 x 1440, 8-bit/color RGB, non-interlaced
i love this kind of thing, why bother doing your sole job correctly? fuck it, this png image is a word document, who cares! also we're delivering it as a binary blob so you have to use clientside js to unpack it.
I saw it happening on a few posts on 196 as well too, plus it seems to work just fine on Lemmy versions prior to 0.19.6, so I think Lemmy is the problem: https://lemmy.dbzer0.com/post/31505839
The problem not happening on servers pre-0.19.6: https://lemmy.world/post/21870740
This might be a db0 issue tbh, here's that 196 post on .ml and slrpnk and it works fine.
The reason the AI posts works on previous versions is probably (I know nothing about how lemmy-ui works) because lemmy-ui sees a URL with an image extension and puts it in an <img> tag, they must've stopped doing in 0.19.6 and stated using the MIME type in the API instead.
It's not, it's still happening on the other instances, here's a different one on Lemmy.ml which isn't working, but is working here.
I think whatever that change they did was a bad idea, an example of trying to fix what isn't broken.