Earlier quoted context omitted.
Where possible I recommend not caring because figuring out whether malice was present is difficult and you can likely address a problem without needing to be sure. For example by creating working processes which never end up "accidentally" causing awful outcomes. This is sometimes more expensive, but we should ensure that the resulting lack of goodwill if you don't is unaffordable. Worst case there is malice and you'…
> Worst case there is malice and you've now made it more difficult to hide the malice so you've at least made things easier for those who remain committed to looking for malice, including criminal prosecutors. i am quoting the maintainer of the project. take it up with them if you think microsoft coordinated a directed attack on their project.
It's really easy to end up with procedural machinery that makes it unpleasant for other entities that you don't like.
It seems to get the things that you do like and value less often. Why? Because you think about the consequences to what you consider important and you're inclined to ignore potential consequences to those you oppose or are competing with.
The Vogons weren't necessarily overtly malicious when they obliterated Earth.