Hi all, so it has been a couple weeks since the initial launch of kbin.run and I'm curious to hear what people's opinions are and how they like the overall experience here vs. other kbin instances. Generally speaking, I think kbin's stability has greatly improved since launch as the first turn on was a very haphazard attempt at getting an instance going using very limited documentation to configure all the interconnected services. There are still a couple of hacks in place to keep federation working smoothly, but I do anticipate official code changes in the near future will greatly improve the overall kbin experience.
I honestly don't know how many people actively utilize kbin.run, but I do see we have 56 registered users (2 pending deletion) as of posting this thread. The primary server that runs the site is hardly breaking a sweat, so tell your friends to join us if they're looking for a lightly loaded instance.
Also, if you're searching for a community that seems to be missing in the fediverse, feel free to create a magazine to support it here. I made a few that I'm interested to see gain some momentum, but there's nothing stopping anyone else from doing the same.
Thanks as always and enjoy!
EDIT: I've added the monthly cost breakdown for kbin.run to the FAQ page.
Hello @debounced, I hope you're going well :)
I just found the site linked as a Kbin alternative with more updates/fixes. So far it looks great!
However, I noticed I can't access some federated communities from the site, like https://kbin.run/m/[email protected] . Here's the Kbin.social view for comparison. This magazine doesn't show up in the magazine search for Kbin.run, either.
I checked the federation page and it does look like Kbin.run federates with that instance, but the individual magazines are not loaded. This occurs for a few other instances as well, both Lemmy and Kbin. I'm not quite sure why.
hi! i'm doing well and thanks for joining kbin.run - now powered by mbin!
i just checked out the community you mentioned and as far as i can tell no other registered user on kbin.run has previously searched for that specific magazine (until now)... and I'm also seeing timeouts and/or errors when I try to browse the origin server at https://wayfarershaven.eu/c/fountainpens. if the origin server is having difficulties or is being too slow, kbin/mbin will sometimes give up and retry later to pull in federated content. be aware that you won't get any of the prior threads/posts as of the date the community gets federated, so you'll only see new content once the federation is successful. hopefully that makes sense, but you might want to retry later once the origin server stops throwing errors.
Thank you for writing back so quickly!
It looks like it's all working now, and I can access each magazine by typing its full name into https://kbin.run/search.
I am getting the same odd redirect behaviour mentioned here, but that's pretty harmless.
FYI, the redirect bug should be resolved now. I finally got the motivation to go through the code and figure out why this was happening. https://github.com/MbinOrg/mbin/issues/35#issuecomment-1765265593
Thank you very much! I subscribed to a few more communities and haven't seen the bug since.
Glad to hear it resolved itself!
I created a GitHub issue for that redirect bug since I think it's related to this being a "bare metal" install and not docker as I can't seem to replicate the issue in my docker dev environment, but I haven't spent too much time digging into it. We'll see if someone else solves it before I do, but I think it might be a Nginx config issue with the recent API addition... TBD.