Good morning! :) Today I want to focus mainly on reviewing the pull requests you’ve submitted. There are many great things there that will help improve the kbin experience. That’s amazing, thank you! I’m also in the final stages of sorting out the infrastructure-related formalities. Soon, the situation with the website’s functionality should stabilize, and the traffic from the fediverse will gradually be restored. I’ve decided to delegate some tasks as I can no longer oversee everything at this stage. There are many offers of help for which I’m very grateful, and I haven’t had a chance to respond to some of them yet because I only just saw them - a lot is happening, really.

As I mentioned before, new possibilities have emerged that I couldn’t have imagined before. All of this is thanks to your support; you are incredible, and I thank you. That’s why it’s crucial for me to ensure transparency in everything we do and provide regular reports. I want to share as much information behind the scenes as possible. That’s why it may seem like it’s taking a long time, but I truly want to make the most of every cent.

Now, onto the bad news. I messed up.

The workload overwhelmed me, and I couldn’t read all your messages. I will diligently work my way through them, but I need time.

The registration system is far from perfect, so from time to time, I manually verify and activate accounts whose activation links didn’t arrive. Please check again later if you find yourself in such a situation.

The queue for account deletions is stuck. Manual fix is needed, which will be difficult until the infrastructure is moved. I have recorded all 230 account deleiton requests, and each one will definitely be deleted, but I also need time for that. I apologize for this. If someone wants their account to be immediately deleted, please send an email through the contact form starting with “DELETE MY ACCOUNT” - it will be easier for me to filter it out, and I will delete the account manually.

That’s all from me. I’m going back to stirring the cauldron. Thank you for all the messages and kind words. Thank you for being here. Have a nice day!

  • stickerface@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Just found this site - definitely going to be putting an effort in to getting the formula1 kbin populated.

  • Chuck-of-the-North@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    @ernest Please hang in there and take a breath. This site is amazing quality for a beta given the insane traffic coming over from the /r debacle. Pace yourself. Development and testing is a marathon, not a sprint (no pun intended).

    I hope the many new arrivals (like me) appreciate how far kbin has come so quickly. /r wasn’t solid for quite a while.

  • tal@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Suggestion: If you have work that can reasonably be farmed out, you might try writing up a list of what you need people for and asking for any volunteers and setting up something to let them handle some of the load.

    I don’t know whether that will work, but just doing reviews of pull requests on GitHub for a new project expanding rapidly may be a full-time effort for someone, much less all this other stuff.

    • VerifiablyMrWonka@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      He’s apparently found some people to help with the infra side of things - which is the hardest thing to do. This means more focus on improving the product. :D

    • delawen@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      From experience escalating other projects, he’s probably at the stage where the urgent (the site collapsing) is done before the important (delegating tasks). If he stops to delegate tasks, the normal functioning of the site will collapse.

      Anyone who wants to volunteer and don’t know where to start can start by going to the currently opened PR and reviewing them, testing them, improving them. Of course @ernest will have to review them afterwards. But if three independent developers say they already tested and reviewed and reported the potential mistakes, that makes his life much much easier.