I had no idea this issue had been identified. While I find this tool very useful, the project is seeming rather questionable to me now.

    • kautau@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 days ago

      It sounds like they weren’t using any form of version control, so that’s definitely on them at this point

      • Alexstarfire@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 day ago

        What makes you say that? To me, it sounds like that’s what they do have cause they tracked the change back to him. The commit message obviously said nothing about the file.

        • kautau@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          1 day ago

          Ah I could see that. I took it as them not knowing where the file came from at all, so they’re just asking all the devs who would have had access at that point, which is why it was “hey do you know anything about this file?” and not “is there a specific reason you committed this file to the build?”

            • kautau@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              1 hour ago

              You think they’d call up devs who left them just to ask if they happen to know about a random file?

              I mean, that’s what op said happened. Literally with the verbiage of “file we found” and not “file you committed”