Good morning,

Some of you may have experienced a small hiccup this morning (eastern time). I went ahead and upgraded our lemmy instance to 0.17.4. I also took this opportunity to make some small adjustments to the instance that required a restart of services. These changes were mainly related to increasing Federation worker count in hopes to decrease synchronization times with other instances. A small fix to help slow down the storage growth was also applied (limiting log sizes that get generated).

Everything should be back up now. In the future my goal is to be more transparent with scheduling downtime.

edit: updated link

  • @mikehuntEnglish
    26•2 years ago

    Keep up the good work eh!

  • @[email protected]English
    20•2 years ago

    Cat pics arent loading fast enough…

    Please post donation link so we can upgrade the server!

    Thanks for your hard work!

  • @[email protected]English
    19•2 years ago

    Thanks for your effort. I really have to say the performance here is very good compared to other instances (tried two others before I landed here). Shit just works.

  • Ram_ZeEnglish
    16•2 years ago

    Thanks for your hard work! It’s greatly appreciated.

  • @[email protected]English
    13•2 years ago

    Are you sure that’s the right link for the version? That changelog only goes to 0.17.2, 4 months ago. Wanted to see what changed.

      • @[email protected]English
        12•2 years ago

        Thanks! Ah, so this is just a DB optimization patch. From the sounds of that changelog, all the big stuff is coming down the pipe in the next version. Presumably that’s when they’re finally turning off WebSockets.

        • @[email protected]OPMEnglish
          11•2 years ago

          I believe the devs were saying that they were moving away from websockets in v0.18.0 which is scheduled to come out in a few weeks

    • @[email protected]OPMEnglish
      9•2 years ago

      The security fixes were documented prior and manually applied on our old instance as well. This patch was to get the performance gains and align with the latest release!

  • DekthroEnglish
    5•2 years ago

    Thanks for the all the hard work. Keep it up, so proud to be apart of this growing new community!

  • @[email protected]English
    4•2 years ago

    Unclear if this happened since this patch or it was like this, but I am unable to log in on desktop. My Android app works fine, but on desktop, if I go to the login page then click login, the thing spins forever without any error message regardless of if my credentials are correct.

    Edit: this doesn’t happen on blahaj.zone which runs 17.2. edit2: either you did something or it fixed itself.

    • OtterEnglish
      1•2 years ago

      I was getting that on a different one earlier, resetting my password fixed it for me.

      Looks like yours is fixed already, but if someone else comes across this that’s worth a try

  • synacksyn
    2•2 years ago

    Thank you! Can you confirm that we are having federation issues? I cannot seem to locate magazines on other instances. I just wanted to make sure its not just me doing something wrong.

    • UsualMap
      1•2 years ago

      As I understand it, part of the issue on kbin is that the default federation threads value is too low for large sized instances.

      I gather this will improve over time.