> makes it very likely that it was an honest mistake. I don’t have any doubt that it was an honest mistake. They also took accountability for the mistake, shar

> makes it very likely that it was an honest mistake. I don’t have any doubt that it was an honest mistake. They also took accountability for the mistake, shared their steps to prevent it from happening again, and they’re in contact with the original repo author directly. At this point, anyone digging for excuses to further demonize Microsoft isn’t interested in honest discussion about this issue. This is a textbook mistake followed by rapid resolution (on Christmas Day, no less), with great communication on top.