See the screenshots.
Basically, people posting to !alternativenation@lemmy.world from lemmy.world or other instances all seem to work well, even going to Mastodon with no issues.
But lemmy.ml doesn’t seem to be seeing many of the post and is slow to update things like pinned posts.
Nor does lemmy.ml posts to the community seem to be going to Mastodon.
Challenging to build a community on Lemmy when one of the big instances can’t see many of the posts making an active community of over 1500 users seem dead.
lemmy.ml view: https://lemmy.ml/c/alternativenation@lemmy.world
lemmy.world view: https://lemmy.world/c/alternativenation
mstdn.social view: https://mstdn.social/@alternativenation@lemmy.world
I believe the federation queue for world is a little way behind and it’s doing its best to catch up.
I’ve seen a lot of lag and downtime from lemmy.world off and on. It seems like they get hit with DDoS or have maintenance issues (for lack of any real IT knowledge). I get the feeling they’re getting squeezed and targeted because they’re the flagship instance, but that’s just speculation on my part.
(Posting from kbin.social in case that matters.)
Officially the flagship is still lemmy.ml; lemmy.world is actually a relatively recent addition to the network (but grew the quickest).
“Flagship” in this sense would mean the biggest and most notable, seeing as how the the very nature of Lemmy means there’s no single figurehead or central instance.
lemmy.world has had massive issues and a bunch of downtime for the last several days, and that might have something to do with it.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !alternativenation@lemmy.world
