theinspectorst

By far the biggest issue at the moment is that fedia.io isn’t federated with kbin.social, which is by far the biggest kbin instance. That issue is on their side, but the guy who runs it posted an update today indicating a solution is on its way:

Good morning! :) Today I want to focus mainly on reviewing the pull requests you’ve submitted. There are many great things there that will help improve the kbin experience. That’s amazing, thank you! I’m also in the final stages of sorting out the infrastructure-related formalities. Soon, the situation with the website’s functionality should stabilize, and the traffic from the fediverse will gradually be restored. I’ve decided to delegate some tasks as I can no longer oversee everything at this stage. There are many offers of help for which I’m very grateful, and I haven’t had a chance to respond to some of them yet because I only just saw them - a lot is happening, really.

The key question for me is what do ‘soon’ and ‘gradually’ mean here. If it’s all sorted within the next couple of days, I’ll ride it out here. If it’s longer, given the enormous growth they’ve seen over there and the content we here are therefore missing out on, I may start using kbin.social as my primary unless/until I’ve got confidence that fedia.io is sustainably integrated with the rest of kbin (and to be honest there’ll be some path dependency there - if I start using kbin.social as my primary then there’s a good chance I’ll not get around to coming back…)

I’m having the same problem. This needs sorting out quickly as it’s completely defeating the point of a federated model - kbin.social is the biggest Kbin instance and if we can’t see its magazines from other instances then they’re encouraging everyone to just sign up there instead - which they don’t seem able to accommodate anyway…