Kbin Blog Updates

Yes you heard that right, we are planning for the first /kbin release. Currently most server admins are running directly from the develop branch since /kbin is still in very (early) active development.

That being said, we are planning for creating the first tagged released of /kbin! We still merge several pull requests, but holding off a bit. At the same time we are looking at all the high priority issues, seeing if some of those can be resolved or mitigated before the first tagged version.

I already introduced some basic CI/CD Workflow Actions within Codeberg. Also Ernest setup several development environments. All these preparations are necessary to achieve a better, faster and more stable release cycle in the near future.

Thanks to all contributors and of course @ernest and @piotrsikora. Thank you all for this wonderful community and becoming part of it.

~Melroy

Currently, the kbin.social instance has planned maintenance. They are busy upgrading the infrastructure to Kubernetes, using Docker containers. They said it shouldn't take much longer than 1 hour downtime in total (if everything goes fine).

The migration will help to dynamically scale the instance, to remove the growing pains. And hopefully increase the availability (uptime) as well.

Soon additional setup configurations, best server practices and ansible playbooks will be shared with the community.

In the meanwhile you can of course use other instances (I bet you are reading this message right now from another instance).

Today kbin.social is blocking a huge list of domains just to get federation working again.

The reason for this temporally block is not to defederate, but rather to get the large backlog of 500k messenger queue processed again. Anyway, this does mean that kbin.social is federating again with other instances.

This is a temporary measure. Several users / developers are looking into how to better optimize the failed message queue, as we speak. Hopefully Ernest has eventually time to dive into solutions as well instead of workarounds, once his instance is migrated to Kubernets. See my preview thread: https://kbin.melroy.org/m/updates/t/4257/Kbin-federation-issues-and-infra-upgrade

List of the domains causing trouble:

lemmygrad.ml, eientei.org, vive.im, lemmy.ml, lemmynsfw.com, kbin.lol, lemmy.webgirand.eu, tuna.cat, posta.no, lemmy.atay.dev, sh.itjust.works, kbin.stuffie.club, kbin.dssc.io, bolha.social, dataterm.digital, kbindev.lerman-development.com, test.fedia.io, mer.thekittysays.icu, lemmy.stark-enterprise.net, kbin.rocks, kbin.cocopoops.com, kbin.lgbt, lemmy.deev.io, lemmy.lucaslower.com, lemmy.norbz.org, social.jrruethe.info, digitalgoblin.uk, pwzle.com, lemmy.friheter.com, federated.ninja, lemmy.shtuf.eu, u.fail, arathe.net, lemmy.click, thekittysays.icu, lemmy.ubergeek77.chat, lemmy.maatwo.com, faux.moe, eslemmy.es, seriously.iamincredibly.gay, test.dataharvest.social, programming.dev, kbin.knocknet.net, pawb.social, lucitt.social, longley.ws, kbin.dentora.social, atay.dev, lemmy.kozow.com, ck.altsoshl.com, pawoo.net, techy.news, lemmy.vergaberecht-kanzlei.de, lemmyonline.com, beehaw.org, pouet.chapril.org, kbin.pcft.eu, fl0w.cc, lemmy.sdf.org, lemmy.zip, feddit.dk, fedi.shadowtoot.world, lemmy.noogs.me, lemmy.kemomimi.fans, social.agnitum.co.uk, fediverse.boo, hive.atlanten.se, forkk.me, lemmy.ghostplanet.org, lemmy.mayes.io, lemmy.mats.ooo, lemmy.world, lemmy.sdfeu.org, lemmy.death916.xyz, geddit.social, masto.fediv.eu

Don't forget you can change the look & feel of kbin. Go to the setting (gear icon) menu. And try out all the options.

Adapt the settings to your preferences!