Image bug is happening again, this time only limited to dbzer0 though (lemmy.dbzer0.com)

submitted 4 months ago* (last edited 4 months ago) by Draconic_NEO@lemmy.dbzer0.com to c/div0@lemmy.dbzer0.com

17 comments fedilink hide all child comments

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:

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

you are viewing a single comment's thread
view the rest of the comments

[-] Blaze@feddit.org 1 points 4 months ago

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

But to add to the confusion, that picture works on dbzer0: https://lemmy.dbzer0.com/post/33680915?scrollToComments=true

[-] db0@lemmy.dbzer0.com 2 points 4 months ago* (last edited 4 months ago)

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.

[-] Blaze@feddit.org 1 points 4 months ago

But then wouldn't Lemmy.ml be impacted as well? They're still the 4th most active instance

[-] db0@lemmy.dbzer0.com 1 points 4 months ago* (last edited 4 months ago)

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

[-] Blaze@feddit.org 1 points 4 months ago

Interesting to see that Tesseract is not impacted

this post was submitted on 19 Dec 2024

13 points (100.0% liked)

/0

1615 readers

2 users here now

Meta community. Discuss about this lemmy instance or lemmy in general.

Service Uptime view

founded 2 years ago

MODERATORS

db0@lemmy.dbzer0.com