Well, it was worth a try, but I think Kbin isn’t working out for me I’m going to close kayb.ee down in the near future.
I know the developer has had other stuff to deal with, but sadly there’s no momentum in the project, there have been no changes to the code in over a month, and radio silence from the developer in the same time.
I started worrying about the state of Kbin a while back and closed registrations, as I worried that more users would mean more people to disappoint if I had to close this site down.
As it stands we have a handful of active users, so my plan is to close down at the very end of February giving them a few weeks’ warning.
I’d have been quite happy to keep kayb.ee running on the side if some of the issues were resolved, but I’ve never managed to get S3 object storage working with kbin despite numerous attempts, and it still chews through a huge amount of CPU as the worker processes keep restarting.
This means that the dedicated server I have this running on is using masses of local disk space for media caching, and a huge amount of CPU just to run kbin. It’s sadly just not sustainable.
So with that in mind I’ll look to close down kayb.ee on the weekend of 30/31 March. Hopefully that will give our few active users time to make alternative arrangements. And sorry for letting you down, it’s not a decision I’ve taken lightly, but I feel it’s the right thing to do given the state of the Kbin ecosystem.
@buzz Sad but understandable choice, once again thanks for giving it a shot. It was fun while it lasted.
@Essence_of_Meh You’re very welcome! I hope that gives you enough time to get set up somewhere else.
@buzz Yup, should be more than enough. I already have backup accounts on some Mbin instances, just need to test which ones federate with everything I need since I didn’t really use them.