This is probably related to my post from a few days ago: https://kbin.social/m/kbinMeta/t/131241/What-s-up-with-The-magazine-from-the-federated-server-may
New Lemmy version doesn't federate outbound with non-Lemmy instances anymore (issue from GitHub)
https://github.com/LemmyNet/lemmy/issues/3354
6 Comments
Alexmitter@kbin.social · 12 pts · 3y
Actually there is now a fix, https://github.com/LemmyNet/lemmy-ansible/pull/114
But it seems that instances that update to the latest RC do not just automatically get that fix into their nginx config. I have worked with a instance owner and he had to, despite updating, manually update the config. After that federation worked again.
Treedrake@kbin.social · 2 pts · 3y
Ah. Thanks for the update! Hope it resolves
Pamasich@kbin.social · 3 pts · 3y
Isn't this fixed in 0.18.1 iirc?
Treedrake@kbin.social · 3 pts · 3y
It continues to be a problem as far as I can see
roofuskit@kbin.social · 3 pts · 3y
That's already and old version.
fearout@kbin.social · 3 pts · 3y
Using Memmy, I see all kbin communities as empty, even though I subscribed to them using a Lemmy account and there have been posts since.
Is that a thing that’s going to be fixed in the future, or did Lemmy decide to partially defederate from kbin and all is working as intended?
I really don’t get current Lemmy—kbin relationship and what to expect in the future.