zlacker

Can you explain in what way Windows already does this?

>>bradfo+(OP)
If an executable isn't code-signed, Windows SmartScreen displays a big scary "This file may harm your computer" warning box, requiring multiple clicks to get past. Been like that for years.

Code-signing certs used to be very expensive and annoying to obtain. The situation has improved a lot since the launch of Azure Trusted Signing, and now it's roughly on par with the cost and annoyance level of code-signing for Mac binaries.

>>evanel+Fa
Big scary box might as well be outright disallowing, since someone who isn't 100% sure about your software will likely be dissuaded by the warning. But if they want to install it, then they can.

My understanding of the article is that there is nothing that a user will be able to do to install your software.

> “developers [that we approve] will have the same freedom to distribute their apps directly to users through [installation] or to use any app store they prefer.”

So, less freedom.