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.

  • Nominel@kbin.run
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    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.

    • debounced@kbin.runOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      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.

      • Nominel@kbin.run
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Thank you very much! I subscribed to a few more communities and haven’t seen the bug since.