- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
cross-posted from: https://lemmy.wtf/post/56006
Any idea why federation is not working between that instance and this one?
It’s getting better. @[email protected] recently changed a setting in the
nginx_internal.conf
onlemmy.wtf
(suggested herer) and we are now able to subscribe in both direction, I think.Not all older posts/comments are automatically federated, but you can manually “pull” them over by searching for the full source URL on the destination instance. Which I do from time to time.
My comment actually showed up on Kbin.social immediatly!
That’s awesome, thanks to you both :)
But it looks like
kbin.social
isn’t federating (pushing/forwarding) comments which they received from us (lemmy.wtf
) to other instances (e. g.lemmy.world
) which have subscribed to their magazine, too. Or at least this takes very long.
Also, I found this comment, though I don’t know whether this is (still) true:
- https://kbin.social/m/kbinMeta/t/132893/Some-of-my-posts-and-comments-are-not-showing-up#entry-comment-519843
- https://lemmy.wtf/comment/215978
In order to catch up with a massive queue backlog a temporary hold on delivery to domains that are being problematic has been setup. Those other domains aren’t responding to kbin.social’s requests properly and so our own queues are getting backed up.
It’ll all be back to normal soon. Once the queues are sensible we can reenable domains as they start becoming responsive to us.