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.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.