Status update July 4th

Just wanted to let you know where we are with Lemmy.world.

Issues

As you might have noticed, things still won’t work as desired… we see several issues:

Performance

  • Loading is mostly OK, but sometimes things take forever
  • We (and you) see many 502 errors, resulting in empty pages etc.
  • System load: The server is roughly at 60% cpu usage and around 25GB RAM usage. (That is, if we restart Lemmy every 30 minutes. Else memory will go to 100%)

Bugs

  • Replying to a DM doesn’t seem to work. When hitting reply, you get a box with the original message which you can edit and save (which does nothing)
  • 2FA seems to be a problem for many people. It doesn’t always work as expected.

Troubleshooting

We have many people helping us, with (site) moderation, sysadmin, troubleshooting, advise etc. There currently are 25 people in our Discord, including admins of other servers. In the Sysadmin channel we are with 8 people. We do troubleshooting sessions with these, and sometimes others. One of the Lemmy devs, @nutomic@lemmy.ml is also helping with current issues.

So, all is not yet running smoothly as we hoped, but with all this help we’ll surely get there! Also thank you all for the donations, this helps giving the possibility to use the hardware and tools needed to keep Lemmy.world running!

  • randon31415@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    The redirects to baseball games glitch is gone. I am unsure if this is because the glitch is fixed or if baseball season is over.

    • headie_sage@fanaticus.social
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      😆 sorry about that! Baseball season is still very much on.

      This issue was caused by the websockets replacing the current thread you were on with newly updated or created posts. Our game threads get updated frequently so they were constantly popping up in people’s faces. We decreased the frequency of the updates pretty substantially in order to be less annoying to unrelated instances but it was still happening occasionally.

      Now that we’re all through with websockets it won’t be an issue anymore!