3 ms·
>I was told I was making stuff up and/or this is in 'best interest' I read the comment thread. It's unclear which comment said that you were "making stuff up".
by gruez 5y ago
>I was told I was making stuff up and/or this is in 'best interest'
I read the comment thread. It's unclear which comment said that you were "making stuff up". There's also zero matches for "best interest" (your direct quote).
>that this only happens because these are 'uncommon applications'.
Relatively speaking, winmerge and kdiff3 are quite uncommon, compared to the normal stuff that people have installed on their computers.
>Pardon the snark, but this is BS and its really sad to see this shitshow being defended.
Are you against people defending microsoft on principle, or are simply unsatisfied with the explanations given? The explanation given (ie. unknown software -> don't know whether it's safe -> warn users it's unknown) seems pretty reasonable to me, as it fails closed rather than fail open. For a technical user that might not be an acceptable trade-off, but I also don't see it as an unacceptable default for non-technical users.
- josephcsible 5y ago> Relatively speaking, winmerge and kdiff3 are quite uncommon, compared to the normal stuff that people have installed on their computers. I think you missed the point here. The fact that programs are uncommon isn't a legitimate excuse for Microsoft to falsely flag them as malware and then not fix it.
- gruez 5y agoI'm must be missing some context here. Did OP and/or the project flag this problem to microsoft?
- e3bc54b2 5y agoI admit and apologize for salty tone above. It is not very constructive, and I agree, and would like to elaborate. This isn't the first time such thing has happened and it won't be last. Windows has becoming more and more painful as Operating System as in operating the machine and has been trying to operate the user instead. The incidents I mentioned about Winmerge and Kdiff3 did happen with me and I stand by that. Above comment does not quote anyone but convey my understanding of the replies in general, which I now understand to be less than perfect. But, > unknown software -> don't know whether it's safe -> warn users it's unknown You must be able to realise that it is not exactly presented in such manner as to be "unknown". Unknown would simply mean windows doesn't know about it and its upto user's discretion. Microsoft, by virtue of all the telemetry, happen to know that this application is uncommon. Why not say that? Why not let the user decide whether they want to run an uncommon app? What is happening here instead, however, is it gets presented as "dangerous" and blocked by default. This, along with Microsoft's position ends up being (in my humble opinion) an abuse of powerful position. And that, again, in my own humble opinion is unacceptable in being defended.
- ethbr0 5y agoTBH, Windows shouldn't even be in the business of having any opinion on uncommon software. If they want to collect data sets for virus protection, go ahead. If they want to hash installed files from common software to detect divergences for virus protection, go ahead. But having any kind of notification that an install is uncommon? We call it a general purpose computer because we want to use it for general purposes: which is to say, uncommon purposes. This feels like ape'ing Apple without thinking it through.
- gruez 5y ago> But having any kind of notification that an install is uncommon? We call it a general purpose computer because we want to use it for general purposes: which is to say, uncommon purposes. How much % of the windows install base do you think is running random programs that they downloaded off github, and how many are just running the top 1000 programs (eg. chrome/office/winrar)?
- ethbr0 5y agoDo we want to live in a world where someone running something different than everyone else on their computer is treated with suspicion? This seems like a very slippery slope towards the iPhonization of the PC.
- gruez 5y ago> Do we want to live in a world where someone running something different than everyone else on their computer is treated with suspicion? It depends on what you mean by "suspicion". Should users be wary and not blindly run uncommon binaries they got off the internet, on a unsandboxed system? I don't see why not. I'll even say that most developers are not exercising enough caution when downloading random packages off npm.
- ethbr0 5y agoIsn't this already what Windows does? It's warned about unsigned binaries on first run for a while now, no? And I can see some argument for that, even if in practice it feels more like teaching users to blindly ignore warnings. But holding uncommon or un-Microsoft-sourced (that is, signed) to a higher standard feels wrong.