Live data from Hacker News

YouTube-dl's repository has been restored

github.blog

541–550 of 686 posts

Re: YouTube-dl's repository has been restored

#541

Earlier quoted context omitted.

Github links to the EFF letter [0] in the DMCA repo. This letter spells out in clear, convincing and explicit detail why the RIAA was wrong. Profit-making Github and Microsoft could have performed this analysis and championed developers themselves, but it was the non-profit EFF that actually did the work. EFF deserves more credit than just a link for fighting against this shit. [0] https://github.com/github/dmca/blob…

The EFF is probably more qualified to respond to this, actually, since they have some of the most experienced lawyers there are when it comes to defending fair-use/free-as-in-freedom works from malicious DMCA notices. Microsoft's best play is just paying them, which other comments indicate they are doing. The EFF isn't just some non-profit, it's the premier legal entity defending internet freedom. This is squarely in…

> since they have some of the most experienced lawyers there are when it comes to defending fair-use/free-as-in-freedom

And why would one assume that Github or MS do not have such experts? They undoubtedly have the technical know-how, and the primary findings in the letter are of a technical nature, or even obvious to technically savvy people. And the court decisions referred to are not about fair use or free-as-in-freedom.

Re: YouTube-dl's repository has been restored

#542

Earlier quoted context omitted.

You already have to sign in to view some videos, don’t you? Does YT-dL not have a way to handle those right now?

It does, but it's broken. https://github.com/ytdl-org/youtube-dl/issues/23860 The developers are not responding to the issue, and from what I understand it is borderline impossible to fix, because there is an entire security team behind the Google login protection. The only workaround is to login with a browser and copy the cookies from it to youtube-dl.

Why not simply create a youtube-login command that does nothing but launch an electron instance that lets you login into youtube and then returns the cookie?

youtube-dl could then call that command to obtain the cookie.

Re: YouTube-dl's repository has been restored

#543
post #18

The amount of publicity this generated for youtube-dl is astounding... I would love for this to be a ”the plan to get rid of youtube-dl backfired badly for RIAA” ending. But I guess RIAA is reviled enough already so nothing they do really matters. So I suppose the hope is that some political will to change the laws around this arises from it.

I don't believe that RIAA's real intention was simply to get rid of youtube-dl. This was probably just a show to push for more DRM on the Web.

Re: YouTube-dl's repository has been restored

#544

Earlier quoted context omitted.

AFAIU the argument is more that youtube-dl is effectively a web browser and doesn’t do anything that a web browser doesn’t do. Further, it does not include any “secret” key for DRM circumvention like might be bundled with e.g. Chrome in the case of Widevine, where browser vendors agree to protect the secret key.

Right, but the law makes no mention of secret keys, it just says you can't go around anything that controls access to a copyright work; and you can't provide tools to do so. The actual legal definition of tools covers both actual technical purpose as well as marketed purpose. Rebranding, say, OBS as "Recorder for YouTube" and talking about how you can use it to get around YouTube's downloading protections by screenca…

Just re-upload it and change the readme to define "youtube-dl" and "Youtube Digital Library"

Re: YouTube-dl's repository has been restored

#545

Earlier quoted context omitted.

Don't lobby. go to your local caucus and change it from within. Note that I said Caucus: even in a primary state there is some form of caucus where the party decides things. You want to be in this system, this is where the party platform is decided on. This is where the people who are working behind the scene to elect someone make the plans. In turn this is where politicians go to find people who will work for them.…

This sounds hopelessly naive. At the risk of starting a political flamewar, it’s really not possible for any individual to effect large scale change to policymaking beyond the hyper local level. It’s especially impossible to go against massive lobbying interests like the RIAA.

You alone yes. However if everyone reading this works at the problem...

Re: YouTube-dl's repository has been restored

#546
post #508
post #448

Earlier quoted context omitted.

If you read the blog post, it goes over several good changes: - What we’re changing - Developer defense fund - How we’re working to improve the law

Right; but the motivation looks rather like the attempt to restore the good reputation after an obvious mistake; one might have expected Github to check the DMCA request a priori and reject it if unfounded.

Even if so, that doesn't mean that these are not good changes.

Re: YouTube-dl's repository has been restored

#548
post #70

Earlier quoted context omitted.

It's hosted on gitlab.com: $ curl -sS -D- -o/dev/null \ https://youtube-dl.org/downloads\ /latest/youtube-dl-2020.11.12.tar.gz HTTP/1.1 302 Found Date: Mon, 16 Nov 2020 15:04:10 GMT Server: Apache/2.2.15 (CentOS) Location: https://youtube-dl.org/downloads\ /2020.11.12/youtube-dl-2020.11.12.tar.gz Content-Length: 3 Connection: close Content-Type: text/html; charset=iso-8859-1 $ curl -sS -D- -o/dev/null \ https://youtu…

