Live data from Hacker News

Microsoft forked MIT licensed repo and changed the copyright [fixed]

github.com

31–40 of 626 posts

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#31
post #26
post #24

Earlier quoted context omitted.

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.

Quoted post unavailable.

How 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?

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#32
post #13

So you can't do that? I do it all the time when I fork something.

You need to go revert all of those commits ASAP.

EDIT: also if there are any forks of your project, you should ask people who forked it to restore the original copyright notice as well. If the original copyright holder sees your name instead of theirs, they'll know who to sue.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#34
post #26
post #24

Earlier quoted context omitted.

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.

Quoted post unavailable.

Problem 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.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#35
post #26
post #24

Earlier quoted context omitted.

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.

Quoted post unavailable.

How about stop blaming the bots and take responsibility? The bots have none, the humans behind the bots have full responsibility.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#37
Since they also removed a full stop at the end...

What is the point of using all caps? For me it makes legal texts like these really annoying to read. I'm not a native English speaker, is that really correct English writing? Aren't there clear rules when to use capitalization? Like, at the beginning of sentences. Feels like they are abusing the language.

Can they just lower case the paragraphs, to make things more convenient to read? Or does that change the legal meaning? For me it would feel like they would stop screaming :-)

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#39
post #26
post #24

Earlier quoted context omitted.

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.

Quoted post unavailable.

Bots don't steal licenses; people who program bots steal licenses.

It's the latter action that's being addressed here.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#40
post #26
post #24

Earlier quoted context omitted.

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.

Quoted post unavailable.

Eh, 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...

[1]: https://www.theverge.com/2020/6/2/21277863/microsoft-winget-...

Post reply on HN