Live data from Hacker News

YouTube-dl is now part of GitHub/dmca.git

github.com

121–130 of 332 posts

Re: YouTube-dl is now part of GitHub/dmca.git

#121

> ... is now part of ... Can someone please explain what that means? Is the code not accessible anymore? Is it frozen? No commits allowed? What exactly are the implications here?

It's just someone creating a pull request to the dmca repository with the pull request containing the entirety of the youtube-dl repository (and its history). It's mostly a joke

Re: YouTube-dl is now part of GitHub/dmca.git

#122
post #99

I think the long term solution for this problem is the developers of open source software like the bit torrent client, youtube-dl and other similar software will have to host their code outside of the reach of DMCA regualation. That will usually mean something like Github like site hosted in Russia, China or some other bloc where DMCA does not apply. Right now, lots of users in the US scientific community use Scihub…

Hosting the git repository on ipfs might be a solution.

There is also git-ssb

Re: YouTube-dl is now part of GitHub/dmca.git

#123
post #43

Earlier quoted context omitted.

And as much as RIAA is mostly a slimey pit of lawyers, they would stand no chance again msft's goblin hoard of attorneys.

More attorneys does not convince judges more. The RIAA has some merit, therefore they can preliminary injunction github to remove the repo. If github doesn't comply then they receive sanctions. That's simply how it works.

[deleted]

Re: YouTube-dl is now part of GitHub/dmca.git

#124
post #43

Earlier quoted context omitted.

And as much as RIAA is mostly a slimey pit of lawyers, they would stand no chance again msft's goblin hoard of attorneys.

More attorneys does not convince judges more. The RIAA has some merit, therefore they can preliminary injunction github to remove the repo. If github doesn't comply then they receive sanctions. That's simply how it works.

The other commenters here have argued pretty convincingly that the RIAA has no merit at all. Microsoft should have done the same reading of the letter and determined that this is a hill they have to fight on, in order to operate Github effectively.

Re: YouTube-dl is now part of GitHub/dmca.git

#125
post #115

Earlier quoted context omitted.

Relying on other countries can't ever be a long term solution. That pirate bay and scihub are still around, that their authors are walking around freely, is a miracle that should not be taken for granted. We need to work on fixing these problems in our own countries. We need to talk about the freedoms we care about, put a good brand to those freedoms and win popular attention and enshrine those freedoms into law. And…

> That pirate bay and scihub are still around, that their authors are walking around freely Let's not equate these sites. scihub gives people what they are likely already paid for. Academic publishing business is a fraud. https://www.youtube.com/watch?v=PriwCi6SzLo (recent video on the topic that I liked)

[deleted]

Re: YouTube-dl is now part of GitHub/dmca.git

#126

I think the long term solution for this problem is the developers of open source software like the bit torrent client, youtube-dl and other similar software will have to host their code outside of the reach of DMCA regualation. That will usually mean something like Github like site hosted in Russia, China or some other bloc where DMCA does not apply. Right now, lots of users in the US scientific community use Scihub…

Relying on other countries can't ever be a long term solution. That pirate bay and scihub are still around, that their authors are walking around freely, is a miracle that should not be taken for granted. We need to work on fixing these problems in our own countries. We need to talk about the freedoms we care about, put a good brand to those freedoms and win popular attention and enshrine those freedoms into law. And…

"Peter Sunde, Fredrik Neij, Gottfrid Svartholm and Carl Lundström were all found guilty and sentenced to serve one year in prison and pay a fine of 30 million SEK". I wouldn't call it walk freely.

Re: YouTube-dl is now part of GitHub/dmca.git

#127
post #60

Earlier quoted context omitted.

> RIAA should get a strong kick for this. Regardless of this particular case, the world would've been a saner place if copyright holders were held liable for erroneous claims.

Is it legal to file a DMCA claim when the motivation is retaliation? (Assuming that the person filing retaliatory DMCA claim can satisfy the good-faith requirement, that is.)

Nobody checks motivation. It is legal to file DMCA for anything. As it stands, the hosting providers don't even verify the validity, or the good-faith requirement, because they don't want to get in a fight that could cost them the safe harbor protection. So even invalid DMCA requests usually mean the content will be blocked for a couple of days and the accused party will have to lawyer up to put together a counter-claim.

Re: YouTube-dl is now part of GitHub/dmca.git

#128
post #103

Earlier quoted context omitted.

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.

> RIAA taking down all of GitHub would instantly pit them against all of Microsoft microsoft isn't gonna fight the good fight. There's no reward (to them) for doing so, and there's only a cost. It'd be a stupid business decision. What is more correct is to lobby legislation changes to copyright. Repeal the DMCA, or change copyright law to such that you cannot abuse it this way. And this lobbying is the civil responsi…

No company would fight the good fight for the same reasons. This can only be fixed by changing the law. Not to mention find and persecute the parties who were paid directly or indirectly to pass this legislation. RIAA lobbyists (and all other corporate lobbyists) don't lobby in the sense of arguing for something. They use stick and carrot techniques against legsitlators. It's practically raketeering.

Re: YouTube-dl is now part of GitHub/dmca.git

#129
post #115

Earlier quoted context omitted.

Relying on other countries can't ever be a long term solution. That pirate bay and scihub are still around, that their authors are walking around freely, is a miracle that should not be taken for granted. We need to work on fixing these problems in our own countries. We need to talk about the freedoms we care about, put a good brand to those freedoms and win popular attention and enshrine those freedoms into law. And…

> That pirate bay and scihub are still around, that their authors are walking around freely Let's not equate these sites. scihub gives people what they are likely already paid for. Academic publishing business is a fraud. https://www.youtube.com/watch?v=PriwCi6SzLo (recent video on the topic that I liked)

> scihub gives people what they are likely already paid for

No, as long as the researcher was not bound by the grant to publish in the open and published in a journal/conference with a copyright, you do not have the legal right to get it, even if taxpayers funded the research.

It’s fucked that the law doesn’t stipulate open publications for taxpayer funded research, but that’s an issue with the law. Academic publishing isn’t a “fraud” in the normal definition.

Re: YouTube-dl is now part of GitHub/dmca.git

#130
post #87
post #16

Earlier quoted context omitted.

It's due to how git works. In order for git tools to compare and otherwise work with two commits, both commits need to be in the same repo. If "forking" a repo on github really cloned it in their infrastructure, they'd require far more data. So all forks of a github repo point to the same repo, only with different branches. Note that git clone only clones the actually present branches of the upstream you point it to,…

This isn’t simply because of how Git works. You can configure Git to look in multiple places for repo objects. For whatever reason, the GitHub devs either didn’t know this, or they didn’t want to implement their forking and pull request systems this way. As someone else mentioned, this may be an intentional design to make it simpler to implement pulling down remote PRs from the destination repo.

> You can configure Git to look in multiple places for repo objects.

What do you mean by multiple places for repo objects? Do you mean multiple remotes? The remotes are fully inside your local database if you run commands like git pull or git remote update, they are just not in your checkout. Commands like git show work on commit hashes in those remotes as well, even if it's not in one of your local branches.

Or do you mean configuring git to use multiple .git/objects directories? I haven't heard of that feature, can you give a link?

Post reply on HN