Is this only some kbin instances thing or all kbin instances thing? I’m fairly sure that fedia.io (/kbin instance) does not use cloudflare. But that would definitely explain why I’m struggling to search some instances that might use it.
Here’s a list I used to find kbin.run, it’s a little barebones right now but the UI is really familiar as someone who used Reddit a lot. It is mostly centralized to kbin.social right now, as more instances pop up and the main instance fixes federation it should sort itself out as long as it keeps momentum.
kbin being more centralized is just an unfortunate accident of timing. I was only first publicly released two months ago, and from what I understand there’s still not much help available for starting up a new instance of your own, and the lone developer over there has been busy trying not to let the kbin.social server catch fire.
Is this only some kbin instances thing or all kbin instances thing? I’m fairly sure that fedia.io (/kbin instance) does not use cloudflare. But that would definitely explain why I’m struggling to search some instances that might use it.
As far as i’m aware it’s only the main kbin instance.
but (as far as i can tell) kbin is way more centralized than lemmy, so it has a large effect
It’s not at all, they’re just having tech issues right now.
ah. do you know where i can find a list of all the kbin instances?
https://kbin.fediverse.observer/list
Here’s a list I used to find kbin.run, it’s a little barebones right now but the UI is really familiar as someone who used Reddit a lot. It is mostly centralized to kbin.social right now, as more instances pop up and the main instance fixes federation it should sort itself out as long as it keeps momentum.
am I misreading that, or was I right that they’re way more centralized? I only see a few instances there?
kbin being more centralized is just an unfortunate accident of timing. I was only first publicly released two months ago, and from what I understand there’s still not much help available for starting up a new instance of your own, and the lone developer over there has been busy trying not to let the kbin.social server catch fire.
Reading this from fedia right now