Document the evolving Windows SmartScreen errors
Since we moved from PyInstaller to Nuitka for building application executable binaries, we have noticed frequent Windows SmartScreen errors. These are false positives and untruthful detections, only because the executable binaries are not code signed. The protection system flags them as potentially unsafe due to absence of an active code signing certificate but that does not mean that the codebase is malicious.
To proceed past these frivolous warnings, simply click on "More Info" and then "Run anyway" to start the executable binary. As this project is free and open source software, we cannot afford to make additional expenses to subscribe to various code signing services. Not only are the executable binaries are transparently built on GitHub Actions, folks are invited to verify the project's integrity by compiling things locally.
Document the evolving Windows SmartScreen errors
Since we moved from PyInstaller to Nuitka for building application executable binaries, we have noticed frequent Windows SmartScreen errors. These are false positives and untruthful detections, only because the executable binaries are not code signed. The protection system flags them as potentially unsafe due to absence of an active code signing certificate but that does not mean that the codebase is malicious.
To proceed past these frivolous warnings, simply click on "More Info" and then "Run anyway" to start the executable binary. As this project is free and open source software, we cannot afford to make additional expenses to subscribe to various code signing services. Not only are the executable binaries are transparently built on GitHub Actions, folks are invited to verify the project's integrity by compiling things locally.