Looking at incoming request. .world is working OK for me. They seem to be batching stuff like I'll get nothing for 30 seconds, then over 3 seconds like 50+ requests.

Of course I don't know if their queue is backed up and I'm getting delayed stuff. I'd need to stop processing and look into the incoming queue to see what they're sending.

Bit of an edit. Looking at incoming again I can see under newest items, an entry from world that was 11 minutes old. Oh I have an idea. I'll see if this edit gets there in a timely manner.

Spoiler alert, it was instant.

Oh ignore me. It's specifically between those two instances I guess.

[–] muntedcrocodile@lemm.ee 3 points 3 weeks ago (1 children)

Aparently its between big instances and lemm.ee only. All of said instances use cloudflair. I suspect that cloudflair has blocked/rate limited the larger instances from reaching lemm.ee.

[–] r00ty@kbin.life 3 points 3 weeks ago (1 children)

I think it must be hit/miss. Because I think those edits I made would have gone from my instance to world and then from world to .ee, and it was happening within seconds.

So, presumably random stuff is being dropped or delayed?

[–] muntedcrocodile@lemm.ee 0 points 3 weeks ago

Yeah ur right. Everything going on here must go through .world as it is the community. Which makes it even weirder that we dont have .world users federaring out.

My understanding of federation is ur events get sent to ur instance (kbin.life) ur instance sends those events to the instance of the relevent community (lemmy.world) the instance of the community sends that event to all instances subscribed to that community (lemm.ee, kbin.life, etc) my instance receives that event then notified me.

So this conversion is goibg through .world just that .world users events seem not to be gettibg sent to .ee

I think we need someone smarter than both of us to fix this