• nyan@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    12
    ·
    2 days ago

    I’d rather they be thorough, and I expect their technical resources are a bit constrained. (Plus, I’m pretty sure the user-facing site is or was built in Ruby, and I have no idea what security best practices are for that.)

    • esc@piefed.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      Realistically it can’t take this long if the person working on it has knowledge required, it might be just a generous estimate or they are going for full backup restoration from some kind of very slow cold storage.

      • nyan@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        7
        ·
        2 days ago

        If we were talking about people for whom this was their job, I would agree that they were being way slow, but we’re talking about a group of volunteers who’re cramming this into their free time along with all their other obligations. In that situation, it sometimes takes as long as it takes.

        • esc@piefed.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 day ago

          I’m not saying that they aren’t working hard, might be some other circumstances are preventing them from re-deploying/fixing it, in my experience with infrastructure work cutting single task into smaller chunks staggered over time actually makes it harder.

          Again there are probably other factors there and it’s not simple ‘re-deploy older version’ kind of task.