Earlier quoted context omitted.
> 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'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't. If MS didn't comply with the DMCA takedown notice, then t…
RIAA taking down all of GitHub would instantly pit them against all of Microsoft, and make every developer who already hates their guts to pick up the pitchforks and march. They won't try doing it.
YouTube-dl is now part of GitHub/dmca.git
41–50 of 332 posts
Re: YouTube-dl is now part of GitHub/dmca.git
#42Earlier quoted context omitted.
This is such a great hack. I approved the PR, naturally.
Note that a hack is not a fix. All of you, write to your representatives about that if you care. In EU when they were going to put some similar laws we all organized and wrote massively to the parliament and they backed down. It is a lot of effort but it works.
Re: YouTube-dl is now part of GitHub/dmca.git
#43Earlier quoted context omitted.
> 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'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't. If MS didn't comply with the DMCA takedown notice, then t…
RIAA taking down all of GitHub would instantly pit them against all of Microsoft, and make every developer who already hates their guts to pick up the pitchforks and march. They won't try doing it.
Re: YouTube-dl is now part of GitHub/dmca.git
#44Earlier quoted context omitted.
There's a lot of reasons it's possible, but the one that sticks out is that the repo owner needs to be able to modify the commit before the PR is merged. AFAIK, the way that's done is by incorporating the remote repo's commit history into the destination repo underneath a pr-specific branch, which naturally brings all of the commits themselves into the repo's git database.
Follow up question, are these commits or pr-specific branch accessible in target repo's `git` (not GitHub)?
But this is exactly how merging a PR locally[0] works.
0: https://docs.github.com/en/free-pro-team@latest/github/colla...
Re: YouTube-dl is now part of GitHub/dmca.git
#45Heh, I didn't expect to get much attention for this. I thought it would be funny to push a merge commit between the 2 repo's latest commits. As a result, the git history is accessible from the dmca repo if you know the commit hashes. Since I didn't rebase, all the commit hashes were preserved with signatures. Another fun discovery is that deleting my fork of github/dmca didn't affect the PR like I thought it would, s…
The end result will be GitHub taking down this repo and possibly blocking PRs. Congratulations on making life difficult for other people.
Re: YouTube-dl is now part of GitHub/dmca.git
#46Earlier quoted context omitted.
Just curious, why is this possible with an unmerged PR? Just a weird setup on GitHub's end?
I think it's because GitHub wants to allow repo maintainers to merge in PRs without them having to add separate remotes themselves, ie `git remote add` isn't required to `git merge`. This basically means that any content can be injected into anyone's GH repo (since PRs can't be turned off), but really only in terms of being able to view it on the GitHub website. To give an example, pull 437 on torvalds/linux[0] hasn'…
Re: YouTube-dl is now part of GitHub/dmca.git
#47Earlier quoted context omitted.
Note that a hack is not a fix. All of you, write to your representatives about that if you care. In EU when they were going to put some similar laws we all organized and wrote massively to the parliament and they backed down. It is a lot of effort but it works.
And what should we ask for? There is stuff to complain about with the DMCA, but the core process is reasonable. Someone claims copyright infringement by a user, and the website takes the content down. The user claims no copyright infringement, the website restores the content. The website is immune from liability, the alleged copyright owner can settle things in court with the user if they want to.
If guns don't kill people, people kill people, then certainly congress can accept that software doesn't pirate copyrighted works, people pirate copyrighted works.
Re: YouTube-dl is now part of GitHub/dmca.git
#48Heh, I didn't expect to get much attention for this. I thought it would be funny to push a merge commit between the 2 repo's latest commits. As a result, the git history is accessible from the dmca repo if you know the commit hashes. Since I didn't rebase, all the commit hashes were preserved with signatures. Another fun discovery is that deleting my fork of github/dmca didn't affect the PR like I thought it would, s…
Re: YouTube-dl is now part of GitHub/dmca.git
#49Earlier quoted context omitted.
> 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'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't. If MS didn't comply with the DMCA takedown notice, then t…
RIAA taking down all of GitHub would instantly pit them against all of Microsoft, and make every developer who already hates their guts to pick up the pitchforks and march. They won't try doing it.
Re: YouTube-dl is now part of GitHub/dmca.git
#50Heh, I didn't expect to get much attention for this. I thought it would be funny to push a merge commit between the 2 repo's latest commits. As a result, the git history is accessible from the dmca repo if you know the commit hashes. Since I didn't rebase, all the commit hashes were preserved with signatures. Another fun discovery is that deleting my fork of github/dmca didn't affect the PR like I thought it would, s…
This is hilarious, well done. 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't care less if Microsoft deleted my account over it. 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/Kubernetes/e…
You'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.
https://en.wikipedia.org/wiki/GitHub#Controversies
Its also pretty obvious MS doesnt check any of these DMCA claims, and just rubber stamps the commits with an insulting and sterile "Process DMCA request" commit msg.
gitea and github both host splendidly inside kubernetes or standalone.