• Ghostalmedia
    link
    English
    201 year ago

    The log in and voting issues aren’t because it’s dying, they were because of scaling issues and DDOS attacks because Lemmy is now a visible / popular target.

    This stuff is pretty normal for a new upstart service that is becoming popular. This feels like Reddit’s early days.

    • @bighi
      link
      English
      01 year ago

      Whatever the reason it’s happening, it’s happening. And has been happening for weeks.

      Even if a bad experience has a reason, a bad experience is a bad experience.

      • Ghostalmedia
        link
        English
        91 year ago

        Growing pains from being popular. It will get sorted out. Same thing happened to Twitter and Reddit in its early days.

        A lot of the early adopters here are millennial and gen X folks who adopted other stuff early in the past, and they have a nostalgia for the growing pains of a new platform.

        That said, you may want to check back in a few weeks when a defense for the DDOS shit has been figured out.

        • @[email protected]
          link
          fedilink
          English
          31 year ago

          If people decentralize and stop hopping on the biggest few instances, that’ll help a lot.

          People can then just hang out on smaller instances and federate to other communities, and the load will be spread out a lot more.

          • Ghostalmedia
            link
            English
            61 year ago

            My hot take is that we need people to hammer certain instances. It’s uncovering performance issues that we didn’t see previously. Stress testing is good.

            Also IMHO, in the future, Lemmy World’s current size will be considered very small. 100k total users and 4000 active users per day will seem quaint.

      • @[email protected]
        link
        fedilink
        English
        41 year ago

        I have had very few issues. It’s probably because I’m on a less popular instance. I don’t understand why everyone piled into one instance instead of distributing the load a bit.