This is a little meta, but you can use the the -I / --head argument to tell curl to download headers only. This will ignore the rest of the response and means you can eliminate all of those other flags. E.g.: $ curl -I https://youtube-dl.org/downloads/latest/youtube-dl-2020.11.12.tar.gz HTTP/1.1 302 Found Date: Mon, 16 Nov 2020 19:10:37 GMT Server: Apache/2.2.15 (CentOS) Location: https://youtube-dl.org/downloads/202…

Not quite: when you pass "-I" curl makes a HEAD request instead of a GET request:

    $ curl -sS -v -I \
        https://www.jefftk.com 2>&1 | grep '^>'
    > HEAD / HTTP/1.1
    > Host: www.jefftk.com
    > User-Agent: curl/7.58.0
    > Accept: */*
    
    $ curl -sS -v -D- -o/dev/null \
        https://www.jefftk.com 2>&1 | grep '^>'
    > GET / HTTP/1.1
    > Host: www.jefftk.com
    > User-Agent: curl/7.58.0
    > Accept: */*
    >
It turns out that, often enough to be worth worrying about, servers do not return the same headers in response to a HEAD request as a GET request, so I always send a GET request when debugging strange behavior.

Re: YouTube-dl's repository has been restored

#549

Earlier quoted context omitted.

It does, but it's broken. https://github.com/ytdl-org/youtube-dl/issues/23860 The developers are not responding to the issue, and from what I understand it is borderline impossible to fix, because there is an entire security team behind the Google login protection. The only workaround is to login with a browser and copy the cookies from it to youtube-dl.

Why not simply create a youtube-login command that does nothing but launch an electron instance that lets you login into youtube and then returns the cookie? youtube-dl could then call that command to obtain the cookie.

There’s a good chance that behavior would result in a CAPTCHA.

Re: YouTube-dl's repository has been restored

#550
post #184

It seems like EFF fought for youtube-dl and GitHub used their letter as legal firepower to bring the repo back online. If GitHub were fighting for the developer they would have funded the attorney, right? Though from their blog post it does look like they are taking steps to fund defense in the future as well as other steps to improve the situation. Reading EFFs claim is pretty interesting, they state that saving a c…

Add to this that the original author recently posted a story about the origins of the youtube-dl script admitting it was designed to do:- download YouTube videos and name the downloaded files appropriately.

https://rg3.name/202011071352.html

Under DMCA, neither writing a script like youtube-dl nor using it is prohibited (making an unauthorised copy of a video could be fair use).FN1 Section 1201 however prohibits distributing the script to others. Thus, the author of the script who "releases" (distributes) it is not necessarily the only one who might be violating the DMCA. Any recipient of the script who distributes it further, e.g., Microsoft, could be violating the DMCA as well.

FN 1. Section 1201 prohibits distributing technology that is designed to circumvent either "access controls" and/or "copy controls". Similarly, the act of circumventing "access controls" is prohibited. However, the act of circumventing "copy controls" is not explicitly prohibited. Making unauthorised copies, e.g., downloading YouTube videos, is subject to the defense of fair use. It is arguable that youtube-dl is only designed to circumvent "copy controls". As others in the thread point out, there are generally no "access controls" on YouTube videos, e.g., password protection. There could be exceptions. If youtube-dl is designed to circumvent geographic or age restrictions, would those be considered "access controls".

Aside from DMCA concerns, Google's Terms of Service for YouTube would appear to prohibit use of youtube-dl:

"The following restrictions apply to your use of the Service. You are not allowed to:

1. access, reproduce, download, distribute, transmit, broadcast, display, sell, license, alter, modify or otherwise use any part of the Service or any Content except: (a) as expressly authorized by the Service; or (b) with prior written permission from YouTube and, if applicable, the respective rights holders;

2. circumvent, disable, fraudulently engage with, or otherwise interfere with any part of the Service (or attempt to do any of these things), including security-related features or features that (a) prevent or restrict the copying or other use of Content or (b) limit the use of the Service or Content;

3. access the Service using any automated means (such as robots, botnets or scrapers) except (a) in the case of public search engines, in accordance with YouTube's robots.txt file; or (b) with YouTube's prior written permission;"

https://www.youtube.com/static?template=terms

Would these TOS be enforceable if challenged. #1 makes no allowance for fair use. What do you think.

Post reply on HN