this post was submitted on 19 Dec 2024
12 points (100.0% liked)
/0
1794 readers
21 users here now
Meta community. Discuss about this lemmy instance or lemmy in general.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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