This post suggests that Kbin magazines can be subscribed to in the same way as Lemmy communities, by searching for them, possibly waiting for one’s instance to pull info about the magazine in, and then visiting the magazine through one’s instance. However, although my home instance is federated with kbin.social, I am not able to get any search results for kbin.social magazines, and it seems that I am not the only one; see here, here, and here, though that last case seems to have fixed itself on its own. The behavior is the same whether I search by URL (e.g., https://kbin.social/m/fediverse), by magazine name with an at-sign (e.g., @fediverse@kbin.social), or by magazine name with a bang (e.g., !fediverse@kbin.social).
I’ve been having this same issue and it just seems to be hit or miss. TBH I think it may be because kbin and even some lemmy servers are getting absolutely hammered right now. Sometimes I can search for a kbin “magazine” on lemmy and it finds it, but most times not.
As I’m writing this, i’m trying to test and kbin is actually down at the moment. I think the reddit wave is just affecting things.
TBH I think it may be because kbin and even some lemmy servers are getting absolutely hammered right now.
This may be it. kbin.social was outright down a bit earlier, and now I get a captcha page. Perhaps the ActivityPub stuff gets a captcha too, which obviously would break it. I guess I’ll try again another time.
Yeah kbin’s developer says his ddos counter-measures affects federation: https://kbin.social/m/kbinMeta/t/10415
I’ve been trying to do the same today. I think it’s more likely that your instance is blocking access to kbin altogether or specific magazines. For example, I have both a beehaw.org and lemmy.world account. I can access https://beehaw.org/c/kbinmeta@kbin.social and can subscribe from that page but https://lemmy.world/c/kbinmeta@kbin.social returns a 404: couldnt_find_community error.
The reason I think it might be instance specific versus, say a bug in the server version, is because https://lemmy.ml/c/kbinmeta@kbin.social and https://beehaw.org/c/nsfw@kbin.social both work and but https://lemmy.ml/c/nsfw@kbin.social doesn’t work. Presumably lemmy.ml is blocking the nsfw magazine.
Update courtesy of @chaorace@lemmy.sdf.org: kbin.social has enabled DDOS protections that “may cause some issues with the federation”. They will return to normal operation when possible.
Was reading about this earlier, in theory they are fully compatible but Kbin’s implementation is better.
I was unable to successfully subscribe to the same magazine as you tried.
You linked my comment but yeah, I did eventually see that https://partizle.com/instances shows kbin.social as federated for my instance
@nodester@partizle.com do you know why?
I believe they’re at least partially interoperable. Once someone subscribes to a community on another instance, it shows up in your home instances list.
It sure would be nice if kbins documentation was good enough to generate a functional instance. Might take some of the load off.
I have been able to get kbin magazines show up but they don’t show posts and I can’t subscribe. Seems like something lemmy needs to fix.
I’m trying to figure how to do the opposite but can’t seem to figure it out either.
