THE excuses/reasons not to "Delete GitHub" are running out or have run out already (years ago). Microsoft's motivations were explained all along and GitHub is run by a foe. He knows exactly what he's doing. These people have no remorse.
"...instead of Microsoft fighting back it's going even further towards the RIAA."The latest [1,2] of many updates on this, including what we mentioned yesterday in relation to the SFC, shows that instead of Microsoft fighting back it's going even further towards the RIAA. This will impact far more than one project in the long run. GitHub is a Microsoft censorship machine and an extension of Microsoft's "milking cows", whose sole purpose is to control and undermine the competition.
"Microsoft is not about making money," an associate told us, as "profit motive has very little to do with how they work. Too many people wrongly project their own values onto that company. For instance, time and time again, Bill [Gates] has shown that he is willing to lose money in an area indefinitely just to ensure that no one else makes money either. Another example is the Windows monopoly, Microsoft did not make its money selling Windows, it made it off of the monopoly rents, not the actual market price of the product. I can't believe it's 2020 and people still fall for their act." ⬆
Importantly, the action also angered those who maintain, use, and support the software, plus those who didn’t appreciate the perceived overreach into the open source community. As a result, large numbers of people united to stand shoulder to shoulder.
In many instances their response struck at the heart of the RIAA’s aims: if they wanted YouTube-DL to be harder to find, activists would make it even easier. The software was mirrored, cloned, uploaded to hosting platforms and even turned into images that could be easily shared on millions of sites. This, despite the software still being distributed defiantly from its own site.
One of the responses was to repost the content to Github itself, where hundreds of YouTube-DL forks kept the flame alight. A copy even appeared in Github’s DMCA notice repository where surprisingly it remains to this day. Now, however, Github is warning of consequences for those who continue to use the platform for deliberate breaches of the DMCA.
So here's an interesting thing. Certain commit hashes are rapidly heading toward being illegal on Github.
So, if you clone a git repo from somewhere else, you had better be wary of pushing it to Github. Because if it happened to contain one of those hashes, that could get you banned from Github. Which, as we know, is your resume.
Now here's another interesting thing. It's entirely possible for me to add one of those commit hashes to any of my repos, which of course, I self host. I can do it without adding any of the content which Github/Microsoft, as a RIAA member, wishes to suppress.
[...]
What would then happen if you cloned my git repo and pushed it to Github?
The next person to complain at me about my not having published one of my git repos to Github, and how annoying it is that they have to clone it from somewhere else in order to push their own fork of it to Github, and how no, I would not be perpertuating Github's monopolism in doing so, and anyway, Github's monopoloy is not so bad actually ...