4 ms·
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I apprecia
by zenexer 5y ago
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I appreciate hearing about the incident.
Incidents don’t need to be malicious to be newsworthy or intriguing.
- akyoan 5y ago
- luckylion 5y agoHow often did the bot make the same mistake? In how many of those cases does Microsoft now assume they have copyright and make their army of lawyers enforce it? Are you willing to go up against Microsoft in a court, rolling the dice?
- Crosseye_Jack 5y agoProblem is in a world of moderation actions being taken by bots and not humans often the only way to get a human to review its decision is to raise awareness on social media like HN. How often have we seen closed accounts getting resolved after complaining about it on HN/Twitter/Etc. I’m not saying tha to how it should be, just what it’s become.
- AdrianB1 5y agoHow about stop blaming the bots and take responsibility? The bots have none, the humans behind the bots have full responsibility.
- frob 5y agoBots don't steal licenses; people who program bots steal licenses. It's the latter action that's being addressed here.
- bayindirh 5y agoEh, considering Microsoft made similar "harmless" mistakes in the past, I don't give them "harmless mistake" credits. e.g.: Anyone remembering AppGet? [0][1] [0]: https://www.theverge.com/2020/5/28/21272964/microsoft-winget-windows-package-manager-appget-copied https://www.theverge.com/2020/5/28/21272964/microsoft-winget... [1]: https://www.theverge.com/2020/6/2/21277863/microsoft-winget-windows-package-manager-appget-response-credit-comment https://www.theverge.com/2020/6/2/21277863/microsoft-winget-...
- akyoan 5y ago
- bayindirh 5y ago> Do you have brain? Just tapped to my head, looks like there's one. > Leave a message when you realize that forking a repo on GitHub is not the same as publishing a copy under your name. First, you send me a message when you realize you can't just change an MIT License's copyright line as you see fit, then we can discuss the rest. Also, milking knowledge from someone with an implicit promise of hiring, and re-implementing the software and tossing the original developer aside like an orange pulp is nowhere ethical.
- feanaro 5y agoThe mistake is not harmless. Corporations don't get to hide behind their bots' mistakes. Microsoft needs to reverse the change, explain why it happened and implement precautions so it doesn't happen again.
- anonymousab 5y agoBot-driven crimes would be crimes nonetheless.
- coliveira 5y agoYou wouldn't believe how long "harmless mistakes" are maintained without correction, as long as they're benefiting a big company.
- kstrauser 5y ago- You’re at work looking for an appropriately licensed library to do X. - You find one with an MIT license and use it. - Oops! It was really GPL and now you have some undesirable options to face. Microsoft’s had a few “accidents” lately that remind me too much of their old war on the GPL.
- deleted 5y ago[deleted]