Recently noticed a resurfacing of the image bug that happened back when 0.19.6 was released where random posts with image links wouldn’t be detected as the images they are.
I’ve noticed it happening for several posts on the instance, here’s a few:
https://lemmy.dbzer0.com/post/33634525(Works now)- https://lemmy.dbzer0.com/post/33642831
- https://lemmy.dbzer0.com/post/33626225
I’m making this post here though and not in the Github issue since it seems to be affecting only this current instance. I checked and it doesn’t seem like lemmy.ml is affected at all. So in all likelihood it’s probably limited to dbzer0. If anyone else notices this elsewhere pleas feel free to chime in and provide post links (dbzer0 copy, the origins don’t help us since this is a dbzer0 issue).
Sopuli.xyz seems fine for the first post (https://sopuli.xyz/post/20326458?scrollToComments=true)
For the two others, they like to the Imgur post, not the picture itself, so that could be why it doesn’t work (sopuli has the same: https://sopuli.xyz/post/20321505 and https://sopuli.xyz/post/20332076)
What’s surprising is that lemmy.ml correctly displays imgur posts: https://lemmy.ml/c/196@lemmy.blahaj.zone?dataType=Post&sort=New
I checked their URLs and they do indeed link to the imgur images, not the main posts themselves, so it seems like the server is having trouble with imgur images.
We might be getting rate limited by imgur
Hm, strange. I just double checked, and when I click on the thumbnail square (empty, with just a big arrow), the first time it redirects me to the imgur full page, and then the following times it redirects me to the direct image, like what?
Anyway, it does not seem to be Imgur only, see thee same picture from catbox.moe working properly on lemmy.ml and not on sopuli
- https://sopuli.xyz/post/20353321?scrollToComments=true
- https://lemmy.ml/post/23751361?scrollToComments=true
But to add to the confusion, that picture works on dbzer0: https://lemmy.dbzer0.com/post/33680915?scrollToComments=true
So it doesn’t seem to be something only affecting dbzer0. As I mentioned elsewhere, it might be a rate limiting situation, where the originating source is preventing instances from caching that image for a thumbnail randomly.
But then wouldn’t Lemmy.ml be impacted as well? They’re still the 4th most active instance
No, by nature rate limits are random. It might just be that the image when received by lemmy.ml happened to not be in the rate limit window. Also this is just speculation on my end. Also I’m using the tesseract frontend (t.lemmy.dbzer0.com) and haven’t noticed this is issue at all
Interesting to see that Tesseract is not impacted
Works perfectly fine for me on all available frontends and the voyager app on android
The web UI as well? Which browser are you using?
Waterfox
Curious, this is what I get on Firefox
First one works on dbzer0, so maybe that’s the one they checked?
The first one seems to be working now, but the others still don’t work.
Can you check the second one ? The first one actually works on dbzer0 for me as well
