Email or username:

Password:

Forgot your password?
Top-level
🏳️‍🌈🎃🇧🇷Luana🇧🇷🎃🏳️‍🌈 :verified:

@vkc @arraybolt3 Meh, I wouldn’t really say they’re ignoring it. Ventoy’s last commit itself was 2 months ago, and the issue isn’t much older than that. The binary blobs need to go, sure, but it’s not like anyone complaining is opening a pull request for that.

This is a foss project, the dev isn’t being paid for it or anything so maybe let’s just not reproduce the foss negativity we all complain about? They’re in no way obliged to respond as quickly as anyone wants, you know?

Instead of accusing without proof and recommending a closed source expensive hardware alternative (and btw the same proofless accusation could be made here, saying people are attacking #ventoy just to recommend a backdoored closed source alternative…) maybe someone could actually build those binaries and make sure they are the same? And while they’re at it document the building processes so someone can make a PR removing those blobs from Ventoy’s source.

The suspiciously enthusiast fanboys are weird tho…

2 comments
Aaron Rainbolt

@luana @vkc The last commit was made two months after the thread was started. 60 days seems like plenty enough time to at least drop a note indicating that they saw it and will take it into consideration.

No one is obliged to do anything. But you can learn from their behavior.

I intend on building those binaries and seeing if they are the same. I discussed techniques for doing this elsewhere in the thread.

burne

@luana @vkc @arraybolt3 "it's foss" is not a good reason for maitaining a potential malware vector.

Go Up