I tried it from 3 different webrowsers, on 3 different instances. As you say, it’s likely something with the app:-(. Though notably, this image URL does not end in a standard extension, so perhaps the app may have an improper method to read images that would require that, as the Lemmy code itself used to until recently. But I’ve only ever used a web UI so I don’t know anything else in this regard.
I tried it from 3 different webrowsers, on 3 different instances. As you say, it’s likely something with the app:-(. Though notably, this image URL does not end in a standard extension, so perhaps the app may have an improper method to read images that would require that, as the Lemmy code itself used to until recently. But I’ve only ever used a web UI so I don’t know anything else in this regard.