I propose that you learned of the Github Issue when s5msft flapped their wings and flew to your home, landed on your shoulder and telepathically communicated the issue to you.
Kim Dotcom knowingly ran a criminal origination with the intent and purpose of turning piracy into a money maker for him/the company. The US indictment lays this out very clearly, with proof.
EDIT: RE "Why is it a bad thing for Kim Dotcom to make money by using copyrighted works without the permission of the copyright holders, but a good thing for Microsoft to do it?"
Well, for one thing, the works that Kim was making money off of have valid legal protection - proven, codified into law.
The real reason is malice - MS inadvertently failed to include the licenses. Kim structured Megaupload so as to reward the users who uploaded pirated content in great scale. Employees were aware of this usage of Megaupload - that it was effectively the only use of Megaupload, that the site was funded by the money piracy generated, etc etc etc.
Instead of stopping this criminal act, employees emailed links to pirated content hosted on Megaupload to one another. Does any of this sound like what, say, Dropbox would do?
RE RE:
No, your works do not have the same protection that the works of the massive companies that Megaupload victimized have.
Depending upon your license, your works may have no protection at all. Copyright does not protect you - if you release X and the license for X is invalid in whole, you have released X with no terms of use. The Follow? That's a gross simplification, but it will suffice.
I wanted to see Microsoft deliberately violate GPL, but that does not show malice; I want X, but they did not do X.
RE RE RE:
Not quite right. Rights do not automatically default back to you in an instance of your license being restrictive in an illegal matter. A Judge makes that call, and the call very well may be to allow the existing userbase rights to the work in question.
The 'default' does not necessarily apply in instances of abuse.
RE RE RE RE:
You established an install base through an unlawful license. The users do not automatically lose rights to given to them under that unlawful license. There is a human involved here. The human is unlikely to punish your users to resolve your wrongdoing.
See, the license in question gives users X set of rights and one restriction: 'include my name in derivative works'
Your license is illegal in whole, but your intent was to assign this set of permissions/restrictions.
The license in question could be written so as to comply with the law, but as it stands it does not appear to do so. The exact same 'credit me' thing is possible to do legally.
As such, I don't see a human striking the license down without further action resembling a requirement for the software to be relicensed, with users able to acquire this new license if they so choose. In the real world, the one creator does not matter any where near as much as the army of users. Decisions are made to protect the users interests.
RE RE RE RE RE:
"Edit the last: so your theory is that the part of my license which says "you can redistribute this" is legally valid, but the part which says "under the following conditions" is not? That's certainly an interesting legal theory. I am not convinced, to put it mildly."
Both parts could be valid, but in the form they are written are not. As it stands, neither part is valid. A human being (judge) would/should look at the license, see the intent of the creator and resolve the issue.
As I said on Github, I do not regularly read HN and was not made aware of the issue through HN. You have no way of knowing when and how I was made aware of the Github issue. Do not pretend, you look silly when you do. I was not even aware that this 'thing' was on HN until you mentioned it.
A position you disagree with is not abuse. I am not targeting a specific person and forcing them to read my posting, I am responding to an issue with a valid perspective. This is far removed from the kind of awful harassment that happens on Twitter all day, every day.
Read the US Government's case. It's pretty clearly laid out. Megaupload employees were even sharing links to user-uploaded pirated content hosted on their servers.
Those who release pirated content in a particular way. All non-p2p warez groups.
I don't see any normal (Dropbox, etc) cloud storage companies being designed to make hosting pirated content easy and lucrative for them. Believe it or not, most people want to make an honest living.
Youtube has a legitimate use. Megaupload was designed to be used to host pirated content, and for Kim Dotcom to make money off it. I, along with the rest of the scene, am/are insulted by this abuse of the content we released.
Kim Dotcom - piece of shit who makes money on the back of the scene, gets raided for (knowingly) doing so.
Somehow the combination of Kim being a piece of shit (whom no one would want to work for) and the very real possibility of the US Government going after anyone having anything to do with MegaUpload V2 resulted in the new product not being very secure/good. What a surprise.
You get it yet?