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.

  • debounced@kbin.runOP
    2·
    1 year ago

    hi! i’m happy to hear things are working well for you here, i’ll do my best to keep it that way. :-)

    i think the issues you’re describing sound like “normal” federation delays between this instance and the origin instances where the content is being generated. there shouldn’t be any real delay in viewing content that is generated locally other than database transaction times, which are typically super small, but anything that needs to get sucked in from other instances won’t show up until the origin server decides to push it out. federation can also be a super lossy process if things get overloaded, i.e., i’ve seen things backdated from weeks ago that all of a sudden show up here once the origin server decides to sent it again.

    however, this instance/server is hardly being taxed at all… in my limited testing, stuff that is generated here is federated almost immediately. if you find a situation where things aren’t coming thru in a reasonable time, let me know and i’ll investigate it further to verify it’s not something on my end. it’s also entirely possible that the larger instances have more user engagement with federated activity causing more frequent updates than what is currently happening here… so things may speed up the more active this instance becomes.

    my goal is to continue running this instance for as long as possible… mainly because i want to use it (lol), but i also plan to post a detailed “invoice” of how much it costs to run even this small instance just like @ernest did for the mothership’s infrastructure… i’ll either put it under the About or FAQ page, haven’t decided yet. if “we” as a kbin.run community agree that it makes sense to either scale up or scale down, i’m willing to do anything reasonable.

    • Pat@kbin.run
      2·
      1 year ago

      Awesome. I’m excited to see how this instance evolves as the overall threadiverse grows. I’ll be calling this my home in the fediverse for the foreseeable future