[tptacek]

"Scrutiny" doesn't mean making up nonsense issues, which is what this is. There's no amount of weasel words you're going to apply that's going to make changing an MIT license in a public git repository part of a terrifying conspiracy --- or a conspiracy of any sort.

[windexh8er]

Removing and applying an incorrect license to open source software by a multi-national software giant is a "nonsense issue"?

Hardly "weasel words" when you look at the action that took place. It wouldn't be OK for you to do it and it isn't OK for a bot that Microsoft deployed incorrectly to do either.

[tptacek]

How much of the operation of the MIT license do you want explained to you? I’m happy to do it but don’t want to patronize you either.

[windexh8er]

"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."

I understand the license. Based on your response and Microsoft's attribution change I don't think you understand the argument. I won't patronize you however based on the non-response.

[tptacek]

No, do go ahead, because I don't understand really any of the dudgeon being worked up in this thread, given the original license gave Microsoft the right to do virtually anything it wanted to with the software already. Obviously, Microsoft shouldn't take credit for other people's work; equally obviously, to me at least, that's not what they were trying to do, since all it took was a single Github link to show what had happened.

So, yes, nonsense issue. What am I missing?