| ▲ | tialaramex 4 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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'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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | john_strinlai 4 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||