As the lemmy.ca community has been growing, I’ve begun to look at some of your /c/communities and … things are bugged. I can’t really post or comment very well on my https://lemmy.world account.
So I created this local https://lemmy.ca account to maybe bring attention to this federation problem.
I’m not sure if this is due to the growth of https://lemmy.world, or some configuration issue on the backend. But I figure that tracking and testing my account access from both sides can help everyone get to the bottom of this.
Case in point: https://lemmy.world/comment/668202
This comment here, I made it from https://lemmy.world. And… its not here yet on the lemmy.ca side! The https://lemmy.world thinks that the post is getting transferred over, but… there’s a bug. Something seems to be stopping my post from coming over.
On this subject: the https://lemmy.world administrators have been investigating the federation issue on their end (see: https://lemmy.world/post/818810). Note that https://lemmy.world is still on version 0.17.4.
I’m wondering if the problem could be on the https://lemmy.ca end as well, or a bug in 0.18.0. In either case, I felt the need to report this federation-bug.
I know that various lemmy-administrators have been forced to tweak worker-settings and play around with timeouts to get federation working correctly (or at least, working better). The default settings are simply not workable, not with the #RedditBlackout growth upon this corner of the Fediverse.
There are known federation issues with 0.18.0 that are supposed to be fixed in 0.18.1. We’ll be upgrading this weekend hopefully.