Search

Right now, it shows a generic error image.

Are there specific resolution requirements, or?

EDIT: It solved itself. I guess Lemmy lags a little when propagating new community icons/banners.

EDIT: Looks like this is resolved now. For future reference, I had checked !support@lemmy.world, but I didn't think to check the announcements community, !lemmyworld@lemmy.world. I'll try to remember to check that space next time before posting. Thanks for chiming in, everyone!

ORIGINAL ISSUE:

I've noticed the last two game day threads on !caps@lemmy.world have not federated from my home instance (.ml) to either of the remote instances I've checked so far (<https://lemmy.world/c/caps> and <https://lemm.ee/c/caps@lemmy.world>).

The .ml posts' URLs are <https://lemmy.ml/post/22823350> (from two days ago) and <https://lemmy.ml/post/22885345> (from less than an hour ago).

The fact it's affecting multiple remote instances suggests that maybe there's some issue specific to .ml.

Searching recent support posts, I came across this federation health checker site, which indeed shows a spike in federation time from .ml to .world and lemm.ee, but it doesn't explain the cause.

Does anyone know why this is happening? Also, will the content eventually catch up on those remote instances or is it lost to the sands of time?

Depending on the answers to these questions, I might need to start posting from one of my alt accounts on another instance.

Thanks in advance.