[issue]: Remove BLOBs from the source tree · Issue #2795 · ventoy/Ventoy
github.com
What happened? Due to the recent XZ-Utils drama I checked the code and I'm appalled. There are more BLOBS than source code. https://github.com/ventoy/Ventoy/tree/3f65f0ef03e4aebcd14f233ca808a4f8946...

Dear community,

I hope this message finds you well. I want to take a moment to address the concerns raised in Issue #2795 regarding the BLOB functionality in our app. First and foremost, I sincerely apologize for any confusion or frustration this may have caused. I was on vacation during this time, and I understand that my absence may have contributed to the lack of clarity surrounding this issue.

The BLOB feature is an important aspect of our app, and I recognize that the documentation surrounding it has not been as clear as it should be. I appreciate your patience as we work through these challenges, and I want to assure you that I am fully committed to resolving this matter.

As I return to work, I will prioritize updating the documentation to provide a comprehensive understanding of how the BLOB functionality works. I will also investigate the specific concerns raised in Issue #2795 to ensure that any underlying issues are addressed promptly.

Your trust in our software is paramount, and I am dedicated to regaining any confidence that may have been affected by this situation. I am confident that, with your continued support and feedback, we can enhance the app and provide a better experience for all users.

Thank you for your understanding and for being a part of our community. I look forward to sharing updates with you soon as we work towards improving our app and its documentation.

Warm regards, longpanda

    • longpanda@lemmings.worldOP
      0·
      1 month ago

      The BLOB in my app is a key element that manages and stores various types of data efficiently, ensuring smooth performance and user experience. We understand the interest in this feature, and we will issue an official statement soon to provide more detailed information about its functionality.

      • T0RB1T@lemmy.ca
        0·
        1 month ago

        I’m gonna be honest, when I read this, I initially thought it was a joke answer by a community menber. The joke being about vague hand-wavy statements that people make when dodging questions.

        Then I realized it’s OP, and OP is ostensibly the actual developer. I have nothing specific to say about this situation, especially from a technical perspective, but this reply… why even bother?

        • Localhorst86@feddit.org
          0·
          1 month ago

          I can not tell you, how much I thought the same. It sounds like an answer filled with as many buzzwords you can think of, made up by some random as a joke, moking such answers. Then I saw the username highlighted in blue, indicating it was OP.

          I am still not sure of it’s just a mocking answer, tbh.

      • herrvogel@lemmy.world
        0·
        1 month ago

        Ah, if I understand this explanation right, the blob’s purpose is to do things and stuff. Is that correct?

      • muhyb@programming.dev
        0·
        1 month ago

        A BLOB in an open source project usually indicates something proprietary. Does Ventoy really need this to function or just to speed things up? If it’s the latter, we don’t need this and community can probably take care of it in time.

    • deadcade@lemmy.deadca.de
      0·
      1 month ago

      According to Jim Starkey, the person who coined the term, “Blob don’t stand for nothin’.” However, it is often referred to as a “Binary Large OBject”, meaning a large file with content not easily readable by people.

      With an open source project, you have source code which is turned into executables/“blobs” by the compiler. As long as you trust the compiler, you can (functionally) know the content of the blobs by looking at the source code they were made from.

      In the case of Ventoy, several “blobs” are included from an unknown or vague origin. This is a great way to bundle malware, as seen with the XZ backdoor from earlier this year. As such, the original creator of the linked issue is requesting they are built/obtained at compile time, so either the content or origin of these files can easily be found.