I’m wondering as a relative fediverse noob - are there any known issues when federating with lemmy.world?
I ask because I run a They Might Be Giants community there that I created with an alt account and moderate with my account on this instance, in part because as giant as they may be, I feel like a They Might Giants community doesn’t fit this instance (if I am wrong, might consider migrating it).
I made a post ~14 hours ago and it still hasn’t shown up on other instances. I’m guessing it’s either lemmy.world is a ginormous instance or it’s still on 19.3. I just find it weird because I’ve made posts without problems before.
Anyhow, glory to the admins of this instance; they honor their houses.
We (and other instances) do tend to have issues with lemmy.world from time to time - I think it’s a combination of their sheer size, and some geographical quirks that can slow things down.
Right now, it looks like federation from them to us is fine, but content from us to them is taking about 19 hours to go through.
I can look into this, but there’s a high chance that we’ll have to just wait for it to settle down.
On another note, it looks like federation should be sped up in this commit, which is in the recently-released version 0.19.6 (and 0.19.7, which has come out since). I would think lemmy.world would have to upgraded as well, though.
Yeah, I have no idea how that stuff will work if instances are running different versions.
Federation is an imperfect thing, but hopefully we’ll get this sorted soon enough.
A couple of weeks ago, federation from .world fell behind by about 3 days if you can believe it.
Good news - after getting real bad today (okay, that part’s not good news), it looks like we’ve fixed federation with lemmy.world and a number of other instances. Things should be within normal parameters.
More specifically, federation from us to lemmy.world has a delay of about 57 seconds, while federation from lemmy.world to us is about 1.7 hours (this is admittedly not ideal, but also not that unusual).
We suspect this may have to do with their older Lemmy version as we’re noticing it on some other instances as well, but not .ml which is running the latest.
