• FiskFisk33@lemmy.one
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    I saw a lot of people saying they used bots to rewrite their entire post history to things like “fuck /u/spez”

    I’m thinking that amount of comment editing might be quite the spike on the servers.

    • lawliot@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      I did that, but not “fuck u/spez” because that might get the comment deleted altogether making the edit meaningless. Instead I edited to say the comments been deleted in protest against the API changes.

  • nulldev@lemmy.vepta.org
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    A significant number of subreddits shifting to private caused some expected stability issues, and we’ve been working on resolving the anticipated issue.

    How in the world does setting a bunch of subs to private crash the website?

    • andrew@radiation.party
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      High-scale software is complex, sometimes there are edge cases where weird unexpected stuff happens. This isn’t a situation they would normally run into.

      • CycliCynic@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It absolutely is something they would normally run into. I work on maintaining a massive application; think 60+ teams of 6, each extremely specialized and minimal overlap. Almost 75% of my job is predicting issues and avoiding them. Peer testing draws on this a ton as well. They just continue to plainly show that they don’t care. Time and time again, year after year, they continue to have the exact same issues and do fuck all about it.

    • withersailor@aussie.zone
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      It’s the user/moderator fault. If they would just keep working without pay there wouldn’t be any problem. /s