<story><title>YouTube-dl is now part of GitHub/dmca.git</title><url>https://github.com/github/dmca/tree/416da574ec0df3388f652e44f7fe71b1e3a4701f</url></story><parent_chain><item><author>AdamJacobMuller</author><text>This is hilarious, well done.&lt;p&gt;I realized something while :+1:-ing your PR: I was thinking about how digg deleted my account over posting the AACS key, I really couldn&amp;#x27;t care less if Microsoft deleted my account over it.&lt;p&gt;Very interesting considering that even just 2 years ago I never would have done this for fear of my account being deleted. All of my work and personal projects are moved to gitlab (the CI&amp;#x2F;Kubernetes&amp;#x2F;etc integration are just too good to pass up).&lt;p&gt;I know a sample size of 1 has an effectively 100% error rate, but, I think Microsoft is losing mindshare with GitHub. Stuff like this doesn&amp;#x27;t help. I could see a small company like GitLab needing to toe the DMCA line, but, Microsoft has the deep pockets and could have built some major community will here by handling this better. Unfortunate that they didn&amp;#x27;t.&lt;p&gt;Anyway, fun hack, I wonder how long it will last, or will they merge it? It must be the most approved PR in GitHub history at this point!</text></item><item><author>Stephen304</author><text>Heh, I didn&amp;#x27;t expect to get much attention for this. I thought it would be funny to push a merge commit between the 2 repo&amp;#x27;s latest commits. As a result, the git history is accessible from the dmca repo if you know the commit hashes. Since I didn&amp;#x27;t rebase, all the commit hashes were preserved with signatures. Another fun discovery is that deleting my fork of github&amp;#x2F;dmca didn&amp;#x27;t affect the PR like I thought it would, so it seems a mirror of youtube-dl&amp;#x27;s commits are stuck in the ether until GH deletes my PR and garbage collects the repo.</text></item></parent_chain><comment><author>echelon</author><text>Microsoft is losing the good will they&amp;#x27;ve worked so hard to rebuild.&lt;p&gt;Microsoft employees, managers, Satya: do you see what you&amp;#x27;re doing? I love the direction you&amp;#x27;ve taken over the past five years, but bowing to the RIAA and attempting to disrupt an innocuous tool are horrible decisions. It&amp;#x27;s a chilling note, and everyone involved in tech can hear it.&lt;p&gt;Are you telling us Github is not a safe place to develop software anymore? Because I&amp;#x27;ll believe it and go elsewhere.&lt;p&gt;Siding with the RIAA and bringing engineers&amp;#x27; Github accounts into compliance will tell us who your real customers and allies are.&lt;p&gt;Don&amp;#x27;t side with regressive legal trolls that bring zero benefit to the world.</text></comment>
<story><title>YouTube-dl is now part of GitHub/dmca.git</title><url>https://github.com/github/dmca/tree/416da574ec0df3388f652e44f7fe71b1e3a4701f</url></story><parent_chain><item><author>AdamJacobMuller</author><text>This is hilarious, well done.&lt;p&gt;I realized something while :+1:-ing your PR: I was thinking about how digg deleted my account over posting the AACS key, I really couldn&amp;#x27;t care less if Microsoft deleted my account over it.&lt;p&gt;Very interesting considering that even just 2 years ago I never would have done this for fear of my account being deleted. All of my work and personal projects are moved to gitlab (the CI&amp;#x2F;Kubernetes&amp;#x2F;etc integration are just too good to pass up).&lt;p&gt;I know a sample size of 1 has an effectively 100% error rate, but, I think Microsoft is losing mindshare with GitHub. Stuff like this doesn&amp;#x27;t help. I could see a small company like GitLab needing to toe the DMCA line, but, Microsoft has the deep pockets and could have built some major community will here by handling this better. Unfortunate that they didn&amp;#x27;t.&lt;p&gt;Anyway, fun hack, I wonder how long it will last, or will they merge it? It must be the most approved PR in GitHub history at this point!</text></item><item><author>Stephen304</author><text>Heh, I didn&amp;#x27;t expect to get much attention for this. I thought it would be funny to push a merge commit between the 2 repo&amp;#x27;s latest commits. As a result, the git history is accessible from the dmca repo if you know the commit hashes. Since I didn&amp;#x27;t rebase, all the commit hashes were preserved with signatures. Another fun discovery is that deleting my fork of github&amp;#x2F;dmca didn&amp;#x27;t affect the PR like I thought it would, so it seems a mirror of youtube-dl&amp;#x27;s commits are stuck in the ether until GH deletes my PR and garbage collects the repo.</text></item></parent_chain><comment><author>nimbius</author><text>&amp;gt;I think Microsoft is losing mindshare with GitHub.&lt;p&gt;You&amp;#x27;re not wrong. Sure, the cloudflare browser checks and antibot pages on gitlab are aggravating, but there are a litany of documented reasons people are walking away from Microsofts latest acquisition.  maybe the biggest one is the ICE contract they ardently refused to back out of.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;GitHub#Controversies&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;GitHub#Controversies&lt;/a&gt;&lt;p&gt;Its also pretty obvious MS doesnt check any of these DMCA claims, and just rubber stamps the commits with an insulting and sterile &amp;quot;Process DMCA request&amp;quot; commit msg.&lt;p&gt;gitea and github both host splendidly inside kubernetes or standalone.</text></comment>