I didn’t really wanna write about this. But there we go anyway now.

Yesterday the problems started to occur with the media.kbin.social domain issues with an expired TLS certificate. Causing problems with thumbnails and other media on the main instance.

Now the kbin.social domain instance seems to be fully down. Might be related to the TLS certificate issue or planned maintenance?, that is anybody’s guess.

Nobody from Ernest to Piotr are responding or seem to be present to resolve the actual problem(s). This affects thousands of people on that instance and damaging the /kbin brand as a whole. I think it’s unacceptable. I hope people will not migrate towards Lemmy. I do hope if users want to migrate, they migrate to other kbin instances. Spreading the load and users across several instances is never a bad idea anyway. Making it more decentralized in the process.

I have wanted to discuss these issues several times before about how we deal with sustainable software development at kbin and recently also the main instance (kbin.social). The the focus on long term and on continuity of the project as a whole.

We may have now reached the bottom, and hopefully (some) people will realize that things can and should be better.

I do like kbin and all the developers/contributors. I do not want to see it disappear. My hope is that changes will happen rather sooner than later.

~End of my story

  • Bradley_@kbin.melroy.org
    2·
    9 months ago

    I am really worried that the whole platform may grind to a halt because of sume trivial issue like the two we had in the last 24hours… The community has great conceptual potential, but if there isnt a team of developers ready to adress basic technicalities, it simply wont work.

  • vintprox@kbin.melroy.org
    2·
    9 months ago

    No way I’m switching to scatterbrained Lemmy just because of people depending on kbin.social instance and hailing centralization. But it’s certainly concerning that even close contributors cannot contact each other regarding such emergencies.

    I think, if we’re going forward with Kbin, there needs to be some agreement on the urgency types for maintainers. Imagine making a tier list of all things that Kbin lacks: what few things would be in an S-tier - well, NEVERMIND, because this big library of images won’t show the signs of life, let alone an unplanned downtime of Big Daddy™ server.

    As expected, this post has triggered few drama queens in the comments. Anyway, glad to hear from you, even though this particular issue couldn’t affect me by a long shot, haha.

  • Zeppo@sh.itjust.worksEnglish
    0·
    9 months ago

    I think it’s just down for maintenance.

    I suppose I’d add that I also wonder about the sustainability of a project that costs money and the effort of a fulltime job, but probably doesn’t pay like a fulltime job.