Comment on Lemmy.world no longer federating with Kbin? If yes, why??
justlookingfordragon@lemmy.world 6 months ago…and zero users per week, which is wrong even when viewed from “this side” of the Fediverse, as many people have clicked that link by now. Hm. Seems like it is not “just” a federation issue when the Lemmy.world version of the magazine doesn’t even count visitors ON Lemmy.world properly.
tun@lemm.ee 6 months ago
When I link to cars magazine from lemmy it should be kbin.social/m/cars but appeared as kbin.social/c/cars which does not exists.
Other Redditmigration and breathofthewild links do not have this problem.
justlookingfordragon@lemmy.world 6 months ago
The “proper” way to link magazines from lemmy would be lemmy.world/c/cars@kbin.social - this is supposed to fetch a clone of the kbin magazine but display it in the lemmy.world UI. Using a “c” is correct here, but something still doesn’t work properly for this particular instance.
If you write it as kbin.social/m/cars, then you’re directed to the original magazine with the kbin UI.
The same works the other way around too: lemmy.world/c/support will open the support-community on lemmy.world in its original state, and kbin.social/m/support@lemmy.world will open the LW-support community clone as a magazine on kbin, with the kbin UI. (you might need to copypaste that last link instead of clicking it, as LW seems to “fix” the link by automatically converting it into lemmy.world/c/support@lemmy.world )
Long story short, the c/w thing is not the issue as it works for other communities and magazines just fine. Still, somehow the content in this case doesn’t federate properly … maybe someone who can take a look at the actual code might have an idea why? I mean, sooner or later this needs to be fixed. The magazines listed in the original comment are surely not the only ones that are affected, and any magazine that looks dead and abandoned from this side of the Fediverse, is a magazine that won’t gain any subscribers, posts and comments FROM this side of the Fediverse, defeating the idea behind Federation. It slows down growth.
CommunityLinkFixer@lemmings.world [bot] 6 months ago
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !support@lemmy.world
tun@lemm.ee 6 months ago
Lemmy server did what I said.
When I use !cars@kbin.social the link produced by Lemmy is not correct.
When I use !breathofthewild@kbin.social the link produced by Lemmy is correct.
justlookingfordragon@lemmy.world 6 months ago
Ah dang … I forgot to factor in that we’re on different instances. For me, a Lemmy.World user, the !cars@kbin.social link creates the correct link (lemmy.world/c/cars@kbin.social) but since those exclamation-mark-links create different types of links for different instances, it does not mean that all users get the correct link that way. Apologies, that was my mistake.
Maybe that formatting error is what prevents the magazine from federating properly. The instance creates a link that leads nowhere and therefore doesn’t know from where to fetch the content, so the magazine clone on other instances stays empty.