Lemmy’s 0.19.6 introduces some bug fixes but it also introduced a nasty bug which breaks image rendering in many posts See here and since this instance hosts a lot of image based content it would probably be a good idea for us to hold off on upgrading until this is fixed. I do not know yet if this bug will apply retroactively, as in, if all posts made or affected by this will be fixed once a fix rolls out or if they’ll be screwed up forever or until editing or re-posting.
I encourage people in instances which have not updated yet to cross-post this to their instance’s meta community or ping their instance admins to let them know.
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/[%E2%80%A6]/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-interlacedi 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.
