See the screenshots.
Basically, people posting to [email protected] 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/[email protected]
lemmy.world view: https://lemmy.world/c/alternativenation
mstdn.social view: https://mstdn.social/@[email protected]
I believe the federation queue for world is
a littleway behind and it’s doing its best to catch up.I think they had to implement rate limiting for server stability so that’s probably a factor as well
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.)
yeah, I’m not sure where the issue is - .world? .ml? lemmy in general?
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.
Fair enough.
I’ve found this time of day that lemmy.ml runs the slowest/most overload.
I have the same problem with [email protected] . In some instances, the last federated post is 2 weeks past and on lemmy.world it’s 8 days (https://lemmy.world/c/[email protected])
super frustrating from a community building perspective. no point in lemmy.ml folks joining [email protected] if no post ever actually show up for them.
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: [email protected]
I mean, I’m noticing the same thing between kbin.social and lemmy.world. There was a post I wanted to see through kbin.social from lemmy.world and couldn’t.
yeah, definitely see it with kbin, but I was chocking that up to “early days”, but I assumed Lemmy-to-Lemmy federation was not an issue.
I wonder if this has something to do with the Activity Pub Protocol? But then again I don’t think I have ever heard of any issues like this on Mastodon, or any other fediverse instance that uses Activity Pub.
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.
