Hey! A kbin user here, just logged in to my lemmy.world dummy account to ask this, I’ve noticed communities like m/AskKbin, m/Cars, M/RedditMigration and etc are not federating at all with Kbin anymore, I am not sure if this is just an issue from my side, a bug or did lemmy.world mods really decide to not federate with Kbin??
EDIT: Just saw another official post from the admins here 3 months back, so looks like it is partially defederated as in Lemmy.world from one side can’t see Kbin’s communities thanks to the spam issue a while back?
To mention, the spam issue is no longer a problem afaik, and Kbin has since brought built-in mod request system, allowing inactive communities to be requested by new moderators similar to reddit request, this has helped a lot and ever since many of the “used to be spam with inactive mods” is no longer an issue as new mods have since started requesting and taking over those communities.
Ie; One of the biggest Kbin communities: m/RedditMigration, was a community that had an inactive mod and a flow of spam, I was able to takeover and place ban on the spammers and bring back the peace. We were able to make a ton of progress in the past month, placing new rules and soon, we will be recruiting even more mods to keep up the quality-control.
So I do hope lemmy.world can reinstate full federation between both platforms, allowing users from here to see communities there as well.
EDIT: Also Kbin.social’s admins, is Ernest who is also the developer of Kbin itself, when lemmy.world admins decided to hide Kbin communities about 3 months ago, Ernest was facing private issues in his life but ever since then development resumed from being paused and bot spam has been addressed apart from the mod request system that has also been helping. Considering it’s been months and it’s now no longer as the issue it was months ago, I do hope the admins here can bring back the connection between both instances.
The “proper” way to link magazines from lemmy would be https://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 https://kbin.social/m/cars, then you’re directed to the original magazine with the kbin UI.
The same works the other way around too: https://lemmy.world/c/support will open the support-community on lemmy.world in its original state, and https://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 https://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.
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
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.
Please see the screenshot and note the URLs
Edit: happened yesterday. Not happening now. Both links produced incorrect url.
Edit 2: your reply in the screenshot.
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 (https://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.