Things have been incredibly unstable there. Until things stabilise, they should force the traffic elsewhere.

  • Kecessa@sh.itjust.works
    link
    fedilink
    arrow-up
    16
    arrow-down
    4
    ·
    1 year ago

    What?

    People can subscribe to other instances or even host their own. If the majority of users end up on the same instance then what’s the point of decentralization? Even worse if the traffic it generates for that instance makes it unstable.

    Should the admin do nothing until the instance is mostly down with windows of uptime throughout the day?

    • RoundSparrow
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      A big part of the problem is that a new instance starts with zero database content and PostgreSQL performs fine with the way Lemmy organizes the data. But then there isn’t anything for people to read, and search is only going to pick up local stuff.

      • Kecessa@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 year ago

        There’s no perfect solution but I certainly didn’t move to a decentralized platform only to see it be intentionally centralized through inaction.

        • RoundSparrow
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          The quantity of users on Lemmy I still consider to be pretty low, the performance bugs need to be addressed on a big server. Bugs like not having a WHERE clause on an UPDATE hitting 1500 rows in a table (one row per server) instead of 1 single row… these need to be shaken out.

          The errors of the overload themselves have been a way to throttle growth of the big servers. People were not able to insert new posts and comments into Lemmy.ml - reducing outbound federation activity too, and they went to other servers. This went on all of June and July.