Note that RIAA is making this takedown because the software CAN be used to download copyrighted music and videos, and it uses examples in the ~~README~~(unit tests, see correction[1]) as an example of that:
> We also note that the source code prominently includes as sample uses of the source code the downloading of copies of our members’ copyrighted sound recordings and music videos, as noted in Exhibit A hereto. For example, as shown on Exhibit A, the source code expressly suggests its use to copy and/or distribute the following copyrighted works owned by our member companies:
They could, of course, have asked for the code to have been changed. Instead, they attacked the project itself. IANAL, but this seems outrageous the same way DMCA'ing a Bittorrent client would be. This doesn't circumvent DRM like Widevine. I don't understand what leg they have to stand on here.
This feels like DeCSS all over again.
P.S.: They also took down youtube-dlc, even though it's not listed.
[1]: It turns out I am wrong. It wasn't in the readme, but in the test cases. See extractor/youtube.py. To me this seems even more tenuous, but IANAL.
The fact that copyrighted works were included in the readme shows it was intended for that use, and the RIAA complaint will likely stand up to any legal scrutiny. Just because it can be used for legit purposes too won't matter in the slightest. I mean, Napster could have been used for legal means as well, and it got destroyed in court.
The only chance tools like this have legally is when infringement is an "unintended side effect."
Just to add a data point, but back when I still was working for a video distribution startup, we offered our customers the ability to directly import their video inventory from YouTube. They were the owners of the videos, it was just a convenient (and very popular!) feature for them to let us handle this import.
We used YouTube-dl for this, of course. No way we could have done this easily without it. We imported hundreds of thousands of videos like this.
I suspect there are many more legitimate uses of YouTube-dl than you would expect.
To add another item to the list of legal, legitimate uses of YouTube-dl: lots of public domain content is uploaded to YouTube, including a lot of media produced by the US government. For example, The White House has a YouTube channel, and my understanding of US law is that the vast majority of the content uploaded to that channel is public domain (produced by federal employees in the course of their job). Journalists or anyone else wanting to monitor the government would likely find YouTube-dl useful for archiving this public domain content from government channels.
I've gobbled hours of Cspan videos with youtube-dl. Turns out cspan is a hodgepodge of like 3-5 video hosting and codec schemes, but it is able to pull about a 3rd of them no problem.
Definitely forking it, I need this to continue my research.
The beauty of `git clone` is that there are copies of the repository on many thousands of hard drives (including mine -- last pulled a few days back). The main loss at this point is the metadata stored in GitHub's proprietary addons, like issues.
We can hope this inspires a) greater suspicion toward proprietary players that are sitting atop open-source work like GitHub (they're not the only one by any stretch); and b) greater adoption of systems that distribute the software's entire history together, including documentation and bug reports, e.g. Fossil.
Why should they ? YouTube is in the streaming business, not the archival business. If someone wants to make their videos available for download they should post a link on their website, served through their servers and bandwidth.
Youtube benefits from being everyone's go-to site for finding video content. Keeping that monopoly of mindshare is worth far more to them than any short sighted profit maximisation.
Yeah that's not some kind of general rule. This is because the US legal system in particular lets this happen. And in fact, the US legal system works so badly that it often still benefits companies long after they've monopolized too much, causing all sorts of damage to consumers and other companies that actually did nothing wrong.
Isn't streaming live video? It seems to me that youtube is exactly in archival video and hardly in streaming. But it's a big site so maybe a lot of people use it in ways I don't know.
Streaming is not exclusively live video. Streaming is viewing the file as it downloads. As a stream. The alternative is what we did in the dark ages. Download the entire file before beginning playback.
WMVs can embed instructions on where to grab codecs or authorization to play the content in the multimedia. Back in the day if you played WMV with windows media player this could be used to pwn your computer.
I'd love to be wrong here, but there are two separe things, content license and general YouTube terms of use, I think the terms prevent you from downloading any content, the fact that some content is licensed CC has to do more with being explicit, perhaps for displaying publicly or just informative, and I want to think they are leaving a bit of gray area for non abusive use(tons of downloads) , but you can see there is no download button, and if you build something that depends on it to certain scale they could go after you with terms of use, not license.
If you can prove me wrong with some link to where are we covered legally to download CC content from YouTube, it would make me very happy.
> I think the terms prevent you from downloading any content, the fact that some content is licensed CC has
Maybe you are right. If that is the case it is questionable whether contents produced with tax payers' money should exclusively hosted on Youtube to increase Google's income and restrict tax payers' rights.
I remember using youtube-dl back 8 years or so ago when I was an undergrad in India to download MIT OCW lectures (and others e.g. SICP vidoes, Coursera), because bandwidth was limited, download was capped, and 3G was too expensive. I could watch these videos anywhere, and whenever I wanted. And I'm pretty sure non of those videos had (or even have) ads.
It's one thing if a tool designed for legitimate archiving use results in incidental violation of copyright.
It's another thing entirely, legally, if a tool is designed for violating copyright. In such case, it doesn't matter if there are also legitimate fair use uses of the tool.
And that's what the README showed: that youtube-dl was built primarily to violate copyright.
EDIT: based on other comments, it turns out the offending evidence was in the unit testing code not the README file, which legally makes it a bit worse than if it had just been in the README file.
Downloading a Youtube video with youtube-dl IS NOT violating copyright in the USA.
Downloading videos may violate Youtube's TOS, but that's civil/contract law and not criminal and so the DMCA can't be used to enforce such TOS violations.
A person might share a video they don't own the copyright to, after downloading it from youtube with youtube-dl, but youtube-dl has no functionality in it to do such illegal sharing. It only has the time-shift functionality.
The only tenuous leg the RIAA has to stand on is claiming that allowing only streaming of content constitutes some form of digital rights management code, and by reverse engineering it, without imposing the same restrictions as Youtube's website and apps, do, maybe that's some form of circumvention which will be found not entirely legal.
They had to cite a German legal ruling which found YouTube’s “rolling cipher” was an anti-circumvention device. But German court rulings have no bearing on US law, and Germany doesn't have a DMCA statute, so it is a specious claim, and the RIAA is just hoping an open source project won't be able to fund a legal defense.
It's Betamax time-shifting plus macrovision/video stabilizers all over again.
> Downloading a Youtube video with youtube-dl IS NOT violating copyright in the USA.
Are you a lawyer? Ethically I agree with you: copyright law regulates distributing copies to other people, and YouTube is the only one doing that in this scenario.
But I've been told in other internet discussions that courts don't see it that way. Basically, that the point of the law is to allow big companies to stop people from accessing media without paying, and the interpretation is stretched as far as it needs to be in order to enforce that.
Yeah if you get realistic about it, courts in the USA simply see it the way of the party with the most money all the time. You can interpret laws until you're blue in the face, but they get to break the rules.
Clearly whenever we discuss laws in the USA as they pertain to a small party versus a giant corporation, we do so in the context of a hypothetical fantasy where these laws are actually followed equally.
It's like everybody's playing hide 'n seek, and you're like "of course a real SWAT team would surround and find you in moments".
> Yeah if you get realistic about it, courts in the USA simply see things in the way of the party with the most money all the time.
This might or might not be true, but even if it’s true it’s not (necessarily) a sign of bias or corruption on the part of the legal system, it might simply show bias (or rather strategic foresight) in what they bring to court.
In the spirt of Von Clausewitz’s On War, it is always easier to attack than to defend, because the defender has to maintain a solid performance throughout every inch of their line, while the attacker need only find a weakness and exploit it.
RIAA might’ve decided months or years ago that as part of their legal strategy they needed to curtail downloading an intact local copy of streamed content, since then they might’ve been seeking the perfect violation that, in the opinion of their lawyers, would show clear enough intent to break copyright law, be a core node in the ‘ecology’ of the downloading-streams strategic landscape, and have a hope of creating suitably broad and useful precedents to employ later. Maybe this case finally caught their eye. Maybe they’d been eying it for a while and only just recently something changed and opened the barn doors for attack (in the RIAA lawyers’ opinion — for example, was the example added to the test cases recently?)
A good question is: why didn’t they do this earlier? Another good question question is: could they do it to anybody else, and if they could, why haven’t they?
So you see it as the judges typically ruling in favour of the corporations. I see it as perhaps the corporations being very savvy in choosing what to attack and being willing to wait for ages for the perfect circumstances.
> Yeah if you get realistic about it, courts in the USA simply see it the way of the party with the most money all the time. You can interpret laws until you're blue in the face, but they get to break the rules.
This is a result of money being a proxy for competence.
They may not be a lawyer, but they have basic grasp of copyright law. It is indeed distribution of copyrighted content without permission that is illegal, not obtaining it.
> Copyright infringement requires distribution, that is the core of the offense.
Infringement does not require distribution. The rights encompassed by copyright include reproduction, derivation, distribution, public performance, public display, and broadcast rights. Infringement of any of those rights is copyright infringement. For US law, see at least 17 USC 106(a) abd 501(a).
The tort of copyright infringement is as you describe it.
When people say copyright infringement requires distribution they mean you can't be tried in a criminal court for merely copying you can still be sued.
> The crime of infringement requires distribution.
At least in the US, criminal copyright infringement may be for any act of infringement. The statute 17 USC 506(a) [0] describes the necessary conditions for a criminal prosecution, which are not limited to reproduction or distribution. Here [1] is a nice article from the department of justice about the crime.
Courts take a very non literalist approach to technology. Even though YouTube is literally sending copies of the video to users’ computers, because they provide no convenient mechanism for saving the video then courts will tend to ignore that. Instead, it will be argued that a musician’s YouTube channel is acting like a venue and the users are attending an authorized public performance. youtube-dl would then be equivalent to someone recording a concert using a camera.
They might have a very strong case in court. One of the reasons youtube-dl is so active as a project is because they’re in an arms race with Google. Google regularly changes how videos are delivered in an effort to thwart downloading tools. The RIAA could seize on this and even have Google testify that they’re trying to protect against this unauthorized downloading. Given the revelations about the tests in youtube-dl’s own repo, it would be a very difficult legal battle.
In that context youtube-dl would be a camera which most assuredly isn't illegal.
In the criminal sense, you're correct.
In the civil law sense, you'd be wrong. Using a camera to record a performance is an act of copying and is subject to copyright law. Generally, if the performers and/or the owner of the copyright don't give you permission to record the show, you don't have the right to do so. (Note that taking pictures or recording short clips is usually but not always regarded as fair use. Recording an entire performance without permission is rarely treated as fair use.)
However, recording the performance is also an act of creation, resulting in a derivative work that has its own copyright, but one which is useless without a copyright license to the underlying performance.
I don’t understand your argument. No one is saying that recording a performance isn’t subject to copyright law. They are saying that youtube-dl is the camera, or the camera manufacturer. Canon or Nikon are not subject to copyright law because I use one of their cameras to illegally record a concert, I am. I am the one that did the illegal act and the fact that manufacturers make cameras, that gave me the ability to do it, is not the problem. The argument is youtube-dl shouldn’t be subject either, that it is the individuals using it to download copyrighted material that are breaking the law and a program having the ability to be used illegally is not the fault or responsibility of the program.
Downloading a Youtube video with youtube-dl IS NOT violating copyright in the USA. Downloading videos may violate Youtube's TOS, but that's civil/contract law and not criminal and so the DMCA can't be used to enforce such TOS violations.
Downloading a Youtube video is making a copy. Whether it is a copyright violation depends on whether Youtube's license includes letting visitors make permanent copies, as this is considered a separate type of license. The TOS has nothing to do with it.
A person might share a video they don't own the copyright to, after downloading it from youtube with youtube-dl, but youtube-dl has no functionality in it to do such illegal sharing. It only has the time-shift functionality.
This is false. Also, time-shifting is not a a valid fair-use defense for material available on-demand, because the justification for time-shifting (as in the Betamax case) generally no longer exists. There are other fair use arguments that could be made, but time-shifting isn't one of them.
They had to cite a German legal ruling which found YouTube’s “rolling cipher” was an anti-circumvention device. But German court rulings have no bearing on US law, and Germany doesn't have a DMCA statute, so it is a specious claim, and the RIAA is just hoping an open source project won't be able to fund a legal defense.
I don't know if you're joking or not, but they cited a variety of US cases. Kazaa, Limewire, Napster, etc, are all US cases that all came down the same way: a tool intended primarily for copyright violations violates the DMCA, and in certain cases can even expose its developers to statutory damages under the copyright code.
It's Betamax time-shifting plus macrovision/video stabilizers all over again.
Nope, not even close for so many reasons already explained in this and other comments.
> Downloading a Youtube video is making a copy. Whether it is a copyright violation depends on whether Youtube's license includes letting visitors make permanent copies, as this is considered a separate type of license. The TOS has nothing to do with it.
YouTube is not the copyright owner (in almost all cases). Downloading a video with youtube-dl may not be a copyright violation if you already separately hold a suitable license, or are in fact the copyright owner yourself (as in the case of one of the grandparent comments).
Yeah, I should have worded that better. I was referring to Youtube's license with the RIAA, since Youtube doesn't provide a copyright license to its users for content licensed from third parties.
If the license between the RIAA (or other licensor) and Youtube allowed visitors to make permanent copies of Youtube streams, then downloading a Youtube video would not be a copyright violation. But generally, having entered into streaming and downloading licensing agreements with the RIAA before, I would be extremely surprised if the RIAA would enter into such a license with Youtube, as it would kill sales of digital music downloads if people could just download permanent copies of Youtube videos instead for free.
If you own the copyright and upload a video to Youtube, then it wouldn't be a copyright violation to download that video from Youtube.
I wouldn't be surprised if there's a legal violation when you're downloading a copy from YouTube even though you're the original copyright owner of the video. Youtube has a license to distribute the copy according to their TOS. That license will be subjected to specific terms (streaming + DRM protection). It might not include allowing creators to circumvent those terms for archival purposes.
It's very possible to have a TOS violation but not a copyright violation if you're the copyright owner of the video being downloaded.
Owning the copyright means you don't violate the copyright in making a copy, but that doesn't mean you get to make that copy through any means; you still have to use legal means, and for a website, that means methods that are acceptable under the TOS of that website.
I haven't seen anyone else making this argument yet, but yes! Chunk by chunk, streamers copy bits into their buffers and discard them as they are done watching. Is that discarding required, when the same companies can charge extra for additional bandwidth usage (not for making additional copies, but for clogging up their pipes)
I'm not sure if this is going to be considered similar to taking a full copy but I'm also not sure what substantial purpose there would be for taking that full copy except for the (probably valid fair use) purpose of shifting access to manage time, location, or network conditions. Given that you pay separately for your bandwidth, and there is an incentive to conserve it, I don't see any way this isn't considered fair use without a sharing component.
Taking a copy is incidental to lawfully consuming the content that was provided in an authorized setting, whether that copy is stable or not. Nobody is hosting copies of YouTube content, paying the bandwidth and hosting bills so anonymous co-parties to the infringement can enjoy the content separately from the authorized channel, (it is not even suggested that anyone would want to do this.)
> I think the question is whether the license YouTube implicitly provides to copy so one can stream also extends to downloading to a file. Probably not.
> Why that should be youtube-dl's fault is yet another question, of course.
TV broadcasters do not give you a license to copy their content but it's legal to record TV. Why is youtube any different?
It was legal to record TV, using VCRs and DVRs, for time-shifted viewing, due to the alternative being that the content could not be consumed at all (at the time of the Betamax case, episodes were broadcast once, and generally not re-broadcast unless they were extremely popular, and were not available for purchase individually or even as part of a collection).
Today, there are a multitude of options for consuming TV content, and due to the (recent) creation of time-shifted licenses, the fair use justification for standalone-DVRs has mostly gone out the window (which is why they're not for sale anymore; for example, Tivo no longer offers standalone DVRs; Hulu, cable companies pay for time-shifted viewing).
As Youtube was always on-demand to begin with, the time-shifting justification for recording TV in the Betamax case never applied.
Legally, even running a program is making a copy (from disk to RAM):
Yes, that is why 17 USC § 117 provides that making a transitory copy necessary to run the program (such as a RAM copy), or an archival copy of the data needed to run the program, are both explicitly not violations of copyright.
I think the question is whether the license YouTube implicitly provides to copy so one can stream also extends to downloading to a file. Probably not.
It does not. Youtube does not explicitly, or implicitly, provide the user a license of any type. Youtube has licensed the right to provide a temporary copy of a video to a user.
Why that should be youtube-dl's fault is yet another question, of course.
It normally wouldn't be...except that some idiot decided to include unit tests to make sure that youtube-dl could be used to download music videos covered by RIAA licenses. That basically makes the RIAA's case, especially since youtube-dl must be regularly updated to handle Google's countermeasures.
Right, but 17 USC§117 only applies to programs, not video. Who provides me the license to copy the video from the buffer of the network card to main RAM, and then to GPU ram, and then to my screen?
iTunes was designed [in part, probably a principal part of the original design] for CD ripping, I gather (I haven't personally used it more than twice, many years ago).
Format shifting was at the time not allowed in UK copyright law, and again is not allowed as of a couple of years ago (it was only allowed for about a year).
iTunes was designed for copyright violation. I'm sure the manual will show that.
Just for comparison.
It's my understanding that any media _can_ fall under Fair Use in the USA, meaning that there would have to be specification as to who was using the software and their circumstances within the unit tests in order to make it infringing use. You might fir example be archiving, or preparing educational materials, or compiling a review, or doing subtitling.
It's not sufficient to prove someone downloaded, you have to show it was infringing activity. How do you do that with a unit test? Software to perform legitimate, legal downloads would still have to do that same test.
In short you've found a smoking gun, now prove its principle purpose is murder.
This comment is provided solely for entertainment and in no way relates to my employment.
Tunes was designed [in part, probably a principal part of the original design] for CD ripping, I gather (I haven't personally used it more than twice, many years ago).... iTunes was designed for copyright violation. I'm sure the manual will show that.
No, Itunes was designed for organizing music. How you got that music was a separate function,and you could split out the CD ripping functionality and still have the primary function of iTunes. Additionally, making copies of physical media for personal archival purposes is recognized as a legitimate fair use (and was back then), so the the CD ripping functionality would have generally still have been okay. And yes, there is case law on when ripping CDs is considered fair use and when it is not.
It's my understanding that any media _can_ fall under Fair Use in the USA, meaning that there would have to be specification as to who was using the software and their circumstances within the unit tests in order to make it infringing use. You might fir example be archiving, or preparing educational materials, or compiling a review, or doing subtitling.
Yes, any media can be subject to a fair use defense. The second statement is not relevant to the copyright analysis. The last statement are examples of fair use, but note that acquiring the content for the purposes of preparing educational materials is not automatically "fair use". For example, preparing educational materials for a class provided at a for-profit institution, or in educational materials sold commercially, would not support a fair use defense, though otherwise the use of copyright content in educational materials has generally been deemed fair use.
It's not sufficient to prove someone downloaded, you have to show it was infringing activity. How do you do that with a unit test? Software to perform legitimate, legal downloads would still have to do that same test.
The unit-test is a part of a different analysis from a basic copyright infringement claim; That question is whether the tool is intended for violating copyright and for that, they don't need to show any infringing activity actually took place, only that the tool was intended for infringing activity. The DMCA does not require a creator to suffer harm before they sue, since it recognizes that in the computer age, once such harm occurs it may not be possible to put the genie back in the bottle.
No, iTunes was designed for organizing music. How you got that music was a separate function, and you could split out the CD ripping functionality and still have the primary function of iTunes.
Well, being able to rip music off your CDs was literally advertised as an iTunes feature; Apple promoted iTunes after its introduction in 2001 with the slogan "Rip, Mix, Burn." And Apple did get accused by various industry players of promoting copyright violation. I wouldn't say that iTunes was "designed for copyright violation" any more than I'd say youtube-dl was "designed" for it, but Apple definitely understood that iTunes had value to people who wanted to make digital copies of media in ways that did not strictly fall under fair use guidelines. :)
but Apple definitely understood that iTunes had value to people who wanted to make digital copies of media in ways that did not strictly fall under fair use guidelines.
Ripping CDs for personal archival copies had already been characterized as fair use by the courts by the time iTunes was first released. If it hadn't been, the industry players wouldn't have just "accused" Apple of promoting copyright violation, they would have done something about it. The music industry has always been very aggressive about protecting their IP rights.
It would have been very different if iTunes had the slogan "Rip, Mix, Burn, Share."
The kicker is that if their demo examples had been something like that, or e.g. students downloading copies of free lectures, or etc, the RIAA would have much less of a case. No actual code would have had to change.
If you have a tool which skirts (bad, overreaching, probably constitutionally invalid) laws, be smart about how you present them!
If this content is freely available, why can't we take a fair use copy? That is not a violation of copyright. (Even if it is entertainment / not educational.) Those are the terms of the deal, we made when we enshrined copyright into law. If you can show it to me, then I am allowed to take a copy. (Is it not? I thought that DMCA law itself was written to skirt around this fact of law.)
If this content is freely available, why can't we take a fair use copy? That is not a violation of copyright.
Making a copy on its own is not fair use. What matters is the reason for making the copy. If you are making an connectivity-shifted copy (aka, for viewing away from internet access) there could be a fair use argument to download content from a streaming site that is not otherwise available for offline consumption.
But the flipside of that: if there is a way to access the content in a way that fair use is not implicated (i.e., because the copyright owner makes the content available for that use case such as offline viewing, even if payment is required), then generally fair use does not apply.
Remember: fair use is a defense to violating copyright, and it must be reasonable under the circumstances. Not wanting to pay for a license for your intended use case is generally never considered reasonable.
If you can show it to me, then I am allowed to take a copy.
That has never been the law, at any point in the history of copyright, dating back to before copying works was trivial.
In Sony Corp. of America v. Universal City Studios, Inc. the majority opinion stated:
> [There must be] a balance between a copyright holder's legitimate demand for effective - not merely symbolic - protection of the statutory monopoly, and the rights of others freely to engage in substantially unrelated areas of commerce. Accordingly, the sale of copying equipment, like the sale of other articles of commerce, does not constitute contributory infringement if the product is widely used for legitimate, unobjectionable purposes. Indeed, it need merely be capable of substantial noninfringing uses.
Is there a subsequent opinion that reversed that? (How is youtube-dl substantially different from a VCR recording, if youtube is substantially similar to a broadcast medium?)
> [W]hen one considers the nature of a televised copyrighted audiovisual work ... and that time-shifting merely enables a viewer to see such a work which he had been invited to witness in its entirety free of charge, the fact ... that the entire work is reproduced ... does not have its ordinary effect of militating against a finding of fair use.
To play devil's advocate, I wonder if it can really be said that when you watch a youtube video you have been
> invited to witness in its entirety free of charge
when you consider advertising. It could be argued that when you watch a monetized youtube video you are being invited to view the video in exchange for also viewing advertisements as a form of payment.
I hope that you're right though, and that we get a ruling in favour of being able to make copies for fair-use.
> To play devil's advocate, I wonder if it can really be said that when you watch a youtube video you have been
>> invited to witness in its entirety free of charge
> when you consider advertising. It could be argued that when you watch a monetized youtube video you are being invited to view the video in exchange for also viewing advertisements as a form of payment.
The problem with this idea is that you're quoting a case about recording televised broadcasts. The quote you pulled your quote from begins "when one considers the nature of a televised copyrighted audiovisual work".
Televised works were shown with embedded advertising a lot more intrusive than what can appear on a YouTube video. There is no way for the presence of advertisements to affect how this argument applies to YouTube, when it was originally cast in terms of television.
Gets complicated, but watching ads to watch a video is a separate issue from the underlying copyright for the content.
The content holder licensed the content to Youtube (or Vimeo, etc), but does not necessarily control the monetization of that content by the licensee. (Generally, the license will say something like royalties shall be X% of revenue derived from the content, without limiting itself to specific methods of monetization.)
Youtube doesn't have a license to give to the viewer; the license they have is merely to show you the content.
I hope that you're right though, and that we get a ruling in favour of being able to make copies for fair-use.
This has been the law for several decades already. But the key thing to understand is "fair use" doesn't mean "to avoid paying." If digital content is available for purchase, the courts generally have not found making a permanent copy from a streaming source to be fair use. (Where it gets complicated: multiple copyrights applying to a single work, such as the dancing baby Prince video. The creator of the video was okay with people viewing it and downloading it freely, but Prince was not. In the music arena, this would be a non-issue due to compulsory licenses, but those licensing schemes don't exist for other types of media. Ultimately, the court said that the focus of the video was the toddler dancing, and that the music was incidental, so including it in the video was a legitimate fair use. But it took more than a decade for the case to be resolved.)
For sure, that is the argument they will have to make! As a counter-argument, what if I paid for my youtube premium membership though, to avoid the advertising, and really what I want to do is to location-shift within the bounds of the law, I want to take my laptop into the wilderness and watch the movies I paid for, on an Indian reservation in front of a mountain scene, ... where there is no broadband or cell radio tower service?
(Hypothetically of course! Youtube-dl is not only for Youtube.)
That's multiple different licensing scenarios. Paying for Youtube Premium doesn't give you a right to download whatever videos you want, since that right has to be granted by the copyright owners of the videos.
If you purchased a movie, presumably this included the rights to watch it offline (and most of the movie lockers like Vudu, etc, generally include such rights), then the selling website generally makes available copies for offline viewing (and many Blurays include codes to activate on movie locker service to get a license for a digital copy). In such case, you would need to use that service for downloading the offline copy, because the Youtube copy isn't part of that license to you.
There are fair use rights that are not able to be satisfied without a copy.
You can assert all of that, but unless you have some landmark precedent to cite that agrees with what you're arguing, I'd like to hear a court decide on that. Sony Betamax says what I'm arguing, and archival can be for fair use, too. There is 36 Cinema, which maintains copies of classic kung-fu movies that aren't available for purchase anymore, and invites Rza from Wu-Tang Clan on periodically for broadcast viewing with a value-add, Rza's commentary. Since the movies are no longer available for sale, there is no impact to marketability. Since commentary is added, transformative. That's all fair use, format-shifting. I say youtube-dl is a tool for format shifting, with substantial non-infringing uses that present a compelling value and don't impact marketability, exactly in line with the Betamax case. If format-shifting and copy for archival was strictly prohibited as you suggest, those movies could be lost forever whenever a format becomes obsolete. When was the last time you saw a VCR? (CD or DVD player?)
That's just one of the things that the fair-use rules and exemptions in copyright were written to help resolve positively.
You can record anything on TV with a VCR, even if it's available separately for purchase on video. There is no technical way I can see in which this scenario differs. You are not obligated to pay for content again and again in every medium, format-shifting is also an allowable kind of fair use. Everything you're saying makes sense, but I don't think it's as clearcut as you say, until it has been decided by a court (and appealed, and decided again by a higher court.)
You're literally just arguing against how the law works in the US. I'm not going to argue against the fictional legal system you've set up in your head.
The 36 Cinema stuff resulted in a new copyrighted derivative work: the commentary. And they can distribute that commentary all they want...but to distribute the underlying films as part of a commercial offering they need copyright licenses to those films. It's irrelevant that the underlying films are not for sale at retail, since they can still acquire a copyright from the copyright owner.
Format-shifting isn't fair use. It's literally an act of copying that is subject to copyright protections. Format-shifting might be fair use, but you have to do the full analysis, and format-shifting to avoid paying for a copy in the destination format is not fair use.
That's just one of the things that the fair-use rules and exemptions in copyright were written to help resolve positively.
Now you're just making stuff up. 17 USC 107 sets forth the basic rules for fair use, and they're quite limited.
When was the last time you saw a VCR?
Last week. Best Buy and Walmart still sell VCRs...Millions of people in this country still have old TVs with purely analog connections.
You are not obligated to pay for content again and again in every medium, format-shifting is also an allowable kind of fair use.
Actually, yes, you are, since each offering of the content in a different medium is a different copyrightable work subject to its own copyright. A VHS copy of a film is very different from the Bluray copy of the same film.
> but to distribute the underlying films as part of a commercial offering they need copyright licenses to those films
They sell tickets to these events. It's still fair use, (and it would not be possible to have these events without someone first acquiring a digital copy for archival.) You're arguing that they could broadcast the video with commentary but they can't make (or take) a copy? This is prerequisite to the activity! And many of these publishers may no longer exist, as not everyone agrees these movies are classics.
Also section 117 of Copyright Act explicitly calls out the making of a copy for archival as an allowable exception.
Copyright included fair use and the courts ruled that a balance for fair use must be maintained for the monopoly rights of copyright to be enforced, but congress wrote the DMCA and said "nah"?
Yeah I'm gonna need to hear that from the courts, my assertion here is that the DMCA unfairly skirts around this provision of copyright, not that it superceded it outright.
Those fair use rights are not an optional provision of copyright, (although many opinions have stated that copyright provides the author may refuse to allow copies if they technically can, unless you have relevant case law that superseded Sony Betamax, in that case I believe it was the minority opinion), I am not aware of any decisions that say anything other than "copies for fair use may be required for there to be fair use."
But I am not a lawyer, and just because I haven't heard of the case doesn't mean it didn't happen...
Copyright included fair use and the courts ruled that a balance for fair use must be maintained for the monopoly rights of copyright to be enforced, but congress wrote the DMCA and said "nah"?
The Constitution gave Congress the power to right the laws on copyrights, not the courts. The courts don't write copyright law, they just interpret it.
Fair use, for example, is explicitly written into the copyright statutes by Congress (17 USC § 107), but with sufficient breadth and ambiguity in the language that the courts have added in uses that were not explicitly written into the law but could be reasonably read as being within the scope of the text of the law. That is indeed why the court in the Betamax case was able to characterize "time shifting" as fair use in the first place.
Yeah I'm gonna need to hear that from the courts, my assertion here is that the DMCA unfairly skirts around this provision of copyright, not that it superceded it outright.
Again, Congress gets to write copyright law... They get to change it how they want, so long as it does not violate the Constitution. (Note that the DMCA is an "act" of Congress, which is the method by which Congress actually writes and changes the laws of the US. When we refer to the DMCA, we are referring to the changes to US copyright law embodied by the DMCA.) Courts have upheld the constitutionality of the DMCA.
Those fair use rights are not an optional provision of copyright,
Yes, they are. The Constitution makes no provision for "fair use." In fact, by its bare text, it would appear that the Constitution would not support fair use because it provides for "exclusive rights" to go to creators and inventors (for the periods covered by copyright and patent). "Fair use" is entirely a legislative creation of Congress, and theoretically Congress could take it away.
unless you have relevant case law that superseded Sony Betamax
I don't know why you're hung up on Betamax. That case was based on the copyright law at the time of the case, i.e., the 1980s. Congress changed the copyright laws after that case (in the DMCA and other legislative acts), so Betamax is no longer relevant except as persuasive authority, and the underlying facts supporting the time-shifting as fair use ruling generally do not apply to digital content available on-demand.
> "Fair use" is entirely a legislative creation of Congress, and theoretically Congress could take it away.
If you have a court decision that shows a court interpreted Congress' actions as revoking fair use by the enactment of DMCA, then I'll concede the point, (but you won't have one as the DMCA does not explicitly revoke fair use.) DMCA laid out protections for copyright owners who sought to protect their copyright with eg. DRM schemes.
That doesn't revoke fair use. It just makes it practically difficult to utilize, since you might have to (illegally) circumvent a copyright protection device in order to access those fair use rights. They are still there, copyright owners just have a few more tools in their toolbox to prevent you from accessing them lawfully.
Is Youtube's "rolling cipher" such a mechanism? Debatable. Is the proper remedy a DMCA takedown of the entire youtube-dl source, or something else? That's all something for a court to decide. Only certain uses of youtube-dl are potentially foiling anti-circumvention devices like "rolling cipher", it's a utility that works on many video streaming sites, (and substantially many of the works on those sites are not protected by "rolling cipher" or similar, possibly any, DRM.)
> I don't know why you're hung up on Betamax.
Has there been a landmark ruling since, that reversed Betamax? It was decided by the Supreme Court, so unless you have one, I don't think I can agree that it is no longer relevant.
> But the flipside of that: if there is a way to access the content in a way that fair use is not implicated (i.e., because the copyright owner makes the content available for that use case such as offline viewing, even if payment is required), then generally fair use does not apply.
Can you cite a source for this? I do not believe that is generally the case. You are allowed to rip CDs even if the same music is sold digitally and you are allowed to DVR a TV show even if they sell DVDs of the same show.
You are allowed to rip CDs even if the same music is sold digitally and you are allowed to DVR a TV show even if they sell DVDs of the same show.
Fair use is a balancing act based on analysis of various factors. In the case of ripping CDs for personal archival purposes, the courts treated that as fair use because at the time there was otherwise no way to make archival copies. It's very possible that today a court could rule that making archival copies of CDs for personal use is no longer fair use, because the digital version of the music now exists, as a separate article from the CD, and can be legally acquired. (Note that libraries and other archives still have a statutory archival use exception. Also note that because a CD is a physical good, there are certain rights associated with it that would not apply to content acquired digitally.)
For TV shows, it's not the same thing, since a DVD of an entire season is not the same thing as being able to view just a single episode. That being said, with the rise of digital, on demand availability of individual episodes, the original fair use justification for VCRs and DVRs has basically gone out the window.
The original Tivo could not exist today, and indeed...it does not: Tivo no longer offers standalone DVRs. Hulu, Youtube TV, your cable DVR, all of those services license time-shifted viewing rights from the copyright owners. (Yes, the studios created a new type of right just for this...)
>an entire season is not the same thing as being able to view just a single episode.
Even from your own archive?
Originally many people started out with plain paper terminals rather than the spiffy video terminals that would later become common.
Well, sprocket-feed terminals more precisely, where you sit at a floor-standing wide-carriage _printer_ having a full QWERTY/ASCII keyboard, connected to the mainframe using a RS-232 serial COM port cable.
Or remotely dial-up over regular phone lines using external modems compatible with the kind first used for internet dial-up. Modems later found internally as standard equipment on PC's, made to accept a common RJ-11 telephone connector, eliminating the need for the RS-232 cable.
Not unlike a space-age teletype.
Either way, you type to the computer and it types back to you.
When available, as we all know it's been a while and computers still can never be expected to have 100 percent uptime, so time shifting has always been the norm in some way or another. At this point with a dumb terminal you just come back later when the mainframe is not too busy for input, or for output just wait for the printout until it's good and ready.
More effective session management would have to be accomodated by storage of some kind not unlike the punched paper tapes for sending and receciving on some teletypes.
Underneath the terminal you have a big box of the fan-feed computer paper so you fundamentally get an endless record of the communication in its entirety. Otherwise there is nothing. This is the default. Out-of-paper meant no communication and no data.
Pallets and pallets of boxes and boxes of printouts, excessive amounts of trees giving their lives and paper mill pollution up the wazoo (you ever smell that stuff?). But it's worth it, these are not copies, this is the original data, as you received it coming in live over the wire.
Depending on the institution or individual, and the risk of losing this unique output, archival handling procedures may apply.
Upgrading to a VT-102 type video terminal is actually analogous to a desktop PC when it comes to form factor, but the command line is still not from a local processor, and no local disk storage.
Naturally you still get your continuous printout as the screen display scrolls it on by, now possible from a plain serial printer (or from the same old paper terminal) connected to the second COM port on the VT-102 for pass-through printing.
You still use the terminal to operate the command line & display the output from a remote CPU, and with scrolling ability, can roll back to redisplay some recent earlier content. This was not a copy either, it was the same original live data as printed, just redisplayed. Not every terminal had that kind of memory though, and if present, not much.
Then you get _intelligent_ terminals with lots more memory plus local floppy storage, having more than two COM ports, and a simple local OS in ROM to handle these peripherals.
It finally became posible to judiciously save paper like never before, from that point on there has always been a local SAVE command of some kind. That's one of the only main purposes of any mainstream desktop workstation ever since.
You end up with a stack of floppies instead of paper containing the original data from that hardware session.
Interestingly, even today it is sometimes still faster to look something up in your paper records than find it on a disk though.
Anyway the disks simply have digital representation specifically crafted for the storage medium, often in appropriately treated text files.
From that point you could always play back data from a disk to your console screen, and/or one or more of the COM ports which may be connected to other terminals, computers, storage, or printing hardware. When the time is right.
The purpose of putting data into a computer file format to begin with is precisely so this type of communication can be achieved electronically.
And also, so the file or disk can be archived using one of the only non-communication commands in such a pre-DOS desktop environment, the ominous-sounding COPY command.
Well, it's electronic and you need to keep the original completely intact, so no telling how many times you need to run the COPY command to get a reliable archive.
But when one of the things that came across your wires is something like the text of The Godfather, that's an author's original work and it would be most questionable to manufacture copies for people as if it were your own creation, perhaps unfair even if proper attribution is given.
Each user has always been responsible for appropriately respecting the rights owners of any material in their archive, and questioning their own operation enough to avoid things like selling duplicates to just anyone. It's part of the responsibility of having such powerful equipment at their disposal.
Not just for those with dual floppy drives. Takes lots of floppy disks to boot sometimes too. Twenty years ago most PC's already came equipped with two CD drives in addition to a floppy drive, one CD drive was writable for archiving since floppies were not too popular any more.
MP3 sites earlier than Napster arose without question as experimenters compressed and shared their archives using the emerging codec. This was nothing like selling pirated copies of CD's, and was not made available to the general public by any means, just the few technology enthusiasts who had PC's with internet capability.
With progress in hardware and internet performance, there should be more advantage for archival use as time goes by.
Now exponentially more good material is at risk of being lost due to electronic or legislative failures, beyond the pre-existing threats from ordinary disasters like floods or acts of war. There's also the limitations of things like MP3 compression.
There should continuously be improving apps so users can work more effectively than ever with the desired portions out of their own complete digital history.
Meanwhile there is some consensus that operators without your permission are clandestinely eavesdropping to make truly illegal copies of your original complete digital history (along with many others') and extract portions that they my find desirable, sometimes against your own best interest.
You surely need to be entitled to better than this, and in favor of your own preferences instead.
In the USA according to copyright law archiving is not supposed to be impossible.
Nobody has a continuous paper record to fall back on any more.
Any threat to the usefulness of your digital equivalent would seem to be a form of cyberattack now that we have a better idea of how a cyberattack can do damage.
It's always been the same tool with possible uses for good or evil, the desktop workstation.
What you primarily do with it can only be determined by examination of its complete digital history.
From an entertainment law perspective it would seem like the only sensible violation could be if illegal entertainment had actually ocurred, not whether the file was being stored locally or remotely.
If most of the files just sit there almost all the time, with almost no dancing to the computer or anything like that, that's an archival device not an entertainment device.
Even more so when the primary user handling of the files is to maintain them intact against all odds, without ever intentionally using the file contents to achieve the files' own particular underlying purpose, whether entertainment files or not.
By that logic one would only be allowed to record with a vcr shows that weren't available on tape. Furthermore according to parents logic VCRs shouldn't be allowed to exist because they can record from both categories.
It depends. If the shows are available with each episode available on a separate tape (and each separate tape could be individually purchased), then yes, the VCR fair use justification evaporates. But generally VHS tapes include multiple episodes and individual episodes can not be individually purchased (other than a limited number of very special episodes), so there is still an argument to be made for fair use on the basis of each individual episode.
Furthermore according to parents logic VCRs shouldn't be allowed to exist because they can record from both categories.
No, that's not at all what I said. VCRs are just tools. Tools are subject to a different analysis post-DMCA: does the tool have a substantial non-infringing use or is it deliberately designed to violate copyright?
In determining whether a tool was deliberately designed to violate copyright, they look beyond just the mere function of the tool and examine why that functionality is present, and how the tool and that potentially-violating functionality is marketed.
On that note: DVRs generally no longer exist today as standalone goods (see, for example Tivo, etc). This is because the copyright owners introduced new time-shifting licenses a few years ago, and your cable company, Hulu, etc. pay the copyright owners for the right to let their viewers view content on a time-shifted basis. A standalone DVR would generally have the primary purpose of violating those (relatively new) rights, and thus wouldn't pass muster today.
What about VCRs? They're still okay. They make degraded, low-quality copies of broadcast transmissions for archival/time-shifted uses by people who have TVs that still connect to VCRs. As those people generally wouldn't be able to access the equivalent digital content on their TV, it's clear that the primary use of VCRs is for fair uses purposes.
I think gamblor is conflating the commercial publisher's responsibility to pay for each format commercially offered separately (they can only make commercial distributions that are appropriately licensed), with the consumer's fair use right to create a backup copy of their legally obtained copy of any copyrighted media, for backup or archival.
You absolutely do not have to buy the MP3s rather than rip the CD that you own to MP3, just because they also sell MP3s and you want your archival copy to be in MP3 format. You can make them as a backup copy. (If there's no anti-circumvention device like the famous CSS encryption in your way, that is.) The publisher cannot pay once for CDs and also sell MP3s, they need a separate license for that (if that is how the author's licensing is written, granted, that's a fact.) The consumer is not bound in this way, they "paid" for their copy (presumably, if payment was needed to receive it) and they can format shift if their use passes the 4 factors balance test for fair use, (and if it is technically possible to do so, eg. without bypassing an anti-circumvention device, (thanks DMCA.))
Moreover, we are talking about youtube-dl, which is not owned by the RIAA and they have no right to take it down in this way. They can seek relief in the form of an injunction, the scope of the injunction to be determined by the courts, who would have to consider the substantial non-infringing uses of the tool; they would be unlikely to decide that vaporizing youtube-dl from orbit is the appropriate remedy.
Taking a copy does not affect the potential market of the copyrighted work in any way. Sharing a copy is another matter. Youtube-dl facilitates taking a copy only, it is not a tool for sharing. This case is substantially different than Napster, I disagree. In some circumstances, you must be able to take a copy in order to exercise your allowed "transformative" fair use rights. You cannot sample a record without a way to take a copy.
I don't know where tranformation would land as they are just streaming data and not actually viewing it.
It's (potentially) the whole content, but a case that was literally just uploading an entire video as-is with a different title was ruled fair use not too long ago, so this isn't itself damning.
The nature of the work seems irrelevant here as it's not viewed. It could easily be replaced with any other video -- even one owned by the repo creators.
Likewise, since they are unit testing rather than viewing the content, I doubt there is any commercial harm and the market overlap between video viewers and unit testers is zero.
No, the unit test isn't fair use, because it wasn't necessary to violate the license holder's copyrights in order to test the code.
It's (potentially) the whole content, but a case that was literally just uploading an entire video as-is with a different title was ruled fair use not too long ago, so this isn't itself damning.
I'd like to see a cite for that. Generally, uploading whole content owned by someone else is not fair use absent something like the content being newsworthy in itself (such as video of a police beating). Otherwise, fair use would generally require some transformative effort.
Likewise, since they are unit testing rather than viewing the content, I doubt there is any commercial harm and the market overlap between video viewers and unit testers is zero.
Copyright violations don't require the copyright holder to prove commercial harm. That's the entire point of statutory damages.
"Not necessary" doesn't mean it's not still fair use. Lots of things aren't necessary but one definition or another. The argument here is that it's lack of necessity makes it incidental.
Once the infringing use has been established, it doesn't matter that there is also the potential for legitimate fair use. If it did, then Napster, Kazaa, and Limewire would still be around because they all had the potential for legitimate fair use.
Not having read any legal literature around or really understanding the DMCA, how can they not make a distinction between things with legitimate uses and not? How do torrent clients stand up to that?
Torrent clients don’t name themselves “Game of Torrents” and have test cases for downloading TV shows.
The problem YouTube-dl ran into is they literally named themselves after a prominent streaming site that is copyright holder friendly and also literally tested, in their codebase, the ability to do a thing that arguably violates the DMCA.
I don't think it does. Just because there are copyrighted works in the test cases, doesn't mean they are willfully in violation of copyright. If I am granted a license by Youtube to view this material, then is it not also fair use if I take a copy for later review, or otherwise maintaining the fair use rights innately afforded to me by copyright?
What other facilities could I use to exercise my fair use rights in this case, besides tools like youtube-dl? If the video is already available freely for viewing (with advertising), are there any greater damages that aggrieved parties could calculate than the loss of advertising revenue from my repeated viewing of that file?
What incentive is there for me to share this file in violation of copyright if anyone can download a fair use copy for themselves, with the tools provided by youtube-dl?
It makes it worse because otherwise they could have argued that the README was separate from the development of the tool itself, so the tool itself wasn't intended for violating copyright.
By putting the infringing act into the code of the tool itself, they lose the ability to make that argument, and moreover show that the tool was built to infringe copyrights, because clearly they thought it was important enough to be able to infringe copyrights that they created multiple unit tests for it.
are there any greater damages that aggrieved parties could calculate than the loss of advertising revenue from my repeated viewing of that file?
The loss of advertising revenue is largely irrelevant unless the RIAA chooses to demonstrate the amount. Copyright law provides statutory damages starting at $750, and for that they just need to show a single infringing act (and for each additional act they prove, they get another $750).
What incentive is there for me to share this file in violation of copyright if anyone can download a fair use copy for themselves, with the tools provided by youtube-dl?
You're assuming a fair use case for using youtube-dl to download a copy of a licensed music video. But fair use is defense to a claim of violating copyright, so you need to show why your use is a fair use, you can't just say "fair use" as if it were a magic spell that makes your legal problems go away. And generally, it would be difficult to prove fair use for any of the content covered by an RIAA license because they make that content available for use offline, time-shifted, etc...they simply require that you pay for that.
The mention of the copyrighted work eg. "Taylor Swift" does not lay out a case of infringement. Merely possessing a copy does not indicate infringement, you could be in pursuit of your fair use rights, with no intention to share. Given the cost of bandwidth and predilection of media conglomerates to meter and limit it, I would argue that there is actually no likelihood of facilitating any substantially infringing use.
The person who took a copy has no substantial reason to share it with anyone, as it is freely available through the content providers. Anyone with a copy of youtube-dl can get it, (does youtube-dl enable the download of any paywalled content? If so, that might be a fact that changes the game. But if so, does the RIAA claimant have standing to make that argument?)
Merely possessing a copy does not indicate infringement, you could be in pursuit of your fair use rights, with no intention to share.
Right, but you're looking at the wrong thing. The use of youtube-dl by you to download Taylor Swift is not what the courts are looking at (and note, that would generally not be fair use if your intent was just to watch it later as the time-shifting defense from the Betamax case is generally not applicable to content available on-demand, though using the video in a derivative work like non-profit educational content would probably still be fine).
It's the fact that youtube-dl holds itself out as being the tool to use so that you can download Taylor Swift that is at issue.
The person who took a copy has no substantial reason to share it with anyone, as it is freely available through the content providers. Anyone with a copy of youtube-dl can get it, (does youtube-dl enable the download of any paywalled content? If so, that might be a fact that changes the game. But if so, does the RIAA claimant have standing to make that argument?)
It doesn't matter if they intend to share the video further. The copyright violation act is the downloading of a permanent copy of video content provided on a streaming/on-demand basis. The downloader sharing the video with others would be a separate copyright violation.
This case is going to be really interesting if it goes to court, but right now it's not in court.
The letter makes two claims, "copyright infringement" which might be substantiated by the readme, (but not against youtube-dl authors, perhaps against their users) and "anticircumvention [sic]" which is the meat of their real issue.
The making of a copy is not outside of fair use unless it fails the balance test, aka "four factors."
Sony Betamax disagrees with you, if we can agree that youtube is similar to a broadcast medium and that youtube-dl is similar to a "VTR" from that case, aka VCR, unless there are other substantial differences that I'm missing.
Making a copy is only infringing if it isn't for fair use, and Betamax ruled that time shifting could be fair use.
One of the four factors is market impact, so how is the market for this content impacted by this taking a permanent copy? It would be impacted if the purpose and character of the copy was inconsistent with fair use, but remember youtube-dl hasn't taken or shared any permanent copies.
So unless you think that youtube-dl has made a copyright violation (which I think we've established they haven't) then youtube-dl is Sony Betamax, permitted to sell VTRs as long as there are substantial non-infringing uses, and the copyright claim will have to be brought against the infringing users.
That does not mean the courts won't find this is an "anticircumvention device" or will find that the takedown is improperly executed. They may very well rule it is an illegal anticircumvention device, Betamax happened before DMCA, and didn't decide anticircumvention.
But to my knowledge, in Sony one of the opinions spoke about "jamming" with hypothetical language, stating that it could be possible for Sony to build a box that jams unauthorized copying and I'm not aware of landmark cases that would have solidified those concepts.
If RIAA has accurately characterized the key rotation mechanism in YouTube then youtube-dl may well be ruled a circumvention device and that could be the end of it, fair use or no.
I would hardly call this a simple slip-up. It is known that the software could be used to infringe copyrights and other open source projects make it clear that they do not support copyright infringement even when it is clear that their software can be used to do so. (If I recall correctly, Kodi and Calibre are two examples.) Meanwhile, youtube-dl has a test for that specific use case.
I feel that is rather thin legal grounds, if the examples are what dictate legality. The fact that I can change some text that does not change the function of code, or what can be done with it, to suddenly make it more legal does not sound like very great legal basis.
I don't know whether I agree that it should be thin legal grounds for a couple of reasons, even though I do agree that changing a few lines of text that doesn't alter the function of the code makes the argument sound sketchy.
Here's why I am not sure whether I agree:
The text in question is described as being part of a test. It is highly suggestive that at least one developer wanted to consider cases where the rights holder may be more assertive (e.g. with potential protection mechanisms), which implies intent. Granted, I don't know what the actual intent was. Only the people who added that text and accepted the commit can know that.
Intent is important when laws are broken. In the minor instances, it may determine whether the law is even enforced. In more significant violations, it may be considered when evaluating legal recourse or damages awarded. While I am uncomfortable with the law being fuzzy, I am also uncomfortable with it being absolute. The latter is especially true when you consider that it is far too common to create laws that protect singular interests.
not to mention its a console cmd and works well in scripts. i used it for a lot of sites that have their videos free but i used a console browser and used this in a script that i could call through the browser. i never looked at how it worked or what i could do with it in a non legitimate way but i wonder if i did unintentionally. i wonder if its the download part that is the issue though for some sites can have free to watch but might have issue with downloading funnily enough screen recording does exist.
I'm not a lawyer, but I am playing devil's advocate here.
Did your customers own those video files or the rights to the video? If they are the authors and owners of the content surely they uploaded something to YouTube to begin with. Why is that not what they uploaded to your service? If they preferred to import YouTube libraries clearly YouTube was adding some value there.
> Did your customers own those video files or the rights to the video?
Not sure why that's relevant?
I often use(d) Youtube-dl to grab 1080p videos to watch once, not to keep them. eg as an alternative to Firefox
That's because YouTube itself recently seemed to change something about their streaming, such that some 1080p video's now stutter and don't work correctly.
So, I download them to a temp directory then watch with VLC instead. Then batch clean up the temp directory when it's getting full.
eg Youtube-dl is just another Youtube client, no different from a browser. If you're saying that watching media via Youtube-dl is different than watching it via Firefox... to me that sounds incredibly bizarre.
A video streaming service is literally a host for video content + UI's for accessing it.
Whether YouTube internally stores those video's as single files, as multiple versions of a file, as chunked pieces, or whatever... who cares? They'll obviously optimise their backend storage for their particular needs.
Whether you start viewing in the middle of a video, or from the start... are you're trying to say it makes a difference?
Because VLC can seek around a video too.
With YouTube-dl, I download the video, and watch it. At some point, it gets deleted.
With Firefox, I download the video and watch it. At some point, it gets deleted.
Are you saying it makes a difference whether or not it gets assembled into "a file" on the receiving side in order to watch it in an appropriate player?
With firefox, you can see the ads that pay for hosting that content you are interested before, during and after you see it. I don't know how enforceable is that you should watch some content exclusively with the provided frontend, but it really makes a difference for them how you watch it.
And you see that in the downloaded version as well whenever it is part of the video. The fact that youtube implemented this differently for some of their ads is their problem, not mine.
That is like complaining that you aren't allowed to view a webpage on a kindle because the ads are supposed to be viewed in color.
Transcoding a video is making a copy of a creative work. Ergo, by definition, copyright applies.
In fact, if transcoding a video added anything creative to the process, you would have two copyrights: one for the original creative work, and a second for the derivative (transcoded) work.
You missed it. OP has rights to the work. The question was whether downloading from Youtube breaks any laws. Youtube's add is transcoding, which is not a creative transformation. Ergo, OP probably has a legal right to download from Youtube, at least as far as copyright law is concerned.
No, I saw that. I was responding to the immediate parent, not the OP. The comment I was responding to was whether transcoding is an act covered by copyright, and it is.
The OP's comment was different. He was using youtube-dl to download videos uploaded by his own clients, which was fine because they're the copyright owners. Transcoding doesn't generally create a separate copyrighted work because at least for these types of media, the underlying representation of the bits doesn't matter.
Note: this isn't fair use. Fair use is a defense to violating copyright, and a copyright owner can't violate their own copyright ...but if they licensed one or more copyrights to a third party, they could violate the third party's copyrights depending on the terms of that license.
Yes I am aware that the bits are not what is copywritten and I am not suggesting Youtube has any right to the content itself. But using youtube-dl to download content from a competitors site is taking advantage of the functionality on that competitors site to add value to your own product.
It could still be in Youtube's interest to prevent this from happening.
I'm asking why you would expect a competitor to make your own product more compelling for your customers.
This is a further example that Youtube-dl is there to circumvent the intended functionality of Youtube.
> It could still be in Youtube's interest to prevent this from happening.
And in fact it is illegal for YouTube to lock your data within their service in that manner in the EU. You have a right to export your data and they have the responsibility to make it make possible to move that data to a competitor where technically feasible. And it clearly is technically feasible.
Do they have an obligation to export your data in a format you choose with a method of your choice or can they make that determination for themselves? Does the EU mandate the ability for YouTube-dl to exist?
There’s a lot of talking past each other going on in this thread. Nobody is defending the RIAA or DMCA. But they exist and this outcome seems painfully obvious.
RIAA being mean, DMCA being bad and copyright being outdated doesn’t matter here. What matters in that the law exists and YouTube-dl made it really easy for the RIAA to make a compelling case against them.
I think the law made it really easy for Google to make that case. I don't think the RIAA has legal standing here under DMCA.
Google isn't making that case because Youtube is YOUtube. The whole point is that it's a platform for family videos, amateurs, and all sorts of other things.
If the RIAA didn't want their content Youtube-dl'able, they should have used one of their locked-down platforms. They went to Youtube because the locked-down corporate platforms don't have the eyeballs. Now, they're trying to convert Youtube into one of those platforms.
My expectation is the RIAA will prevail, but because of deeper pockets and the potential for a multi-million dollar legal battle, not because they're on solid legal ground.
I understand that as well. I am saying it is possible to imagine a scenario in which someone looks at Youtube-dl as something other than a totally harmless aid to users.
Youtube has legitimate reasons to try and prevent people from downloading content from their site. Youtube-dl is clearly there to enable people to do that. Rightsholders can use this as another argument that Youtube-dl violates (or is designed to violate) the DMCA.
I'm not defending the RIAA or DMCA here but I can understand their argument and why they are making it.
I'm not sure what the line of thought is supposed to be here. Youtube also has legitimate reasons to make sure people watch their videos rather than their competitors, but that doesn't mean they can sue me for watching Vimeo.
Of course not. But what if Vimeo is using YouTube to host the videos? The point I am making has nothing to do with copyright. It has to do with leveraging a third party tool to make a competitors product an advantage for yourself.
And in your example they should be suing Vimeo. If we were competing hot dog stands and I use a hammer to break into your cart and steal your family mustard recipe, you don't deliver a notice to Home Depot.
Your analogy makes no sense. RIAA is arguing YouTube-dl is a tool designed to download copywritten material from YouTube because YouTube-dl included test cases in their own code for downloading copywritten material from YouTube. The existence of other streaming sites or other functionality of youtube-dl is completely irrelevant. YouTube does not need to be a party to this, the RIAA is just connecting the dots to make their own case. Their claim is that YouTube-dl is a tool for downloading copywritten material from YouTube because the creators of YouTube-dl literally tested for that in the codebase.
It’s a pretty easy case to make. Any other use of the tool is again, completely and totally irrelevant.
To be even more clear I’m sure YouTube-dl is a useful tool and I think such things should exist. However, this is an important lesson when making and owning these tools. Don’t do the RIAAs work for them.
Some people use YouTube as their repository. Or if they lost the original files it would be a way to recover something. I once had to download mp3's of my own music from MySpace because I had an HD crash and lost them.
I wondered when this would happen. I'm. not referring yotube-dl specifically but the third-party repository problem such as Github and YouTube where material exists principally on one site.
The fact that the RIAA is involved makes it high profiled case and should warn people that distributed systems/repositories are a much better (safer) idea.
I too offload my personal vidos (family/kids) to youtube from my iphone. I used to back them up on a Hd but it has since crashed so whats on youtube is basically my sole backup. If youtube dl goes down I’ll have a hard time retreiving all that
I stopped sending my data to YouTube years ago for privacy reasons, so I have multiple HD backups. External drives are cheap now. If you use three drives you've redundancy and two of the drives can be second-stage/downstream backups so the drives can be configured so as they're used intermittently, thus they get very little wear and remain reliable.
Sure that is perfectly reasonable. And the fact that YouTube is a resource for this is one of its competitive advantages. So it makes sense that YouTube might make it hard for other parties to take advantage of its position as a repository. Thus Youtube-dl is created to circumvent this design choice on the part of YouTube.
youtube-dl scrapes the website, from what I can tell. The API has rate limits that youtube-dl would bypass in a few minutes if it were to use the official API.
That's primarily what's got the RIAA's panties in a twist, is that youtube-dl is 'bypassing' youtube's protection measures to prevent their site from being effectively scraped.
Still can't understand the logic, the website is open! If the information can get to my eyes and ears I can put a recording device in-between. At the end of the day the video is being played on my computer. The only logical endgame, if stuff like this allowed to stand, leads to general purpose computing being outlawed.
It doesn't matter how much value YouTube adds. It neither owns, nor does it assert that it owns, the copyright to these videos. Banks provide a value-add service for your money. They don't own your money. Value-add is not a valid legal test for copyright ownership.
The question here isn't whether youtube owns the videos, the question is whether youtube's use of anti-scraping measures constitutes DRM that, by circumventing, violates the DMCA.
Right, and again, I'm not saying Youtube has any copyright ownership here. I'm saying they provide a service which adds value and as a business they may want to protect that competitive advantage.
It's not even clear that youtube-dl vs watching in the browser is any different from watching on tv vs using your vcr to record which has long been legal.
RIAA already went after YouTube. That’s why Google added the ability to scan for copywritten material. Google wanted YouTube to be a friendly place for people to view content. That meant playing ball with RIAA.
Napster wasn't merely a tool it was a centralized service that provided an index of infringing files and where to get them. It both directly assisted in the act of infringement it profited from same.
You used the words "unintended side effect" in quotes but I am unaware of where that comes from while I am familiar with the term "substantial non-infringing use" and "contributory copyright infringement"
Youtube-dl neither assists nor profits from copyright infringement and it possesses arguably non infringing uses.
- You can download non infringing videos. Youtube-dl works on a variety of sites beyond youtube
- If you feed mpv a url it will transparently use youtube-dl to handle fetching the media for playback. Unless you specifically tell it to this does not permanently save the video and is not materially different from watching the video on firefox.
Mpv incidentally uses far less resources for decoding video even with newly added hardware decoding in linux.
- You can consume the same video you are allowed to access on a different device or in a situation wherein you lack network access. For example one could watch and then delete a youtube video one wanted to watch on the train where you lacked internet access. This is analogous to format or time shifting which have been deemed fair use.
Can't it be trivially reinstated then by removing any references to copyrighted content? youtube-dl has plenty of legitimate uses beyond just copyright infringement.
Plus they've advertised themselves as having that capability. I suspect that even after the removal the RIAA will argue that the fact that the ability to download copyrighted material, which is something that the project itself said it could do in the past and has not been modified, makes it continue to be illegal.
I don't think that's quite how it works. It's not (generally) capability that matters but rather intent.
The RIAA would of course argue that examples of infringement in the test cases or readme demonstrate intent. A reasonable response to that might (or might not, depending on the context) be that infringement in those specific cases was never intentional but instead purely by accident.
If the infringement in this case ends up appearing to be intentional, it would probably make for a very uphill battle to argue that the tool itself was only intended for legitimate use cases.
Edit: Of course, it's reasonable to ask - if it's legal for YouTube to distribute the content, does using youtube-dl suddenly make it illegal? Is it a violation of copyright to record a pay per view stream? What about a publicly available stream paid for by ad revenue?
Well that's the question, isn't it? Is downloading those particular URLs infringement if the content is legally allowed to be hosted on YouTube in the first place? If so, was the use of those URLs specifically intended to demonstrate or verify the ability of the tool to infringe copyright? Alternatively, can the tool be said to circumvent a protection device under DMCA section 1201?
(For the record, my answer to all of the above is an emphatic "no".)
And would a "derivative work" that happens to use "some" open source code from youtube-dl, but that never included a URL to a Taylor Swift song anywhere in the code, be considered to have a different intent?
I think this is actually an interesting question. Someone could fork youtube-dl to create "public-domain-dl" which has multiple references in the README to the fact that it is only intended for downloading public domain videos from YouTube (and elsewhere).
Instead of a unit test which successfully downloads a copyright-protected video, it would have a unit test which attempts to download such videos but returns an error message to the user based on a hardcoded blacklist of videos IDs, stored in a separate config file. (It would also have a unit test for successfully downloading a public domain video from the developers' own channel, of course).
The developers could also make clear that they are happy to receive DMCA requests to add specific video IDs to their blacklist. As for what happens if the user deletes the blacklist config file, maybe that won't have a unit test.
If such a fork was successful in fending off court cases, though, it would start to raise interesting First Amendment questions. The difference between the two pieces of software, in practice, is just the text in the README telling people not to break the law (plus a single "Delete" button press after installation, which the user would have to learn about from another source). This would mean that the difference between developers complying with the law and breaking the law is including that text in the README, which effectively seems like compelled speech.
> would a "derivative work" ... be considered to have a different intent?
Probably not. If intent were to be demonstrated in court, a derivative work would almost certainly be tainted in turn unless those authors had a _really_ good justification for their actions. (IANAL though; I'm just guessing based on other copyright cases that came up in the media before.)
For example, imagine forking Napster back in the day, redoing the UI, and rewriting half of the internals. Do you really think a court would let that fly? Judges are hardly idiots.
That being said, why not just mirror the original to a host running as a tor hidden service and continue all development efforts there?
My guess is that the answers to the questions is likely "no", "it'd be a hard case for youtube-dl since their lawyers are probably not that great" and "no", even though I wish the answers were "yes", "irrelevant", "irrelevant".
Youtube has a licensing agreement with the RIAA. If they didn't, Youtube would be bankrupt, since statutory damages for copyright violations are $750/violation and there's no legal defense once they show the violation occurred.
(And as someone who has dealt with the music licensing agencies, you always just pay for the license. Paying the big 3 licensing agencies annually for millions of streams cost less than the statutory damages for a single violation.)
No the DMCA says that so long as they respond to take downs they aren't liable. The agreement prevents litigation that COULD result in a judgement that might modify this deal which is clearly a risk in addition to the cost of ongoing litigation.
Youtube has the right to stream those videos, because they pay the RIAA for a streaming license, which is a thing that music licensing agencies have provided for many years now. In many cases, the videos were uploaded by the recording studio itself, and in those cases presumably Youtube isn't paying a licensing fee because the license is implicit in the upload (but note that many videos uploaded by the artists themselves are not technically theirs to upload because the actual rights were held by the recording company, hence the reason Youtube needs the agreement with the RIAA).
The DMCA take-down exemption you are thinking of is a separate protection, that applies to Youtube taking down videos that aren't licensed by them containing music that isn't licensed by the creator of the music.
The statutory damages would apply in the former case, such as if an artist uploaded their own music video and Youtube didn't have the broad RIAA license. This happens a lot more frequently than you would think.
You seem to have a lot of legal theories that are based on your own understanding with no citations in cite. I suggest you do some research and either modify your opinions or add citations that show everyone else is wrong and you are right.
The DMCA only applies to the USA. In my opinion it'll only take days if not hours for the files to appear on a website in Eastern Europe, somewhere that the RIAA can't get at.
If that happens, the difference is that these are public domain non-copyrghted materials -- not the copyrighted videos, thus stopping access to the files will be more problematic.
The issue with the readme infects the rest of the code, even if it's removed. It's still evidence that the repository was intended to facilitate copyright infringement. The problem isn't the words of the readme but what those words imply about what the authors of the code intended.
If they instead had released it and then said in a public forum "check out my cool code for copyright infringement" (but had a totally blameless README) that would be used as evidence in the same way.
Equally, then, couldn't another author fork the code and distribute it under a new name, with the offending test removed and a blameless README that says "please don't use my cool code for copyright infringement"?
It sounds like you're saying the problem is with the original authors, not the code itself, so taking down the code seems like the wrong approach for the RIAA.
What does it matter if I play the beatles on youtube by watching in a web browser or watching an .mp4 file that I just downloaded? It's functionally the same.
The intent matters. Browsers don't make it easy to get ahold of a copy of the file that you can share, youtube-dl does. Add that to a bad README and that's something that a court might treat very differently from a web browser.
This is not far off from how it's legal to carry lockpicks but it's often not legal to carry lockpicks around with the intention of using them to commit a crime. Either way you're carrying the same lockpicks, but if the court decides that you were carrying them with bad intentions, you're in trouble.
But it's perfectly legal to screencapture a video platform in full-screen, and previous courts have ruled that recording a stream you otherwise have access to is allowed (the VCR/TiVo lawsuits). The question here is whether youtube-dl is a tool that allows for the bypassing of DRM, as the RIAA is asserting that youtube has DRM on their videos that prevent automated tools from scraping the website.
> The intent matters. Browsers don't make it easy to get ahold of a copy of the file that you can share, youtube-dl does. Add that to a bad README and that's something that a court might treat very differently from a web browser.
I can't say for YouTube specifically (I haven't tried, I suspect they have the talent to make it actually difficult), but browsers do make it remarkably easy to extract most forms of media from a website. Even websites that attempt to hide it have to embed it somewhere. Whether you feel like it's easier to install Firefox and figure out how to extract the media, or figure out how to install Python and pip and then run youtube-dl is up to you.
There are likely even tutorials up by Mozilla somewhere about how to use the dev tools to pull an image (though I assume they're not stupid enough to do it on material they don't have rights to).
There are many reasons one might want to use youtube-dl. Furthermore, there are many creators that either don't care or are happy that you're downloading their stuff.
If we want to make analogies, every gun shop in America sells guns and human shaped targets. Do they have the intent to encourage people to murder other people? It is a tool that can be used for illegal purposes. They might even have examples of how you can do such a thing (as do gun manufacturers, lockpick manufacturers, security exploit announcements, etc, etc). Why would that make the tool illegal? The argument might hold if the only possible use of it is illegal; that puts it among the ranks of things we deem illegal to merely possess, like fully automatic weapons. I'm not buying the RIAA's argument that youtube-dl is so dangerous to society that we can't trust anyone to use it legally.
> This is not far off from how it's legal to carry lockpicks but it's often not legal to carry lockpicks around with the intention of using them to commit a crime.
No one has demonstrated intent. The publishers have demonstrated that it could potentially be used in an illegal manner (depending on your jurisdiction). They aren't going after someone who downloaded youtube-dl and is trying to use it to pirate things. They're going after the lockpick manufacturer because they have a tutorial on using their lockpicks on their site, and people could use that to commit crimes.
YouTube uses things like DASH, where they download pieces of the video from the server a bit at a time and feed into the browser's video pipeline. There's no single link to the entire video, necessarily; you have to piece together the bits. This is one of the things that allows changing quality mid-video, btw.
Furthermore, the video and audio are served separately so that codecs can be mixed and matched on the client side, and the same audio can be used for different quality video streams, etc. One of the things youtube-dl deals with is grabbing both and muxing into a single container.
So yes, extracting things from YouTube is not trivial at all.
> This is not far off from how it's legal to carry lockpicks but it's often not legal to carry lockpicks around with the intention of using them to commit a crime.
This is pretty far from lock picking tools. The crime commits with lock picking tools involves physically breaking into someone private property to either steal physical items or do physical harm to people. Breaking and entering and copyright law are not comparable. A closer analogy is smuggling a camera into a concert to break copyright law by recording a concert. Canon or Nikon are not responsible for what I did, just because they made the technology that allows users to record any content, which may or may not include copyrighted material. Even if Canon included how well their camera performed at recording concerts, that doesn’t suddenly make them responsible. Youtube-dl is much closer to a digital version of a camera than to lock picking tools.
The former gives money to the original content owner for every listen while the latter does not. Which is why you're able to listen to it on youtube without having to personally pay someone.
Sony Corp. of America v. Universal City Studios, Inc., 464
U.S. 417 (1984), also known as the “Betamax case”, is a
decision by the Supreme Court of the United States which
ruled that the making of individual copies of complete
television shows for purposes of time shifting does not
constitute copyright infringement, but is fair use.[1][2]
The Court also ruled that the manufacturers of home video
recording devices, such as Betamax or other VCRs (referred
to as VTRs in the case), cannot be liable for infringement.
How is downloading something from youtube for later offline viewing ("time-shifting") in any way different from recording a tv show?
The Betamax case was about stuff broadcast over public airwaves, whereas this is a medium that the RIAA barely tolerates, rather than the (ideal) main distribution channel. Seems like a big enough difference to me.
The ruling there doesn't seem to rule out making copies of shows from a cable network, which are not exactly public airwaves in the same sense I think you mean.
I don’t see the fact that the RIAA dislikes internet based streaming as relevant to the analysis. Downloading a publicly available video transmitted over a nearly global communications network is directly analogous to recording a show to tape from a TV signal.
The signal is broadcast (ie not under your control) and so the sole purpose being permitted there is time shifting.
YouTube is an on demand stream. It would be comparable to recording a pay per view movie that you purchased. Is that legal? (The question isn't rhetorical, but I seriously doubt it.)
That would be an interesting argument. I suspect it would be illegal because a pay per view stream is typically time limited. But if the stream itself were still valid while you were on the plane ... ?
"...this is a medium that the RIAA barely tolerates, rather than the (ideal) main distribution channel."
Right, this is the precise problem, and it has to be solved - not by a free-for-all but with proper equitabl copywrite laws.
As matters stand, it's only going to get worse. Say we assume that if somehow both YouTube downloads are made much more difficult to crack AND no downloaders are available, then viewers and downloaders will then use newer tech that's even easier to use to record the videos. With new hi-resonution 4k cameras becoming commonly available, they'll be able to record stuff with still-excellent resolution by just photographing the monitor.
Of course, that still won't deter the RIAA, I can see them trying to ban cardboard covers and jigs that hold cameras and
monitors accurately in alignment.
One could argue that YouTube success is mostly about unlimited access to illegal copyrighted material uploaded by some unknown person in some unknown part of the world
After all the thing it's already on YouTube and on my HD after I watched it
If the videos mentioned in the notice are hosted on Youtube without authorization, then the takedown notice should be sent to YouTube.
If the videos were uploaded to Youtube with authorization, then accessing them through youtube-dl is not an example of the program being used for infringement.
Either way, the purpose of the software is to download anything publically available from YouTube. Its purpose is not copyright infringement unless the purpose of YouTube is copyright infringement.
The monetisation of the content depends on a lot of different factors, many have monetized unauthorized content over the years, many received money from the same unauthorized content by faking clicks and views and many avoid paying YouTube in the form of ads by using ad blockers
I believe youtube-dl users amount to a maximum of a single digit percent of the above (with the digit being between 1 and 2 with 2 excluded)
Someone who is capable of downloading youtube videos can easily block ads and many do, not because ads are bad but because they are both excessive in any form
possible and a malware spreading channel. I do too but don’t bother to download videos because it is still more convent to watch’em
directly on youtube. But it seems those days are coming to an end soon, lets see
It stands up to legal scrutiny, and Betamax case is not applicable.
They have these things called "streaming licenses" these days, that are very different from "download licenses" because streamed data is not the same thing as a downloaded file even if they both use the same codec and are derived from the same source.
This is a wholly imaginary distinction based on a triviality. Streaming IS downloading. Also how is the betamax case not applicable. The user of a VCR isn't "licensed" to record whats on their tv
No, it's a distinction that exists based on the differences in how the video content is consumed.
It is irrelevant, legally, that one implementation of a streaming software may choose to download the streamed data to a temporary disc file, or that some content downloaders can structure the assembly of a partially downloaded file so that (some) content can be accessed before the download is fully completed. What matters is that a streamed file is intended to be consumed contemporaneously with the acquisition of the downloaded data however it is stored on the computer, and that caching for efficiency aside, each separate act of consumption involves a separate act of acquiring the content, whereas a downloaded file is intended to be downloaded once and consumed multiple times.
Also how is the betamax case not applicable. The user of a VCR isn't "licensed" to record whats on their tv
No, they are not licensed to record what's on TV. But the point of the Betamax case was that "time-shifted viewing" by a private viewer was deemed to be fair use because at the time broadcast TV content was transmitted on a fixed schedule and absent the private recording, was not otherwise consumable because many of these shows were not rerun or sold on cassette tape. Thus the court found that the Betamax had substantial non-infringing use (and indeed, that it's primary intended use was thus non-infringing).
However, digital content is provided on demand so there is no need for "time-shifted" viewing, and so the reasoning from Betamax no longer applies. Moreover, many content owners now make the content available for "connectivity-shifted" viewing (aka, away from internet connectivity) via a downloaded content license. Thus, downloading that content from a streaming source is generally no longer protected by fair use.
Consequently, using youtube-dl to download your favorite streamer to watch on a plane trip would probably be fair use because they probably don't make the content available for access-shifted viewing otherwise. But using it to download a music video would not, because the music and video owners make those available for download with a purchasable license. And the problem with youtube-dl is that they demonstrated that the primary intent of the tool was to download music videos, the evidence being that the README and parts of the code explicitly refer to downloading music videos subject to RIAA licensing. Under the Betamax ruling, this would be fine, because there are substantial legitimate uses...but the DMCA changed that and so it doesn't matter if there are substantial legitimate uses if the primary intended use was to violate copyright.
"README and parts of the code explicitly refer to downloading music videos subject to RIAA licensing."
It beggars belief that people can be this stupid. Why the hell would one mention it here? Are they truly that stupid to believe that the RIAA wouldn't see it? Then they made matters even worste by putting it on Github instead of some obscure website in Eastern Europe?
I followed the Napster trial closely. Napster’s argument that it had legitimate use was demolished because it had an ability to monitor the specific use of its service on an ongoing basis. That is, it could see queries from users as they happened. In fact, this ability was at the core of the service since Napster relied on a centralized search index maintained by the company. The court ruled this gave the company a more active role in contributing to infringement than the precedent Napster was trying to use (which involved VCRs - the Betamax case).
The courts remedy (at least at the preliminary injunction phase) was not to shut down Napster but to force it to comply with search blacklists provided by the record companies.
youtube-dl obviously is not a service so had no ability to monitor ongoing use. IMO it would have a much stronger case for legitimate use.
> The fact that copyrighted works were included in the readme shows it was intended for that use
How could that be true? if the YouTube link in the test case was a video of farmer on his truck would that show it is intended for that use? No. YouTube dl is made to download any YouTube videos it has not been made to download specifically Taylor Swift music videos, it just has just been picked as a test case as any other YouTube videos could have been
It's not a problem on a rooted phone, irrespective of what app developer decides or wants. And as I've mentioned, at a pinch, just photograph the screen with another device.
These days, just about anyone can copy anything that the DMCA covers despite any attempts to protect it. The answer is elsewhere, that is copyright laws have to be updated to be equitable to everyone. Unfortunately, it's dinosaurs like the RIAA who are standing in
the way stopping it.
Distributing something that downloads copyrighted content isn't the problem though - the problem is "circumventing a technological measure that effectively controls access".
If the media provided by YouTube were DRM'ed and youtube-dl would be e.g. extracting the decryption key, this would make sense. Is that what youtube-dl is doing though?
From my perspective it kind of seems like YouTube-dl is like a knife, it can cut your food, but it can also be used to kill someone. In the case of YouTube-dl the knife was included with instructions on how to kill someone, so it was deemed a potential "murder weapon".
What if someone sold a car and included instructions on how to run over pedestrians? Should the car no longer be sold, or should the instructions be removed?
My point here is that banning all of something based on the fact that the something could be used to commit illegal acts, when that same something also has legitimate legal uses, is a slippery slope. These days the RIAA pretty much lives on that slippery slope.
Curiously, what do scrapers (aka "readers") have to worry about with this topic?
Eg, i'm making an archiver and reader combination that, for personal use, archives stuff in a Git-like store. Yet, Git (and Git-likes) can also be used to distribute.. so hypothetically i could use this software to scrape and distribute content.
My intention is primarily to make news articles/etc searchable, archived, etc. Yet i'm sure NYT would have something to say about my test cases scraping their site.
I think the recent LinkedIn case established that it is legal to scrape anything which is publicly available (ie no login required). Redistribution would be a copyright violation, but the scraping itself is legal.
I'm not sure what that means for youtube-dl though.
It does, but it's only available for those who have a subscription to youtube premium.
As such, I assume the RIAA will try to argue that it doesn't fall into the same bucket that youtube-dl does, since the method of accessing the site is different (scraping the site, vs a sanctioned API)
I assume that YouTube's licenses with the RIAA covers the Youtube Premium features on their videos. If they didn't, they'd be in violation of RIAA's copyright (streaming licenses are not the same as downloading ones).
You know... I read the Youtube license and I see this:
Licence to Other Users
You also grant each other user of the Service a worldwide, non-exclusive, royalty-free licence to access your Content through the Service, and to use that Content (including to reproduce, distribute, modify, display, and perform it) only as enabled by a feature of the Service.
I am a user of the Youtube service. I read and agreed with the terms, I have watched videos.
Thu I am allowed to reproduce its content. The RIAA explicitly agreed I can distribute it.
I'm not a youtube user, and I didn't agree to their terms of service. I can however plug their URL's into a terminal without actually accessing their web site
"Spitting out an mp4 file that you can copy to another device" is not a service that YouTube provides. That's why youtube-dl exists. If it was a service that YouTube already provided then there would not be as much reason for youtube-dl to exist.
"Unenforceable" doesn't mean practically unenforceable, it means legally unenforceable. The laws of physics permit most cars to exceed most speed limits. Those laws are still enforceable.
Unenforceable clauses in contracts are things that are either contrary to law or otherwise don't fall under contract law. So a clause that says "if you sign this you must give up your firstborn son" is unenforceable. That sentence just says that "if we screwed up drafting this contract, just because you were able to challenge one clause due to being unenforceable doesn't mean the whole contract is void." It's a severability clause.
However, Safari (not Firefox) is not affiliated with Google. Google has no say on how the content provided by the Service is presented. The Service provides a HTTPS connection. Its influences ends there.
> The fact that copyrighted works were included in the readme shows it was intended for that use, and the RIAA complaint will likely stand up to any legal scrutiny.
This. FWIW Grokster is the relevant case law here, not Napster:
Just an anecdata point but I was one of the people who used Napster for legitimate purposes (I used it to distribute music I created, gaining small recognition that wasn’t something I could’ve achieved otherwise with my music and my means and other technologies available). The thing that was disappointing in the fallout was that it caused many years of evasion tactics that made finding a comparable distribution multiplier very difficult. For my own use, I stopped caring about making music for others and trying to find a way to get an audience, and I happily play and write music now for my own joy and amusement, but I hate to think how many artists really struggled to find an audience the same way and came up short
This is exactly the point. All they had to was use their own videos for the tests and readme and the dcma takedown would probably never would have happen. Plausible deniability.
Perhaps the SFLC[0] should be actively seeking out popular Free Software projects and pre-emptively auditing them for legal issues such as these. That must be a more cost-effective (and crowd-sourceable) process than actually fighting a legal case against the RIAA.
No it doesn't follow at all, any more than had the repo owners included a couple of public domain recordings in the repo then the conclusion that the tool was clearly intended to download public domain recordings.
It's hard for a lot of techies to grapple with this, but courts and law are often decided by the intent of the offense. This shows intent, whereas public domain works would not. The difference, in court, is massive.
It's not that it's hard to grasp, we just think it's irrelevant, since plenty of people also have legitimate uses for this tool, and any other tool that allows them to do the same things is just as capable of downloading copyrighted youtube videos.
> since plenty of people also have legitimate uses for this tool, and any other tool that allows them to do the same things is just as capable of downloading copyrighted youtube videos
True, but _other_ people and _other_ tools aren't relevant to the intent of _these_ authors and _this_ tool. _Your_ intent is relevant in establishing whether _you_ violated the law (and thus whether an associated DMCA takedown is valid).
Intent does matter only if there's some action taken, or attempted.
The tool just sits there on github. Only the tool's users actually do download stuff or attempt to.
Also you'd be hard pressed to prove such specific intent from some random testsuite url, added by one or two authors, when the tool has very many authors/contributors and the README/manual for users just has non-copyrighted material sample urls, anyway.
RIAA just tries to make it harder to preserve regularly disappearing youtube content, like war crimes evidence, just to make some people richer on some stupid music. I can prove their intent, because that's what this tool is used for, and they're trying to remove the tool from the internet. /s This is the same stupid argument they're using. They will fail, but why not try to make other people's lives harder, right?
I do hope they fail, but regardless I think your analysis here is completely off base.
The intent or action taken in this case is the creation, maintenance, and publication of the tool itself. At issue isn't the intent of any particular end user, or even the majority of end users, but rather of the authors themselves.
To the best of my knowledge, it simply does not matter how the tool is used in practice. AFAIK, all that matters is the intent of the authors in creating and distributing it.
And that intent only shows that authors like to write code and contribute to such a tool. You really can't show much more from the act itself.
For example I authored and maintain megatools, a tool to download/upload from mega.nz that many people probably use to download the same kind of content that's being the issue with youtube-dl. I have no way of knowing.
I haven't used megatools myself in about 4 years, aside from quick testing prior to release/update. And I never really used mega.nz that much even before. I just wanted to learn a bit about cryptography, and return back to C programming after a few years of just doing PHP/JS, and writing a first mega.nz third-party client was an interesting opportunity at the time. Yet the tool is somewhat popular, and distributed as one of mega clients in various Linux distros.
It's ridiculous to assume intent from some test cases. The only intent I can extrapolate from the actions of authors is that they like to code, fix bugs in other people's code, and want to ease their maintenance burden by having tests. The rest is just speculation.
I don't believe the general principle is limited to either software or tools. It is my understanding that the courts generally operate based on intent, particularly when it comes to criminal law.
(For an arbitrary example, consider the difference between a gas station selling to the typical customer versus someone who asks the clerk for help filling some gas cans and in the process openly admits an intent to use them to commit arson later that night.)
From a practical perspective, it's hard to wish for or imagine a legal system that doesn't rely upon judicial interpretation of intent. An example would be causing the death of another human being. Would you want all four of these incidents to be treated the same from a legal perspective?
- A surgery, which is known to have a 50/50 chance of success even at the hands of an excellent surgeon, goes poorly and the patient dies.
- A serial killer spends six months plotting the murder of his victim before executing them.
- A shoving match breaks out at a bar. Somebody slips, falls, hits their head on the ground, and dies.
- You accidentally frighten somebody by sneezing in a quiet library. They have a heart attack and die.
From a purely logical perspective, these are literally the same thing. A person dies! Realistically speaking, any legal system needs to consider intent.
If the law reached a point where the defendant in all of those scenarios would be found not guilty provided they were wearing a t-shirt at the time saying "My intent is to not kill someone", then we would probably agree that the law is not fit for purpose.
Similarly, if the difference between illegal software and legal software is the value of a random ID in a unit test, or the presence of a boilerplate "Please don't use this for copyright infringement" message in the README, then the law isn't really "promoting the Progress of Science and useful Arts", it is just a gotcha trap for developers who forget to copy-paste a piece of text.
The equivalent from the Prohibition Era would be the warnings on "grape bricks" that told buyers "not to leave that jug in the cool cupboard for 21 days, or it would turn into wine".[0]
If you would put aside your emotions for a second, you would see that this is clearly just an issue of different priorities and values -- on both sides. And the side that has the power has priorities that presumably, given your phrasing, disagree with yours. I understand that can be frustrating and that that frustration might lead you to questionable rhetorical devices, but it won't change the fact of the situation.
No, the court looks to facts to establish intent. It's not possible to look into someone's brain, but courts are very, very comfortable with looking at facts to determine something about what's going on in there.
Crimes like first-degree murder have intent as a requirement. People are convicted of it all the time, and it's based on facts and evidence from before and after the killing.
> The fact that copyrighted works were included in the readme shows it was intended for that use
It's an alternative web browser for videos, of course it was intended for copyrighted works, just like Chrome is. I don't understand your argument, is creating alternative web browsers illegal in the US somehow?
> The fact that copyrighted works were included in the readme shows it was intended for that use
Just because copyrighted works are on youtube and are seen as an example of youtube content does not mean the software was built with the express intent to violate copyright. That just doesn't follow.
I think you are misunderstanding the legal argument. The DMCA Section 1201 specifically prohibits (among other things) technology that "is marketed ... for use in circumventing a technological measure that effectively controls access to a work protected under this title." The example in the README is evidence of this.
The argument is that youtube-dl is primarily used for breaking DRM not just that it could be used for doing so.
it wasn't in the readme, it was in the test suite.
I don't think it would be difficult to argue that downloading the world for the sole purpose of making sure the downloading worked was not an infringement (or, alternatively, was fair use).
Calling the thing youtube-dl in the first place rather than GenericDownloadHelper or something like that could, I guess, be seen as marketing it for a specific purpose.
Sadly yes. Legally this was actually rather stupid.
Giving the project an innocuous name - think of a cute animal that isn't already being used as an open source mascot - and not explicitly mentioning popular artists in the README would have made the RIAA's case harder to argue.
As it stands now, whatever the ethics or politics, legally there isn't much of a defence.
Too late; the code is already tainted. It carries the colour of "intended, marketed and used for copyright violation", and you can't just wash it away by reuploading the repo under a different name.
If youtube-dl incorporates some generic HTTP library (which it presumably does), is that now "tainted" too? If it used the one from Chrome, does everybody have to stop using Chrome? That seems problematic. Also, if that's the case I foresee some epic trolling ahead as people incorporate "interesting" code into their overt piracy tools. I bet some of them even incorporate code built into Windows or macOS.
If not, what stops somebody from taking all of youtube-dl, changing the name and three lines of code, and saying that the removed lines were the ones promoted for infringement?
The law isn't some computer program that you can trick if you try hard enough. If someone can reasonably tell that you just took a program and rejiggled it a bit to pretend it's something else, they are going to come after you regardless and likely be successful when they do so.
"The law isn't some computer program that you can trick if you try hard enough."
I don't know what you're talking about. It happens all the time.
Miscarriages of justice are common. As just one of endless examples, read about how much of forensic science is a joke, yet it passes muster in the courts.
Those things happen because powerful people are involved either on the side of the state or a plaintiff or defendant with lots of money. As a weaker party, you can't make the system work for you so easily.
Generally to do that you have to be willing to aggressively pursue your position and be somewhat ok with being unethical, which I doubt will be youtube-dl's position.
> If not, what stops somebody from taking all of youtube-dl, changing the name and three lines of code, and saying that the removed lines were the ones promoted for infringement?
What that somebody says is immaterial. If they did clone youtube-dl, their clone carries the "meant for copyright infringement" colour, by the virtue of being a clone of a project with that colour, and not a completely unrelated and independent project. It's the provenance and intent that matters. Web browsers and HTTP libraries do not have the "bad" colour, and being general-purpose tools, they likely never will.
> If they did clone youtube-dl, their clone carries the "meant for copyright infringement" colour.
Which part of it? Not the parts that consist of HTTP libraries, apparently? But you can break any given program into arbitrarily many components that are each independently useful as a component of a different program.
In this case the "meant for copyright infringement" part seems to be some of the unit tests. Does that mean the rest of it is fine? Or that the HTTP library part of it isn't?
You need a better way of distinguishing them than just claiming sorcery.
I mean here's a direct quote from your article:
> Most importantly, you cannot look at bits and observe what Colour they are.
So if the same code appears somewhere else, why would you expect to still have the same "Colour"?
> Which part of it? Not the parts that consist of HTTP libraries, apparently? But you can break any given program into arbitrarily many components that are each independently useful as a component of a different program.
Not parts, but the entire thing. Colour propagates through causality. The article I refer to explains pretty clearly about what it means. It's the intent and provenance, not the bits, that are important. If youtube-dl gets classified as illegal, then any trivial modification to it will get the same treatment. Even if you end up slowly replacing every bit of code, if you forked off youtube-dl and didn't change the functionality, that's still essentially youtube-dl.
(You can argue that after enough work done, the ship of Theseus isn't the same ship that sailed into the dock. But the important part is that it's still the ship of Theseus, no matter how many parts you iteratively replace.)
Consider cases like going after someone who took GPL code and republished it as proprietary, or plagiarism, or copyright infringement itself. For the law, it doesn't matter whether or not the bits you have are identical to those of the protected work; what matters is how did you get them. It's the same principle at work here.
> In this case the "meant for copyright infringement" part seems to be some of the unit tests.
In this case, unit tests are evidence that the whole project is meant for copyright infringement. The offending entries serve to establish intent.
> unit tests are evidence that the whole project is meant for copyright infringement
Minor quibble, it's not so much infringement (Wouldn't that require redistribution? Or that the original upload itself be a violation?) as circumvention of a mechanism as described under DMCA section 1201.
(But does _generally_ circumventing a mechanism that is only _sometimes_ used to protect copyright actually run afoul of this?)
People seem to continually be misinterpreting this as copyright infringement, and you are right that it isn't. The fact that you bypassed the viewing of ads changes nothing in this matter.
Otherwise, if we would allow this interpretation, then the entirety of modern internet technology is potentially infringing. This is ludicrous.
Nothing substantially different happens when you view the video in your web browser than when you download it using youtube-dl (mpv, the media player, even wraps youtube-dl so you can directly stream a youtube video). In both cases HTTP requests are made, followed by some processing of the data. Does that mean adblocking software is infringing too?
I don't know, maybe the US has totally lost its mind and this kind of thing would fly there, but certainly not in Europe.
It is copyright infringement (via the argument that ytdl facilitates and encourages others to commit the infringement), which happens to bypass ads.
The rights holders have effectively said "you can watch this for free as long as we get the ad revenue". Theoretically, if there was some way of preserving that ad revenue while committing that infringement, I would assume they wouldn't care about the infringement. They're just using the infringement as a tool to preserve the ad revenue.
What you're worried about is the converse, if there is a way to avoid infringing on copywrite while bypassing ads (which there is, ad-blocking), then there's no infringement to use as a tool, then they're going to want to make ad-blocking illegal. It's not hard to predict that's coming, especially in Europe given Article 13 last year.
I'm actually arguing that it is wrong to claim that a copy is even being made by the mere act of streaming (i.e. transferring the bytes of) a media file and hence you cannot violate copyright by merely downloading something. You only infringe once you distribute the content further.
In fact, as far as I'm aware of, this is also how the situation plays out de facto in most (all?) European countries.
> The rights holders have effectively said "you can watch this for free as long as we get the ad revenue".
The key lies in the word "effectively" here. They may have said and even meant that, but I am unaware of a legal mechanism that would actually allow them to do this (in Europe). The only way I can think of accomplishing this would be to make the content available under a dedicated, bespoke licence, akin to how GPL works, and even then I'm unsure whether it would be enforceable. TOSes, generally, are not.
> It's not hard to predict that's coming, especially in Europe given Article 13 last year.
This is wrong. Article 13 regulates content hosts (in this case, Youtube), not end users. Hence, Article 13 has no bearing on ad-blocking software.
> cannot violate copyright by merely downloading something. You only infringe once you distribute the content further.
Wrong. Copying something, without distribution, is still violating copyright. It's just taken less seriously than distribution. It's the same difference between drug dealers and drug users.
>> It's not hard to predict that's coming, especially in Europe given Article 13 last year.
> This is wrong. Article 13 regulates content hosts (in this case, Youtube), not end users. Hence, Article 13 has no bearing on ad-blocking software.
No, I did not say anything at all about Article 13. Please re-read what I said.
> No, I did not say anything at all about Article 13. Please re-read what I said.
What? You very clearly stated that the content of Article 13 makes it easy to predict that the EU will attempt to make ad blocking illegal in the foreseeable future. (Granted, the response to that didn't make much sense - the current law doesn't have to directly affect end users for us to make a reasonable prediction based on it that laws proposed in the future would attempt to do just that.)
> Wrong. Copying something, without distribution, is still violating copyright.
That really depends on the jurisdiction and context. For example, in the US, making backup copies of materials licensed in perpetuity (ex a movie on VHS) is (always, AFAIK) permitted. Another example is recording broadcast TV for the purpose of time shifting it (ie watching it later), which has been explicitly permitted by the courts here. Yet another example is ripping CDs for personal use, which falls under fair use in the US and is therefore not a violation.
> That really depends on the jurisdiction and context.
No it doesn't. If you haven't legitimately obtained Taylor Swift's Shake it Off, you can't argue the copy you made with youtube-dl is a permitted personal copy, in the US or anywhere with copyright laws.
If you did pay for it, then yes you can argue it's a permitted copy (just not in the UK, which has stricter copyright laws).
>> That really depends on the jurisdiction and context.
> If you haven't legitimately obtained ...
I'm well aware and never claimed otherwise. I very clearly stated that it depends on the context. (It's right there in the text you quoted!)
I was responding specifically to your previous claim that "Copying something, without distribution, is still violating copyright." which was overly broad for the reasons I specified.
Yeah, sorry I knew it was overly broad and should have been more specific. But it was in response to your completely wrong assertion that violating it requires redistribution. I think we're done here.
I like think you are wrong and I have presented my case previously, to which you haven't responded. Nothing in copyright law itself can force you to watch ads while downloading a public video. I am completely sure this is the case in my own jurisdiction. If you want, I would be curious to hear your argument about why you think it does in yours.
This takedown happened because DMCA is a broken, frequently exploited law which allows for illegitimate takedown requests, which you must abide by or risk exposing yourself to legal damage for no reason at all.
> Granted, the response to that didn't make much sense - the current law doesn't have to directly affect end users for us to make a reasonable prediction based on it that laws proposed in the future would attempt to do just that.
You're right. I assumed the OP was arguing that Article 13 itself somehow regulates ad blocking software, which is the only way I could interpret it so as to not be a non sequitur, but in doing so I made a non sequitur myself.
I never said Article 13 bans ad blocking. What I wrote was too difficult to parse and I should have realised that at the time and made it more clear. E.g.:
"It's not hard to predict they (EU and media corps) will want to make ad blocking illegal in future with a new law following on from Article 13." I could have said something more vague like "not hard to predict it given the direction the world is headed at the moment" to make the same point.
> Or that the original upload itself be a violation?
The original uploads are on the artists' channels and are monetised (i.e. when I accessed 2 out of 3 of them, an ad played, so I assume some of the cash the adverstisers paid Youtube somehow wound up at the relevant copyright owners).
No, copyright infringement doesn't require redistribution. In the UK if I buy a physical CD and rip it to a PC, purely for personal listening, that's still infringement (there have been attempts to change the law but they failed: https://www.gov.uk/government/news/quashing-of-private-copyi...)
I was unaware that copyright in the UK was so extreme. That's unfortunate.
The topic at hand, however, is a DMCA action between two US entities (the RIAA and GitHub) and so is purely a matter of US law AFAIK. My understanding (possibly mistaken) was that the courts here had nearly always permitted making personal copies of otherwise legitimately obtained media. In fact, my understanding is that reversing this status quo was one of the primary motivations behind the DMCA; by disallowing circumvention of protection schemes, in many instances it effectively outlawed the tools needed to make otherwise permitted copies.
That's the issue. If you haven't legitimately obtained Taylor Swift's Shake it Off, you can't argue the copy you made with youtube-dl is a permitted personal copy, in the US or anywhere with copyright laws.
If you did pay for it, then yes you can argue it's a permitted copy (just not in the UK).
Which would include the HTTP library and the system call implementations it makes into the operating system etc., and you're back to an intractable mess.
> If youtube-dl gets classified as illegal, then any trivial modification to it will get the same treatment. Even if you end up slowly replacing every bit of code, if you forked off youtube-dl and didn't change the functionality, that's still essentially youtube-dl.
Play it backwards and see if it still works. Somebody forks Chrome and creates Chrome, Pirate Edition. The only difference is the logo and that the third party distributors overtly promote it for copyright infringement. It gets declared "illegal" but it's still 99% Chrome, and Chrome is still 99% it. Is Chrome now illegal? Is the shared 99% of it? If not, how are you drawing the distinction?
> Consider cases like going after someone who took GPL code and republished it as proprietary, or plagiarism, or copyright infringement itself. For the law, it doesn't matter whether or not the bits you have are identical to those of the protected work; what matters is how did you get them. It's the same principle at work here.
Except that copyright actually has some well defined mechanisms for determining which aspect of a work is infringement if you copy it. If you publish a book of poems and one of them is in the public domain, you can still copy that one. And the author of each of the other poems still owns the copyright to that poem, even if they're all published together in the same book.
So how does that apply in this case to an open source project with multiple contributors and components?
> In this case, unit tests are evidence that the whole project is meant for copyright infringement. The offending entries serve to establish intent.
Except that the project has multiple independent contributors each with their own intentions, so "the project" doesn't have any singular intent.
There's nothing fancy in youtube-dl. It's just a bunch of ad-hoc scripts maintained by folks which make it convenient to route the api responses to files on disks. Literally things like pulling html and regexing for certain snippets. In fact it supports many video services, cspan for one. It just dispatches to the appropriate scraper based on the endpoint.
It definitely was very sloppy of them to show examples on actual copyrighted material. Couldn't they have simply put examples of public domain content?
### And add them to TestDownload
-for test_case in defs:
+for n, test_case in enumerate(defs):
test_method = generator(test_case)
test_method.__name__ = "test_{0}".format(test_case["name"])
+ if getattr(TestDownload, test_method.__name__, False):
+ test_method.__name__ = "test_{0}_{1}".format(test_case["name"], n)
setattr(TestDownload, test_method.__name__, test_method)
del test_method
diff --git a/test/tests.json b/test/tests.json
index fd037d818..f6a70f153 100644
--- a/test/tests.json
+++ b/test/tests.json
@@ -11,6 +11,32 @@
"description": "test chars: \"'/\\ä�<86>��<9D><95><90>\n\nThis is a test video for youtube-dl.\n\nFor more information, contact phihag@phihag.de ."
}
},
+ {
+ "name": "Youtube",
+ "url": "http://www.youtube.com/watch?v=1ltcDfZMA3U",
+ "file": "1ltcDfZMA3U.flv",
+ "note": "Test VEVO video (#897)",
+ "info_dict": {
+ "upload_date": "20070518",
+ "title": "Maps - It Will Find You",
+ "description": "Music video by Maps performing It Will Find You.",
+ "uploader": "MuteUSA",
+ "uploader_id": "MuteUSA"
+ }
+ },
+ {
+ "name": "Youtube",
+ "url": "http://www.youtube.com/watch?v=UxxajLWwzqY",
+ "file": "UxxajLWwzqY.mp4",
+ "note": "Test generic use_cipher_signature video (#897)",
+ "info_dict": {
+ "upload_date": "20120506",
+ "title": "Icona Pop - I Love It (feat. Charli XCX) [OFFICIAL VIDEO]",
+ "description": "md5:b085c9804f5ab69f4adea963a2dceb3c",
+ "uploader": "IconaPop",
+ "uploader_id": "IconaPop"
+ }
+ },
{
"name": "Dailymotion",
"md5": "392c4b85a60a90dc4792da41ce3144eb",
One could argue that such a test is used only out of necessity - music videos by publishers are unlikely to have their title or metadata changed, which makes for a good static test.
I agree that they probably shouldn't have done this legally but programming wise, those videos are special (and that's why they are in tests) and looks like only VEVO can upload special videos like that and not a random pleb.
What did the readme say that has no legitimate use? Because even downloading Disney can be legitimate.
LockPickingLawyer teaches you how to do things that could be torts, but there are circumstances where those same actions are entirely legitimate. Tort generally needs the context to show that something is not legitimate; so the same applies here. AIUI copyright is not a situation of strict liability.
Hm, but youtube-dl doesn't break DRM. You can just get the video link from the dev tools panel when you open a youtube page. It doesn't let you download anything you wouldn't otherwise be able to.
DRM is ultimately mostly obfuscation. And access to the video fragments in YouTube is heavily obfuscated.
There's very little case law on what the exact level of protection required to qualify, but I wouldn't want to go to court defending myself offer it. It's very risky.
Have you actually tried that lately? Particularly with a DASH stream? (Not that DASH itself is intended as DRM, but just that it's no longer anywhere near as simple as querying a single URL.)
But what is being circumvented? As far as I'm aware there are no controls put in place that are being circumvented.
Edit: I'm also curious why the riaa would have standing at all? Even assuming there is some protection being circumvented, it's not the riaa's control that is being circumvented.
A german court ruled youtube's obfuscation of video request signatures is an effective technological protection measure. YoutubeIE._decrypt_signature in youtube_dl/extractor/youtube.py bypasses this.
As a philosophical issue, since the youtube-dl code is running the cipher off of the code provided by youtube, just as my browser is, why is my browser not similarly circumventing this protection?
At least with CSS a key needed to be found by means separate from actually watching the DVD and wasn't shipped with the user in the same package as the video itself.
> why is my browser not similarly circumventing this protection?
Because your browser also runs the javascript that displays the ads (unless you've also blocked them, which I think could also be considered a "circumvention measure", IANAL).
If ads we're required, they could certainly not stream a video until the ads have been watched (or at least downloaded and the correct amount of time has passed), they could also insert ads as segments of video without having to transcode all videos for every user, but they don't.
> they could also insert ads as segments of video without having to transcode all videos for every user
That would work in a livestream very well, but not in a video. Imagine everyone getting adverts in the voice of live streamer in the different times of the livestream, and live chat getting time-dilated to compensate, without the streamer itself noticing.
Sorry this isn't really an argument. How can someone not make the argument regarding the browser in court and not have it align with the German court's prior finding?
It boils down to the intention. The intention is to download videos to your computer (as viewable mp4 files for end users) which isn't legal, as they are intended to be streamed (or possibly removed in the future) with ads, stats, analytics, recommended etc.
I definitely don't defend this and I know that this whole copyright and DRM thing is fundamentally flawed by design, but it unfortunately works this way legally.
If it boils down to user intention then you can't also argue the tool is circumventing anything. Either mimicking a browser and working the way google expects any client not written or authorized by them, such as a web browser, to is ok or it's not.
I don't think saving things is in general a copyright violation?
Knowingly and intentionally obtaining unlicensed content is a violation. Unauthorized redistribution is a violation. Saving and copying things isn't (AFAIK) a violation.
Saving things is creating an unauthorized copy, which is fundamentally the basis of copyright. Some territories have explicit allowances for personal copies but many don't.
There are a variety of reasons that you can have a copy of a copyrighted work it a way the copyright holder didn't intend, such as time shifting or media shifting.
And in many juristictions they are explicitly defined, and don't apply to copyrighted work generally, only when acquired under specific circumstances.
Format shifting is explicitly illegal in the UK for example, and timeshifting is restricted to works obtained from a broadcast source by the person performing the copy, and not to an on-demand one, in many territories.
This makes me wonder: if I fork the project into another product without such marketing it in this manner, and BFG away all troublesome uses (e.g. in the tests) the git history, it would then be legal, yes?
I was thinking the same thing:
The next step following this line of thinking would be trying to ban all torrent clients, because they CAN be used to download copyrighted material.
We need to ban radios with tape decks and TVs with VCRs! The audio cassette and the VHS are bringing the downfall of the music industry with how easily they can be used to create unauthorized copies!
i love how dead kennedys literally left one of their cassette tapes sides blank and printed "Home taping is killing record industry profits! We left this side blank so you can help." on it.
Well, following their logic behind DMCA compliant, I guess fiddling long enough with developer's console on Chrome or Firefox would allow you to download potentially copyrighted material from youtube the same way youtube-dl does.
sed s/youtube-dl/firefox/g and voilà, DMCA for Firefox ready to submit...
Let's go further! Let's DMCA the Linux kernel because it runs Firefox/youtube-dl/curl/wget!
The logic behind the DMCA complaint is that youtube-dl is “marketed … for use in circumventing a technological measure that effectively controls access to a [copyrighted] work” [1], not that it “allows you to download potentially copyrighted material from youtube.”
The hell it isn't. A unit test is a bench test for one particular functional unit. It's a check function. If you accept that tests as carrying intent, then I demand every weapons researcher or biologist to be arrested this instant. Clearly they are only out to murder people. That is patently ludicrous.
> If you accept that tests as carrying intent, then I demand every weapons researcher or biologist to be arrested this instant. Clearly they are only out to murder people.
Well, what do you think weapons are for? I’m not saying arrest them but that isn’t really a great example, considering the sole purpose of weapons is to kill or destroy. Using weapons for anything other than killing or destroying is basically a secondary usage.
One of the tests in question extracts the m4a audio file of a Taylor Swift song [0] that has nearly 3 billion views and shows me 2 ads before playing. That's a lot of revenue for UMG, who I guess are a bit unhappy with this mechanism that youtube-dl provides of listening to it without having to watch the ads.
So it's only a problem if the video has a lot of views and ads?
If that's the case, we should ban all Pi-holes, too, as they _can_ be used to block ads.
What if I have YouTube Premium, then I don't see ads, so am I allowed to download via youtube-dl?
> So it's only a problem if the video has a lot of views and ads?
Pretty much, yes. No one is going to hire expensive lawyers to enforce copyright on something not generating revenue, although legally they can.
> If that's the case, we should ban all Pi-holes, too
If Pi-hole is anywhere saying or implying "use us to watch $vendor's content without watching their ads" then yes pi-hole is waving a red flag at $vendor who is now motivated to try to ban pi-holes. If there is a legal action they can afford to take they will.
> What if I have YouTube Premium, then I don't see ads, so am I allowed to download via youtube-dl?
No, downloading is a separate "right" from the right to watching without ads. (Downloading is the first step before uploading elsewhere and literally stealing the ad revenue.) But I think there's a legal grey area if you're watching (streaming) with youtube-dl, without saving the file. I'm sure it's against Youtube's TOS though.
Are you sure you want to say it's literally stealing the ad revenue? I would imagine literally stealing the ad revenue would require robbing the bank or safe where the ad revenue money is stored.
Yes. You have reduced the amount of cash they have and increased the amount you have by the same amount. If that's not stealing I don't know what is.
Trying to say that's not stealing is like trying to say
"Someone hacked into to my bank account and "obtained" my money" is not stealing either just because there was no physical cash involved.
How does it increase the amount of cash I have? I watch the video, without ads, and I have exactly the same amount of cash as before.
It also does not decrease the amount of cash owned by the content owner or hosting company (apart from hosting costs, but that's the nature of the internet and they are willfully participating in it). The only cost involved is opportunity cost.
Yes, you are indeed talking about the opportunity cost. Re-uploading the video as your own (with or without ads) would indeed constitute copyright infringement, but without it, it is not.
I'm not sure this fits the definition of opportunity cost either? I understand why you think it does (because it was money not gained that could have been) but the content producer doesn't have multiple options to choose from here. They expect to have X dollars in their account, instead they have X-Y dollars and there's Y dollars in thief's account, because of the actions of the thief, not because of any decision they made.
The crux is in the expectation: they expect that they will make X in a given day, but an expectation is not a guarantee or a right. They also could have made X in a given day, but sometimes that just doesn't happen due to various factors.
I'm not sure to whom you are referring when you say "thief", but I was under the impression that we were talking about a person watching, but not re-uploading, a Youtube video without viewing ads. This person does not have Y dollars in his account as a result of copyright infringement since they simply watched the video and did not put it up for further distribution.
I really just shouldn't have mentioned ad revenue theft at all in the first place, it wasn't that relevant.
I wasn't saying "people who download are thiefs", I was saying "thiefs start by downloading". Then I had to explain what a thief is, and why they really have Y dollars in their account that should have been in producers account. In my other comment the thief is a separate party from the content consumers (so actually there are 6 parties, content consumers is split into those who watch ads and those who download without re-uploading).
> How does watching an ad decrease the amount of money I have?
There are at least 5 parties here:
· Content producer (spending time and effort making original content that people watch)
· Platform
· Advertiser
· Content consumers
· Thief
In your comment you're Content producer. The advertiser pays the platform who pays the content producer, and the amount they get is based on the number of views (there are other factors, but I think views is the main one). Let's say they're getting X views per day. Then the theif takes the content and uploads it to their own account with ads enabled, and gets Y views per day, and gets paid for that. No one is going to watch the content on the producer's channel a 2nd time just to make up their view stats, so now the producer is only getting X-Y views per day and hence is paid less.
I'm not a lawyer, and even if it was I could never tell you that anything would be "ok" in this kind of situation. But I suspect that it would be better off.
> Why stop with torrent clients? They should ban all browsers, because they CAN be used to download copyrighted materials!
We're talking about an industry that normalized rootkit DRM and persuaded pretty much all hardware manufacturers to implement expensive encrypted pipelines to lock you out from trying to even take a glimpse of content playing.
After a few years of working near this industry I really cannot overestimate how rentseeking and scummy every single part of it is. They will abuse you without a second thought if there's a cent to be made.
All computers with the option to install applications or unlocked/unlockable bootloaders can be used to make copies of copyrighted materials. And it certainly happens a lot.
But then, when secure boot came, Microsoft was forced to grant every owner of an Intel compatible computer the right to unlock it for antitrust reasons (luckily).
So were is the borderline between a legal tool and an illegal tool? Well, lawyers will find out...
In the meantime youtube-dl needs to be distributed some other channel. Which of course might raise the risk of back-doored or otherwise poisoned version floating around.
Why stop with browsers? With enough creativity you can use any network protocol to download copyrighted material, so they should just ban computer networks.
So what does it mean when someone says "he got off on a technicality"?
There have been plenty of cases where exactly that happened.
There's the spirit of the law and the letter of the law, and many are persuaded that when someone hasn't violated the letter of the law, they haven't violated the law.
Judges, lawyers, and juries will vary on this, but in many cases the letter of the law will carry the day, and people will in fact "get off on a technicality".
Because browsers and network protocols were not created with the primary purpose of violating copyrights...
Intent matters in the law.
After after all, two guns can be physically and functionally identical, but if one is purchased to be used in a conspiracy to commit murder then it's evidence of a crime, and the other gun is still just a gun.
They would prefer it if you only used DRM input and output devices that only run approved code rather than general purpose devices that can run any code you can conceive of or download [1]
Same for any kind of information exchange, like speech or the written word. Common sense says their argument doesn't hold water at all. Should courts decide in favor of the takedown that'd just go to show how broken our legal system is. Let's hope not.
And you don't even need a browser for that. Your operating system comes with TCP support and that in itself is enough. (OK, some of them may probably be willing to build in all kinds of restrictions, so maybe they can get a RIAA stamp.)
The next step following this line of thinking would be trying to ban all torrent clients, because they CAN be used to download copyrighted material
Didn't the RIAA put up a considerable effort against torrenting in the early 2000's? I remember quite vividly them going after just about anyone who made music available, even if you owned your own songs and were simply uploading them to a web UI to listen to in the browser (Remember Muxtape?)
Hush, don't leak their master plan! Of course they'd love to just ban about anything that can potentially be used to commit copyright infringement. Of course that includes your web browser, too. Unless it can only visit a list of websites pre-approved by RIAA ;)
Why not just ban computers or even why not jail people who even think about using ytdl? These organisations like RIAA need reality check. Sadly there is no body to stand against their bullying and stiffling the freedom of speech.
EFF takes up these causes sometimes, right? This notice is hollow sabre-rattling, so I wouldn’t worry too much. What can RIAA do if somebody forks the project and hosts it in the Lithuania? Not much. Yell into a pillow, maybe.
youtube-dl needs to be regularly updated as streaming sites add new countermeasures to block it. If those updates can no longer be crowdsourced from a popular, reputable site like GitHub, the tool has a good chance of dying.
The RIAA would absolutely ban all torrent clients if they could. If one advertises itself as a way to download copyrighted material, they would try to pull the exact same thing.
What about chromium? They should take that down as well, imagine what children can see using that thing. `curl`, `wget` as well as gitlab - massive offender, random number generators - one of the biggest offenders, any worst nightmare you can imagine can be produced by it!
Well, we (Lithuania) have a law that works along these lines. When you buy any storage device a part of the price is a tax that goes to IP protection agency. The reasoning is exactly that: because you may store some pirated music or whatever on it. How was this bs passed I have no idea.
This is like the reverse of those common disclaimers on hacking tools and tutorials which claim:
This is for educational use only.
I've always wondered, are courts fooled by such disclaimers? Are their authors untouchable just because they put in some boilerplate disclaimer like that?
As for what was written in some code somewhere in the repo, it could have been written by anyone, even an RIAA plant who contributed that trojan horse to the project.
What makes anyone think what was said there is endorsed by or even representative of the views of the rest of the authors of youtube-dl or is what youtube-dl is for?
God, it pisses me off to no end to think that I'm going to be forced to use youtube's piece of shit, slow, ad-infested, tacker-infested, feature-poor, non-automatable browser interface.
But, after taking a few deep breaths, I think within a year there'll be multiple alternatives to youtube-dl which will all bear disclaimers that they are "for educational purposes only" and that they in no way endorse copyright infringement.
>I've always wondered, are courts fooled by such disclaimers? Are their authors untouchable just because they put in some boilerplate disclaimer like that?
I think the answer is that this doesn't always sufficiently protect them, but these small bits add up. It's useful to be able to point at words written beforehand that could help you in a legal situation. This is what corporate speak is about too and enough people engage in it that it likely does something.
> I think within a year there'll be multiple alternatives to youtube-dl which will all bear disclaimers that they are "for educational purposes only" and that they in no way endorse copyright infringement.
i dont think you have to wait that long. its client side, its open source, people have the code, it will most likely be maintained further, just not on github.
The use youtubeDL for music would probably fit the fair use in Finland. The fair use allows personal copies of legally licensed material but not redistribution of said copies to third parties. It has been used to defend a service where ISP records the specific shows from TV like a VCR and streams them to customers at different time. The ISP:s and representation of copyright holders made a compromise to avoid legal battle, where ISP:s limited the storage duration of said recordings to two years. ISP:s still had service they could sell, and avoid unnecessary legal battle.
I'm not a lawyer. So not expert on matter, but just educated local.
Seems like putting that in the readme was pretty stupid. Intent matters in legal things, making the example infringing undermines the argument that the tool is good and some people are just bad.
> This feels like DeCSS all over again.
I think napster would be the better comparision (and especially napster compared to vcrs)
They did not put that in the readme. The README contains only references to test videos, videos that don't actually exist, and one small-time video (in spanish?) that seems to be an old test video, but I have a hard time seeing for sure.
The source code does contain references to copyrighted videos in the tests, tests intended to make sure that youtube-dl can download the data from videos using the extremely "token" signature scrambling that youtube employs for certain videos. You can see the test cases here:
I don’t see how Napster is more applicable than vcrs. YouTube in this case is the broadcaster, putting content out to a general viewing public, ytdl is a recording device. For Napster to work, YouTube has to be imputes with illegally providing the copy and ytdl has to be the means to facilitate the copies transport.
Napster and VCRs were both accused of being tools to infringe copyright, VCRs won the lawsuit, napster lost. A big part of that related to how napster positioned itself in terms of marketing compared to vcrs.
> it uses examples in the README as an example of that:
>> We also note that the source code prominently includes as sample uses
as far as I can tell these videos are not referenced in the README, but instead in the youtube.py extractor file, which would go against the accusation that they were featured 'prominently'
I clicked on this ready to see some stupidity from the copyright industry but literally downloading from links to copyrighted music in your unit tests?
That's how you give the RIAA a way to take down your project.
-
Actually seeing this made the comments made in the worst faith about how "they took it down because you can use it to download bad stuff, what's next?!?!" seem pretty dumb.
If that was the case Bittorrent... which makes youtube-dl look like a guy slinging tapes out of a van next to Naspter HQ...
The creators of youtube-dl are not distributing the material or inducing infringement by using a link to it in a unit test. I am typically on the RIAA's side,
but they're going to lose this one. If RIAA should be mad at anyone, it is youtube for distributing it without DRM. Youtube really really REALLY should have had their asses taken to the cleaners in viacom vs youtube. I don't know what the settlement was, but it wasn't enough, because youtube still exists.
Here, though, Youtube (Google) have contractual agreements to license the use of copyrighted media on their platform, and which is uploaded directly from the record labels themselves.
The RIAA is claiming that YouTube does have DRM on their videos, which if the court agrees, may be the end of youtube support in youtube-dl.
It doesn't have DRM because youtube download only extracts the direct download link and downloads them. There is no DRM on youtube. Example from the alleged offending link,
You can easily copy the links from the formats into your browser and they will play, you can wget them, anything. There is no DRM there, and if anyone convinced you otherwise, they lied.
What kind of nonsense is that? Playboy did fight people for using it, the eventually let it go because it was one image that wasn't particularly important them. It's literally right there in the article you linked...
And I assume you forgot to link to this other program but again, not exactly a real argument.
RIAA went after them on the use of that link, if other projects (of which dozens exist by the way) didn't slip up like that and are still here, it only makes it clearer what the problem was
"You also grant each other user of the Service a worldwide, non-exclusive, royalty-free licence to access your Content through the Service, and to use that Content (including to reproduce, distribute, modify, display, and perform it) only as enabled by a feature of the Service." https://www.youtube.com/static?template=terms
It is enabled by a feature of the Youtube service.
They explicitly disallow downloading, but it is not enforcable (though that word probably doesn't mean what I think it means... the law probably overrules physics)
Severance
"If it turns out that a particular term of this Agreement is not enforceable for any reason, this will not affect any other terms."
But in that wording they do allow downloading. Features of the Youtube service accessed thought the Chrome browser don't have to be exactly the same as accessed though other browsers and tools, other tools are not prohibited to provide features they can extract and interpret from the received source code and data, they are not obligated to run the code at all or as is.
Ugh, I don't want to get into this Stallmanist "if the server returns 200 it's ok!" tarpit. If you believe that, it's fine.
You probably won't ever actually need to use that defense outside of internet arguments honestly... for all their noise the most repercussions the average person might ever see from infringing copyrights is a scary letter from an ISP.
Good luck if the legal system decides to test your hypothesis though.
This isn't about YouTube's TOS at this point, you're making a copy of a copyrighted video without the consent of the copyright holder
> downloading works protected by copyright without the authority of the copyright owner is an infringement of the copyright owner's exclusive rights of reproduction and/or distribution
First, it's not actually illegal, at least in my jurisdiction and in a great many, to make a copy of a copyrighted work.
Secondly, the author somehow gave permission to YouTube to make the video publicly available and downloadable, and YouTube is perfectly happy to provide to me the download URL.
It's illegal in the jurisdiction that Github and the RIAA operate in?
Laws don't exist in a vacuum, so it doesn't seem like a stretch for my comment to refer to the laws actually applicable here right?
Your second point is just remixing the same Stallmanist POV I call out above.
YouTube doesn't just provide you with anything. You go to YouTube, and you find a link, and you stick it in your unit tests.
The fact YouTube's server replies is neither here nor there in the eyes of the law (ironically Youtube does actually return 402 "payment required" and 429 "too many requests" of they figure out what you're doing)
You're free to make whatever esoteric argument you want, but after realizing they did something as silly as put copyrighted videos in the unit tests, there's not much of a leg to stand on.
Especially when there are literally dozens of YT downloader type projects of Github still up right now that didn't do that...
I can't tell if this is an attempt at a crappy joke or you actually think a) Stallman is not exactly the kind of person to make the argument and b) the overwhelming majority of people who prescribe to that line of though aren't aligned with Stallman in other thoughts on technology
I mean supporters of Elbakyan, when I say Elbakyanism, not Elbakyan herself. Indeed, Stallman also asks for people to take action to end copyright entirely, but he uses a legal tool that twists the law to the opposite of intended purpose, instead of, say, creating a cracked software repository (like Sci-Hub does for scientific articles). Two opposite approaches that have the same intended result.
Ah so you've made up a term for supporters for a person, given them a collective philosophy that doesn't align with their "leader's" much less silly ideas.
My apologies for not divining the tea leaves on your made up term that I guess was not meant as a bad joke, but ends up being one anyways.
I wonder what commit added those three listed examples (from three different music companies) to the README, and when. They're the worrying component as they show intent.
In a dark universe timeline somewhere, the pull request for adding them to the README came from an RIAA employee.
That letter is written by lawyers–trying to explain the specifics of "test cases" versus "source code" is unlikely to be a useful use of space. (Plus, if you can get the entire project taken down, why not go for that?)
Do you know of anything that might be applicable here for arguing a distinction between test cases and actual source code? It's a silly example but bringing a replica weapon through airport security is legal, I imagine, if done to test the security system. From a legal layman's perspective, testing on real data doesn't show intent but is instead good engineering to show that the code is verified for correctness.
The point being made in this takedown is that youtube-dl can be used for copyright infringement and is being used for copyright infringement, and the test cases pretty much do exactly that. (In fact, if you're a lawyer with a bit of an idea of software engineering, you might make the argument that the code is testing the correctness of whether it can infringe copyright!)
As an (hastily made, non-expert) example consider a particular gun called the "PandaHunter 9000". Now, pandas being endangered species and such, and having reports that people use buy the "PandaHunter 9000" to kill pandas, you might consider banning the purchase of such a gun. Of course, the manufacturer is going to say that you can use the gun for something else, and its intended purpose is not to kill pandas, but then imagine you find that they've actually been shooting pandas with the gun to test it. Do you see why youtube-dl has put itself in a somewhat unfortunate spot?
I know my gut reaction to all things IP and copyright (and US) law causes me to lose all rationality, but I'd imagine there's a case to be made that test code is exempt through fair use. I don't think it could be made in this case for the reasons you highlight, but in general as long as the offending tests are a small part of the whole they should be considered separately to the actual code. Like if all my test cases are cracking some DRM then a takedown is probably fair enough, but if I'm using 3 out of 70 plus tests to make sure I handle some YouTube specific algorithm in my tool to download YouTube content then the actual videos I use don't seem relevant. But I get why legally its going to be a huge issue. I just wonder if there might be some case in future where test vs library code is a factor.
Edit: for example in the situation where one of their other tests just downloading a normal video used a copyrighted example instead of a CC example that shouldn't be any different, the content is irrelevant due to it being a test case, it could be any licence, it's just a test, the intent of a test should count.
Without the existence of youtube-dl, youtube itself is necessarily commuting copyright infringement over the a good portion of the CC-By-SA works uploaded to youtube.
(not all of them, since the uploader grants youtube a license... but if the work has copyright holders who aren't the uploader, it applies)
Only if the employee is doing the upload as a function of their job can google have any liability. In any other circumstance google s protected by the safe harbor provisions of the law.
That's some prime rate bullshit. Like saying since I could use Linux to download copyrighted materials, and there are guides around which tell how to do so, Linux should be removed from the Internet.
Also a good reminder - never trust a third party to host your files, always have a backup. And hosting your infrastructure on Github means anybody who wants it can take it down with a single letter.
That's the operative word, because it isn't "like" at all to a nontechinical person. If you explain it as "yeah so I have one tool that literally has 'youtube' in its name, and it downloads videos, also some of the test cases to make sure it works show it work on copyrighted videos" and the other one is "people can use it to watch videos…sometimes? Maybe you can even run the first tool on it? But like a billion people use it for completely different things" you can probably see how this works.
Conversely, the RIAA is making its media available on a known, at-risk platform to attain distribution. They're not protecting their copyright sufficiently, and the copyrights should be revoked.
I can't wait for ML to lower the barrier to entry for music to near nil. Make anyone a vocalist or instrumentalist and hose these assholes.
I'm suggesting that ML will lower the barrier to entry so dramatically that the value of individual songs and musicians will plummet. The back catalog of copyright that the RIAA holds will become a fraction of its value today.
I could be wrong, but nascent technology in this field looks incredibly powerful.
This... doesn't make any sense to me. Are you arguing that songs written by machine learning will become sufficiently good at their "job" that there will be no value in actual humans writing music? And that this will be a good thing?
You wouldn't even need ML. Iirc there was this guy who coded a script that played every permutation of 12 notes in a 5 minute period and then made all the Melodys public domain. Ianal so I don't know if this would hold up in court, but technically that should invalidate every copyright on Melodys after that point in time.
Since there is little to no creative input in merely enumerating permutations, I don't think he has a valid copyright to waive. But the fact that the data set exists might sway a judge or jury away from upholding copyright claims on trivial excerpts of other works.
It seems to me that they are making the claim that this tool is expressly for doing something that is forbidden by the YouTube TOS and breaking the music licenses provided.
Of course YouTube has other videos that are under different licenses so it isn't clear that this is the only use case of the software.
Wait a minute, there's a difference between distributed copyrighted works, and merely copying it for yourself. In France for instance, we have this notion of "copie privée" (private copy), that says we are allowed to copy anything as long as we don't distribute it back. We even pay taxes on persistent memory for the privilege.
Up thread there's also a citation of the Betamax case, which says that it's okay for people to record shows so they can watch them later, and it's okay to sell video recording devices.
This is different from Bittorent, which automatically distribute any content you download. With this too, when you are downloading, you are also distributing, which is a much clearer case of infringement in most jurisdictions.
That's a very common misconception of private copy; the existence of the private copy tax is not excusing copyright violation.
What private copy wanted to cover is more like "I bought a physical CD and I make a cassette copy because my car doesn't have a CD player" or because I want to listen to a mix of my favorite music (so you paid a tax on cassettes and later on CD-R and CD-RW media). This was later extended to "I copy all my collection of music to a hard drive and stop flipping CDs in and out of the player" (so you pay a tax on hard disk drives).
It seems kind of the same to me if the result isn't being distributed again: "I want to view this YouTube video on the airplane when I don't have internet access." (Let's assume no international travel is involved to avoid questions of regional licensing rights.)
YouTube's paid offering in some countries includes this feature on Android and iOS, but for computer users there's no built-in way to do it. Wouldn't it fall within the spirit of the private copying rule for a subscriber to YouTube's paid service to use youtube-dl in this way?
> That's a very common misconception of private copy; the existence of the private copy tax is not excusing copyright violation.
You are wrongly assuming that a copyright violation has taken place. If a country's laws say it's legal to make a copy under specific circumstances, it's not a copyright violation to make a copy under those circumstances.
The issue here isn’t that youtube-dl infringes copyright, it’s that (according to the RIAA claim) its purpose is to “circumvent the technological protection measures used by authorized streaming services.” Even if youtube-dl was tested exclusively on public domain videos, so that the developers never infringe copyright, it could violate 17 U.S.C. 1201 [1] if the RIAA succeeds in proving that it was “primarily designed” or “marketed” for circumventing technological protection measures.
What I haven’t seen pointed out is that this is really Githubs problem. They shouldn’t automatically respond to DCMA. The process should really be passed on to the owner of the repo and make them liable. Basically, defaulting to rolling over to DMCA requests had led to an environment where there’s no way to fight them. Even if I hosted something like YouTube-dl myself, my internet provider could cut me off.
It’s the same issue with deplatforming people, do we want a world where literally you lose the ability to share knowledge others don’t agree with Or in this case, a tool that could be used maliciously
> Basically, defaulting to rolling over to DMCA requests had led to an environment where there’s no way to fight them
That's the DMCA works I thought? When the host receives the notice they have to take down the content then forward the notice to the user, who can then file a counter-claim and then the host restores the content (if they don't take it down they they're liable).
GitHub's DMCA policy[0] is very clear on how to reinstate content. It's not extremely difficult, but you do have to send GitHub a properly-formed counter notice, and you do have to be prepared that the sender of the original DMCA notice may sue you to prevent the content from being reinstated.
actually that it is in the test cases instead of the readme makes it seem worse to me, after all the readme is not addressed to anyone in particular, they needed examples of things someone might do and they used popular videos (that happened to be copyrighted) as those examples.
But anyone running the test cases that does not have rights to those videos will have infringed, and then of course youtube-dl must also run their own test cases and we know they don't have rights to the videos.
IANAL, but regardless, according to RIAA, youtube-dl is circumventing the "DRM" built into YouTube, and therefore they're violating anti-circumvention parts of the DMCA. Therefore a DMCA claim can suffice to take it down.
Perhaps if youtube-dl used different examples (i.e. videos not protected by anti-circumvention) perhaps they could have avoided this.
It's pretty ridiculous. They might argue that a browser is a technological measure to protect a copyrighted work which youtube-dl circumvents since the DMCA is written so vaguely. Cases like this demonstrate why anti-circumvention litigation really has to go.
Except the licensing under which the copyrighted works are uploaded explicitly allow for access via a browser, so no you couldn't. That's like saying that a DVD player "circumvents" DVD encryption, or a key "circumvents" a lock. It's the intended use case.
You misread or misunderstood my comment. I'm saying according to the RIAA, the browser is the technological measure which the command line program is circumventing.
Meh, pretty good claim of fair use. They are just picking a smaller file that unlikely to disappear or move. The fact the file is downloaded and then deleted via a script isn't a substitute for actually viewing the file and has zero commercial impact.
And the take down could have been targeted against the particular files they found problematic rather than the whole project.
And the whole thing is ceded to the public domain. Anyone can remove the examples and unit test, call the code webvid-dl and be golden.
Fair use doesn't apply to DRM circumvention unfortunately. You can't even circumvent DRM for reasons completely unrelated to duplicating a copyrighted work.
From the RIAA perspective it seems clear this tool was created to download copywritten material. You can disagree with the law or think the tool has other valid uses but the intent of the tool author seems clear here.
The author of the tool should have chosen a better example in the tests to at least maintain plausible deniability.
Yes, obviously there are legitimate uses. That’s not the point. The point is the actual codebase of YouTube-dl features copyright infringement as a test case. RIAA is using this to make the case that the tool is designed to aid in copyright infringement.
That seems like a reasonable argument given the evidence and the DMCA. I’m not defending the DMCA or RIAA here.
IANAL but I don't even think DMCA applies. It's not like YouTube-dl is breaking copy protection schemes, at most it is handling anti-abuse schemes. After all, it's not like you can go and bypass Widevine with youtube-dl.
Unfortunately, it is making a copy. These guys also fucked up by "marketing" it for use in circumventing such controls. They should have showed how to pull OCW lectures.
I can understand why it would seem like circumvention, but one usage of YouTube-dl even with the README invocations is so that you can listen to or watch the media in a personal capacity. Not technically any different from how you might using the actual YouTube client, albeit probably in violation of YouTube's ToS. "Copying" in a legal sense might need a little more rigor. (IANAL either, though, so hell if I know.)
Why? youtube-dl is a violation of YouTube's ToS most probably, but does using it to download a copyrighted video necessarily constitute copyright infringement? I have literally used youtube-dl to watch YouTube, in the past; it's handy to be able to use whatever media player you want, including ones that have better scrubbing.
So would using an adblocker, or any extension for that matter, also be a violation?
Another point: If you put your content up for public viewing, you're implicitly allowing people to download the material as that's what browsers do. You are downloading a video every time you go to youtube to watch a video.
I don't think you understand. Yeah, you can sue people for illegally redistributing copyrighted works. However, I am skeptical that you can do the same for people using YouTube-dl to consume copyrighted works. You are downloading the file from someone who has a license to redistribute it, you are just using a CLI utility instead of the page itself. You can't view something without downloading it in some capacity.
I'm not saying there's no possibility this is "illicit," I am saying this is not the same as illegally downloading music off of Kazaa.
I was thinking the same thing. Instead of using a browser to access a website, parse the files given to it, and download the data so that the user can view it, you are using youtube-dl to access a website, parse the files given to it, and download the data so the user can view it.
[Edit: I'm not completely sure how section 1201 interfaces with the fair use rules, but at the very least, a quick glance at the statute (as well as awareness of the First Amendment constitutional underpinnings of fair use) makes me believe the interaction does not entirely eliminate fair use in a context where section 1201 applies. It's clearly complicated.]
The law makes it clear downloading copyright material without holding copyright or a suitable license is usually not legal, but exceptions exist in many countries including the US (where the exception is called fair use).
Some uses of youtube-dl with RIAA-member-copyrighted content very probably fall under that fair use exception, even if other common uses do not. For example, if a music critic wants to use youtube-dl to import a music video into video editing software to produce a review of it, interspersing only a small excerpt of the original video with commentary on it, that's classic fair use and would be an easy win in US court if accused of copyright infringement.
If the actual and as-marketed purpose of covering those copyrighted videos by 3 of 94 unit tests is to make sure that such noninfringing fair uses of youtube-dl are possible with the technologies involved in those videos, I expect that the DMCA claim is invalid. If the actual or as-marketed purpose is to ensure that it's possible to infringe those videos, then the DMCA claim is valid.
That's a question of fact for a judge (in a bench trial) or a jury (in a jury trial). If the more favorable answer is true and credibly defensible in court, youtube-dl might be able to survive a motion for summary judgment, gain support in the court of public opinion, and lead the RIAA to consider settling or dropping the claim.
But if they were indeed trying to facilitating illegal circumvention or infringement, or if they can't credibly prove otherwise in court, yeah this won't end well for their ability to host youtube-dl in the many countries that now have a DMCA-like law.
(Disclaimer: I'm not a lawyer, just a former law student layman who remains a legal geek interested in and relatively informed in these areas. But I don't claim to be authoritative and this is definitely not legal advice. youtube-dl should definitely involve a suitably expert and qualified lawyer if they're going to fight this.)
Pardon i pointed to the wrong case example rather the better one is the RIAA suing Kazaa, Limewire, etc out of existence as they were tools to everyone used to download copyrighted material... 95% used for or more used for such.
Those companies mentioned and or others promoted and or were well aware their users were downloading copyrightable material which is contributory infringement.
This YouTube DL is used for the same thing and probably the same percentage are using it to download copyrighted content.
Not that I pro RIAA ... rather trying to detail the best case example for the RIAA potentially having a case against this tool.
The RIAA and MPAA were suing users of Kazaa who were alleged to have redistributed copyrighted works. These lawsuits were not because someone possessed or redistributed free software source code.
FWIW, they did not. This was misinformation from me, misreading the DMCA. I am not glad that my misunderstanding will now spread far and wide, but I at least caught it within the edit window.
The DMCA is complaining about test cases. See extractor/youtube.py in your local copy.
Worth noting the MPA already tried doing this to Popcorn Time, a BitTorrent client designed to provide a Netflix-like UX.[1] The Popcorn Time devs put in a counter-notice and the repository was back up a few weeks later when the period for the MPA to respond expired.
The same thing will probably happen here because this is not one of the purposes of DMCA takedown letters, period. Even if there are inappropriate test cases or something in the repo, or if they’re correct that youtube-dl bypasses DRM in violation of a different part of the DMCA, it’s still not a valid takedown because GitHub isn’t hosting anything the RIAA/those it represents own the copyright to. The correct way to do this is to go after the lead youtube-dl developer(s) and/or GitHub for facilitating infringement or whatever, but I don’t think RIAA wants to do that because they probably don’t have much/any legitimate grounds for legal claims against them, so they abuse the DMCA to look like they’re doing something.
Edit: for a more concrete picture of what happens next, read GitHub’s DMCA policy.[2] Basically youtube-dl can file a counter notice assuming they disagree with the claims, after that the RIAA has 10-14 days to get a court order or the repo goes back up.
It's interesting how many Github counternotices (e.g., [1] [2]) seem completely justified yet link to repositories that are no longer on GitHub. I wonder what happened.
[1] in https://github.com/github/dmca/blob/master/2020/05/2020-05-0... someone forked a permissively-licensed project; the original author made the project-closed source, then issued a DMCA takedown against the fork. That's clearly bogus: you can't revoke an open source license.
[2] in https://github.com/github/dmca/blob/master/2019/11/2019-11-2... Microsoft DMCAd a project that did something with Windows local licensing keys. I can see how Microsoft would prefer that this project not exist, but I see no infringement. Not everything that a big company dislikes is an infringement of copyright.
DMCA doesn’t give the service provider much room to adjudicate these claims. The intended way to correct bogus DMCA notices is a counter notice. GitHub’s particular policy says they reinstate content 10-14 days after getting a counter notice, unless the claimant gets a restraining order: https://docs.github.com/en/free-pro-team@latest/github/site-...
One of the earlier worries about the DMCA takedown process was that it would be used fraudulently to take down important things right before an election, or during a breaking news window to bury a story. I wonder if anyone has tried that yet.
Those repos have a 404 response, which means the user decided to delete it themselves for whatever reason. Repos taken down from DMCA return 451 (unavailable for legal reasons).
I just used windows-g to record upside down music video. Seems to work fine. mp4 file is in my captures video. Sound is great. How is that acceptable and this isn't?
btw, Popcorn time is a bit different situation. I would say bit torrent is more the problem, or at least the people who upload pirated content.
What is odd though is that it's the RIAA filing suit here and not google. Google has a real complaint, RIAA certainly does not.
It would be like if NYT went after a web client for saving news articles for offline reading.
What’s the difference? The main one I can see is that the RIAA is accusing ytdl of being a DRM circumvention tool while Popcorn Time is just a straightforward P2P infringement tool. That doesn’t make the DMCA notice any more valid.
I guess I’m nitpicking but it’s important that they’re not “filing suit”, possibly because they don’t care enough or don’t think they have a case. DMCA takedown is a sort of dispute resolution process mandated by law, it’s not a substitute for an actual lawsuit.
TOS don't really have any legal power, and you don't even have to accept TOS to use youtube-dl, so I guess the worst they could do would be to deny you service.
To prove tortious interference with a contract, a plaintiff must establish several elements, including that The defendant’s conduct led to a breach of the contract; and The plaintiff suffered damage as a result.
The question would be whether Github users suffered a breach of contract for having any of our repos potentially shut down for a reason that involves a third party's claims of violation of DMCA.
As I recall, there was also an element where the DMCA claimant was protected if they could reasonably believe within good faith that their takedown was valid.
There's also unseen elements at play. If you're publishing semi-anonymously, the counter-claim process can deanonymize you.
Republishing the same content at a slightly different URL is the obvious, cheapest solution.
Very few people have been able to claim damages from false DMCA takedowns, although the DMCA specifically allows for it.
They probably can't go after Github because part of the purpose of DMCA takedowns is that companies which honor takedowns avoid liability for copyright infringement.
Curious if anyone with legal expertise knows if this has legs? They say:
> The clear purpose of this source code is to (i) circumvent the technological protection measures used by authorized streaming services such as YouTube, and (ii) reproduce and distribute music videos and sound recordings owned by our member companies without authorization for such use.
But the "circumventing" is still accessing a stream the user can view anyways, and the "reproduce and distribute" feels like a stretch -- there's no inherent distribution. This isn't anything like a pirating or a torrenting tool.
It feels more akin to when movie studios sued VCR manufacturers for being able to record TV back in 1984 -- and lost [1].
(Also, side note but I have never in my life seen a story upvoted so quickly on HN. 130 points in just 7 minutes so far.)
Also, does the fact that YouTube doesn't supply a download feature constitute a "technical protection measure"?
From the RIAA's point of view, it works to their benefit that a download link doesn't exist, and it may be something they like, but that doesn't mean that's why.
It could just as easily be that a download feature doesn't exist because YouTube wants you to keep returning to their site if you want to rewatch a video.
It would be one thing if some YouTube videos had a download button and others didn't. That would suggest that, on the ones where it's missing, it is missing for a reason, and that reason might be DRM. But as far as I know, YouTube doesn't have download for any videos.
Software doesn't always have all the features that end users might want, and the mere absence of a feature doesn't necessarily tell you why it's missing. Also, it's not some weird, suspicious thing to write software which fills in a feature gap in some other software. (Google encourages add-on software on other products, too. For example, Chrome extensions and Gmail add-ons.)
But, maybe there is some legal reason why this could make sense. Maybe some terms of service or licensing (for video uploaders or for regular end users) says not to download something, which would make it clear that the download feature is missing on purpose.
> Also, does the fact that YouTube doesn't supply a download feature constitute a "technical protection measure"?
My understanding is that basically anything at all, if it is in any way "technical" and shows intent, will be accepted as a "technical protection measure" if you go by what has worked so far.
Much more absurd and blatantly bad faith arguments have been accepted, "conspicuously not supplying the feature" is a very strong case in the absurd world of the DMCA cases.
That is not the argument, though. Your copyright is protected regardless of the strength of your security measures. But it is also, separately, illegal to circumvent these measures. This latter prohibition becomes more far-reaching and has more collateral damage the weaker the security measures it applies to, which is worrying.
Outlawing the methods of committing a crime also (instead of just the crime) requires a balancing act between their legitimate and illegitimate uses, which seems precariously absent when talking about technically laughable “security measures” that can be circumvented by pressing F12.
But the trick is to put a crap lock around both something that can be copyrighted but is unimportant and things that cannot be copyrighted.
Now all legal uses of everything behind that lock are illegal for circumvention reasons.
It's a way to apply the DMCA to literally anything digital. The quality of the software doesn't matter, because it isn't for security, just a legal hack.
The fact that youtube wants people to come back to the site and use servers, miles of wires, electricity, network machinery instead of letting them download videos so they can watch them from thumbdrive just says to me this company is unethical and harms environment. Any business model that forces people to be on the network without any reason other than greed, should be illegal. If you can stream the file, download option should be mandatory by law.
People forget that Youtube is a _business_. The reason they maintain all of those servers and network machinery is to serve ads, otherwise why would they provide that service for free?
How is it possible to legislate electricity caps on google, according to some imagined threshold of "harm to environment"? Sounds like the number of lawyers involved would be the real harm in this scenario.
All businesses run on financial incentives (or what you call 'greed'). How is it possible that profit motive and associated laws that facilitate buying/selling be written off as unethical?
I have YT premium and an android phone so I checked this out. It looks like they don't store a single mp4 or anything and instead store it in chunks. I am not sure though if they are actually encrypted and stored using some sort of copy protection or if you could assemble the pieces into a single video using some algorithm without a special key.
I would guess it’s similar to the chunking they do when streaming in the first place. Assembling the pieces is one of the main functions of youtube-dl.
Youtube does have a "download" feature in YouTube studio. Where you can download a heavily compressed version of any video you've uploaded. But only videos you've uploaded.
The data obviously must make it to your computer. A distinction that can be made is whether it is possible/easy to use it separately, outside of YouTube.
They come as regular media files, the chunking would cause issues for most people but it's easy to view. I don't think difficulty is what is important though, what matters is if they were to need some kind of decrypter from the copyright holder.
> Also, does the fact that YouTube doesn't supply a download feature constitute a "technical protection measure"?
The law is so vague on this point so as to include practically anything. Here is the text:
> a technological measure “effectively controls access to a work” if the measure, in the ordinary course of its operation, requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work.
As mentioned in the notice, the RIAA is specifically claiming youtube-dl's deobfuscation of youtube's request signatures is what's infringing, which a german court ruled to be an effective technological protection measure.
> It could just as easily be that a download feature doesn't exist because YouTube wants you to keep returning to their site if you want to rewatch a video.
Lets be clear though - the only reason copyrighted material is allowed on Youtube is because the owners then grant a license for the content in exchange for ad revenue. Offering a download link severly damages the "owners are paid for their content" part of the equation.
This is true and still applies in the case where you pay for YouTube Premium. Even if you use YouTube Premium you are also helping pay the content creators [1]
> # How YouTube Premium supports creators.
> Creators are the heart and soul of YouTube. To make sure they're compensated for their work, we share ad revenue with them when you watch ads on YouTube. If you're a YouTube Premium member, you won't see ads, so we share your monthly membership fee with creators. Best of all, the more videos you watch from your favorite creators, the more money they make.
So, to reply to the gp you technically aren’t just paying “evil” and “greedy” big corps, but your also helping all the YouTubers.
You are able to download YouTube videos on your phone, if you subscribe to YouTube premium. I haven’t made any deep investigation of this but I kinda assume the videos are protected by DRM.
My argument is that the URL address for the HLS stream you access is not in clear text in the html code youtube sends you. Javascript code is executed to decode it (which changes constantly, hence the need for youtube-dl to be updated constantly) and that is a form of DRM which youtube-dl breaks.
In that case every OSS project is in some way DRM:ed since they require a compiler, interpreter or some specific instruction set to run. That is not at all how the term DRM is used, and if you want to think of it that way you should also know that when speaking to others they have another definition of what DRM is.
As I said it is as encrypted (no less, no more) as all other https traffic. Please note that normal https does no verification of the client, the client verifies the server not the other way around (client verification is of course possible but almost no public sites use it). So the encryption in this case verifies that the content comes from youtube or other sites that it supports but youtube itself does no attempt at verification of the client. This is in contrast to real DRM where the content is encrypted in such a way that it is hard to decode it without running the Content Decryption Module, which are proprietary plugins and that can check HDCP and similar ways to only allow playback on "trusted" devices.
Hmm, so maybe it's legally enough if YouTube does have a protection mechanism and the material is copyrighted, even if the protection mechanism isn't necessarily intended to protect copyright?
The entire IP concept is really hard to make sense of with the web: a browser works by making a local copy of a remote resource and then making that local copy available to the user. I don’t see why, from the server’s perspective, the precise client matters: if I use curl + pandoc to read your webpage, is that really meaningfully different from using Firefox or Chrome?
> is that really meaningfully different from using Firefox or Chrome?
In the USA legally it is because the vast majority of the judges that have ruled on these things think anything that isn't a browser is a hacking tool. Using wget is enough to get you thrown in federal prison for accessing public web resources.
The crime was not that he used wget, it’s that after he was banned from the service he used a server closet he was not permitted to access to continue downloading. Still bullshit but it’s not even close to wgetting a public resource
Edit: no, it’s a private land grant university. What kind of socialism is this, anyway? How is this structure even valid, if not for historical precedent?
Nothing against socialism or even my point, really. Just very odd to see how blatantly discriminatory and contradictory this seems to have a private university performing a necessary public service, with free land from the state. Not that the work isn’t well done, or anything. Just bears strict scrutiny.
Nope, you needed to be on the MIT network. He argued that they should be public, which is very much NOT the same thing as actually being public in the eyes of the law.
I was interpolating, the article implies wget but I didn’t mean to imply I had verified that or anything. I’ll admit I did make a stronger statement than intended and was relying on third party interpretations of the code. Thanks for the clarification!
I think weev may have used wget in his AT&T work where he discovered links or interactions between customer data and iOS in an AT&T subsite?
The true purpose of the DCMA is to control the distributors via the use of tools like DRM.
The fact that you can view music on YouTube at all is something of an anomaly. The recording industry would love to dispense with YouTube entirely if they could.
In the case of youtube-dl, they couldn't do that. At least VEVO videos have an additional layer of "protection" — the direct links to video files require a signature of some sort IIRC. Downloading a non-DRM-ed video is as easy as making a request to https://www.youtube.com/get_video_info?video_id=aqz-KE-bpKQ and then following a link to the format you need, but with those music videos, that won't work. So the test cases were a necessity.
Yes, it's correct and it should return that. The top-level serialization format is simply a URL query string aka application/x-www-form-urlencoded. No idea why but probably historical reasons.
They couldn't have done this. The 'infringing' links were in the test suite and were specifically tests for content from particular sources which had special links which required different techniques to download them.
The test would not have been accomplished if they were pointed at links which didn't have the behaviour that was being tested.
Curious to know if it was not possible for YouTube-dl to create content which was ‘similar’ to the infringing ones & upload it on YouTube for their test cases?
Most of this comment chain has been about why they couldn't do that. They were testing against special features that are only available to select partners.
One solution would be to load those links from environment variables, similar to how it's done with API access keys and other sensitive data. This would mildly inconvenience the devs by having to copy the links to those types of content by hand and set the vars before running the tests, but none of the "infringing" links would be present in the repo itself.
Hi Nullc, long time no see! :-)
And shoot, that is annoying.
It makes for really bad optics though. Gforz's suggestion to upload test video with similar parameters is -in 20/20 hindsight- probably the better plan. Definitely better than giving bad ideas to copyright lawyers.
The smart thing would have been to always filter by CC. And then anyone who can type # could just modify their source code a bit to adjust the filters.
Thanks for doing God's work here. Had to go all the way to the second page to find a copy to clone.
What a ridiculous thing to ban. I've only ever used youtube-dl to grab copies of videos that I'm in but didn't upload, in the event that those videos were to disappear in the future.
The fact that Chinese businesses aren't bound by the Western intellectual property regime is one of their greatest long-term competitive advantages.
It remains to be seen whether the Chinese government will revert to intellectual protectionism once they reach technological parity with the West though.
While its good to get a backup of the source code, youtube-dl is one of those projects that quickly becomes useless as Google mixes stuff around within YouTube, which they like to do. Without an active developer base, the project will quickly become less and less effective, which is one of the big concerns IMO about this lawsuit.
What if collaboration on opensource projects (i.e. hosting, issues and their comments) was decentralized instead of relying on a central entity like Github? That would keep the developer base active and make DMCA takedowns ineffective.
Git seems like a great candidate for hosting through TOR; it's super low bandwidth. I often find myself wondering why DMCA'd fan projects don't just switch to anonymous TOR hosting. Obviously it's not bulletproof, but if it's just copyright holders you have to worry about and not state actors then it seems like a great solution.
In light of this DMCA, this seems like a site that needs to exist...but I don't know of one? Seems like as trivial a build as anything cryptographic actually
They should rename it to open-license-content-dl, paste warnings all over the readme about how it should NOT be used to download copyrighted content, post it to github, and see what happens.
> What if collaboration on opensource projects (i.e. hosting, issues and their comments) was decentralized instead of relying on a central entity like Github? That would keep the developer base active and make DMCA takedowns ineffective.
But decentralisation would also make it harder to verify the code is legitimate.
Would you trust a copy of something like this from an anonymous server?
Despite the project name, "youtube-dl" is a nearly universal video downloader. It contains hundreds of special cases for specific websites, which will gradually break without maintenance. It would be a huge loss.
I imagine someone can re-publish it on Github without it being taken down if they rename it, change the README and/or add some disclaimer saying this tool shouldn't be used to download copyrighted works.
Collaboration to keep it up to date hopefully follows soon after.
I have wondered why Real Player never seemed, over a period of years (some years ago, at least), to need updates to cope with downloading from YouTube, and yet youtube-dl seemed to need regular updates every few months.
It's an architectural difference, but it is unclear what it is. It cannot be because RealPlayer Downloader is a browser extension that provides a "download" button within the WWW page itself and youtube-dl works from URLs given on a command line, because other YouTube downloaders like iTube are also able to download a video given only a YouTube page URL.
Or maybe it isn't a difference nowadays. This was some years ago. But there does not seem to be much talk about having to update these downloaders frequently like youtube-dl.
I would go so far as to say the source code of youtube-dl is less relevant than its existence as a rallying point. The project can be disrupted by attacking its centralized points, but I doubt the general effort can be suppressed long-term.
Youtube is far from the only thing ytdl is useful for. I have a particular hate for youtube and basically don't go there, but still make plenty of use of youtube-dl.
Here's a list of sites that it supports (google cache link because the original seems down, potentially due to the DMCA). It would be difficult to find a reasonably sized site that it doesn't support.
I'm very scared by this. youtube-dl needs somewhat frequent updates as Google moves the youtube codebase around. I'm worried that the RIAA's next move, now that it's starting to get inconvenient to get youtube-dl, will be to make Youtube change in some way to make existing copies of youtube-dl no longer work.
youtube-dl has been my primary way of getting videos since I learned about it. If the RIAA manages to kill it, my ability to partake in culture will be severely limited.
I dunno. Every Youtuber I know makes use of Youtube-dl (or related projects) extensively because many of them don't maintain archives of their own content and Youtube's built-in tools for downloading stuff back from them are terrible.
I doubt that includes every transcoded rendition of every one of your videos. And I don't think they probably store source videos in the original format in most cases? Hard to say for sure.
Youtube used to store original files without even checking that it was a video. This allowed some enterprising individuals to create a YouTube file system. I'm sure that has changed by now.
Under GDPR I believe they only have to give you "Personally Identifiable Information" (PII), aka "any piece of information that relates to an identifiable person".
It seems likely that some YouTube content does not fall under that category.
IMO there's a risk of upsetting the Chrome monopoly and driving users away if they do it in such a heavy handed way.
Also, they would either have to completely neuter their Extensions, or else constantly battle people submitting new adblockers in the same spirit as uBlock.
But if every browser slowly adopts Chromium engine (the worrying trend), then they can make a move against adblockers and competing browsers would have to scramble to remake a competing browser engine to do anything about it.
Well at least if they can hold onto their domain, and then host development somewhere, they'll maintain the ability to redirect updates to a new location without people having to manually reinstall.
Right, but the client is loading "https://yt-dl.org", which currently does a 302 to https://ytdl-org.github.io but could be updated to point elsewhere even if github is uncooperative.
jdownloader.org or .com? The former throws a FILE_NOT_FOUND exception for the Windows version and can't access the SVN, the latter looks a bit sketchy and has no code available, not that it's a prerequisite, just figured HNers would offer up the open-source version first ;)
Cheers! For anyone else looking for the Windows build, here is the link to jDownloader2 builds (which I was only able to find via the forums): https://jdownloader.org/jdownloader2
Not the OP but I’m a heavy youtube-dl user. I live in a rural area where my only internet option is satellite (HughesNet) which is basically unusable for any kind of streaming media. I rent an office in town to do software work and use youtube-dl to download videos for later viewing at home.
This is similar to my use case as well. I just cannot watch a video from Youtube itself, the connection would be lost so many times it'd stop trying after 1% or less. The only solution is to painfully and slowly download it to my system, over time, and hope there aren't cases that destroy the 60% you downloaded over the last 2 days.
If nothing happens to replace or reinstate youtube-dl, a lot of people like you and me are simply cut off from video content. This is pretty much terrible.
Compared to youtube-dl and an offline media player like mpv, youtube's web interface is absolute garbage for consuming content. The only thing it's half-good for is discovery because it shows thumbnails of the videos and links to related videos.
Useful things that I can't do on through youtube's web interface:
1 - archive videos (so many videos have been taken down and would be lost forever to me had I not had an offline archive of them)
2 - quickly play through a ton of videos on demand, offline, without waiting to load the video (and the ads) -- skimming through dozens of offline videos takes seconds, but I'd have to stare at my browser loading forever to accomplish the same thing through a web browser
3 - make use of many useful features of powerful media players like mpv... just yesterday I needed to invert the colors on a screencast because I was watching it at night and the video's white window background was blinding me.. I could do this instantly in mpv, but absolutely impossible on youtube
4 - remix the video or otherwise alter it to my needs using powerful offline video editors.. youtube's offerings here are again a sad joke in comparison (as are most web tools compared to offline tools)
5 - not have to sit through a single stinking ad
If youtube could have just offered simple download links for their videos this would not be a problem.
But, no, they need you to be glued to their website and bound hand and foot to their service for as many hours of the day as they can bleed out of you.
6 - listen to public talks, presentations and soundscapes while doing something else with my mobile device, or letting the screen sleep in my pocket. YouTube requires the video to be on-screen or it stops playing, which makes it completely useless for listening to things. Other video sites are much better for this.
(I don't need advice on how to get around this thanks, I already know how to. But that's another of YouTube's crappy standard behaviours.)
You have a point to some extent, it could be valuable to offer download buttons on a lot of videos. However, YouTube is only as valuable as the content it serves, and the content creators are the ones putting ads in their videos and who would be unhappy if there were download buttons on everything
Not OP, but I personally use youtube-dl to retrieve videos on a remote server accessed via ssh, which then get downloaded slowly over a low bandwidth link for offline viewing at a later time. They may or may not get reencoded using the ffmpeg integration before retrieving as well.
YouTube's web interface is basically useless for me on a slow link, not to mention it's incredibly obnoxious with all its recommendations and other unmanagable propaganda delivery.
Youtube-dl's ability to retrieve titles and descriptions without showing me anything else and before retrieving any video content alone make youtube's opaque hashed URLs usable for me.
Youtube links are shared everywhere, including here on HN.
I also have a small collection of youtube channels bookmarked at their /videos URL, which at least doesn't try play any video and just gives a grid of thumbnails. Occasionally I'll visit those to discover new videos from the creators I'm interested in.
This already consumes more time watching youtube content than I care to admit.
On top of what others said, I also like youtube-dl + mpv because it consumes a fraction of the memory Firefox + one YT tab consumes. My main browser is Qutebrowser where I don't login to Google stuff, for which I use a Firefox profile. So when I'm watching something long like a lecture from any of my playlists, I download it first, quit Firefox, and watch with mpv. If I watch on FF on a large screen the computer starts swapping and I have to go kill some apps.
When I had high packet loss wireless internet, downloading videos was effectively the only way to watch them. Browsers don't buffer a whole video worth.
Comments like this in here seem out of place. We're a community of hackers. Just read the source and figure out how it downloads the videos. Next time YT changes something it'd probably be some query string in the url. It's not rocket science to download stuff from video sites.
Not only do you have to figure out the URLs from the source, but you have to assemble all the parts.
Youtube's website changes all the time, too, so you'll have to constantly re-read the source and adapt your downloader to it (essentially what youtube-dl does).
It may not be rocket science, but it's not trivial either, and not every developer on HN is a web developer or has any interest (or time) to become one.
The removal of youtube-dl is a loss to the open source community. I hope this does not set a precedence going forward and that authors re-establish themselves (and the bug tracker, which had immense amount of information).
At the same time, this lead me to browse the Github's DMCA repo, which has some real gems. For example, this DMCA takedown of repo with copied course assignment of a different student and did not comply with the Apache 2.0 Licence [1].
insane that nintendo is so litigious that they send lawyers to take down fan-made games meant to be patched on Ocarina of Time. What, is this fan game gonna detract from the valuable income you're making on a 22 year old game for the Nintendo 64?? It's at their own detriment...
I remember back in 2008 I read a research paper on what to not do when publishing/advertising peer-to-peer networks in order to avoid stuff such as RIAA. Showing copyright-protected work in your website/screenshots/etc was a big thing. Sadly I cannot find the paper anymore and I don't remember all the advice :(
If someone here with a good research-paper-search-fu can find the paper, it would help help our community a lot. All I remember is that it was from some peer-to-peer conference, and I read it in 2008.
Psst, precedent* :) Precedence is the order of importance in which something occurs (e.g. operator precedence). Precedent is a level of standard to which a secondary action is compared.
---
Also that dude's a fucking legend, DMCA takedown-ing his classmate.
Seems like that student has admitted in the most public and irreversible way possible that they have distributed their coursework online, almost certainly in contravention of academic policy.
Seems like a fresh mirror here https://gitea.eponym.info/Mirrors/youtube-dl to fork and start it over somewhere else. Gitea is a great project. Now we need someone to fork and publish it over Tor or something. Decentralized solution would be a next step.
Diff between that mirror and the one from the web.archive.com looks good. I.e. no hidden/evil things inside. Looks safe to start over.
I will give the main contributors the neccessary access for reviewing/merging/etc.. or will entirely hand over the project if you can prove you are the maintainer.
Considering youtube-dl isn't doing anything a web browser accessing these sites can't do, essentially serving as a headless web browser with a convenient CLI, I don't see how this could possibly have a leg to stand on.
It's like serving Mozilla a DMCA takedown for FireFox.
I however welcome the highly visible reminder that github should only be used as a mirror at most.
There's an obvious difference between a browser that, in normal use, doesn't allow storing of streaming video, and a tool that does and isn't supported by Google at all.
Yes, you can download the full video with a browser. Yes, you can use wget or curl to do that. But youtube-dl's community was dumb enough to give clear cut examples of downloading copywritten material, which is obviously not what the RIAA or probably even YouTube's lawyers want.
Courts care about intent, and it's a straw man to argue that technical similarities mean they're half-assing their enforcement.
You can right-click->save-as the video link in the network panel of dev tools of either Chrome or Firefox. Google's own browser lets you save youtube videos with a few clicks. Also taping TV and radio is legal as well, even though the receiving device doesn't offer that functionality, unlike Chrome.
My understanding is that it only requires you send the notice in good faith, meaning that if you think you own a copyright but don't (because, say, you own too many copyrights to keep track of them) you're still in the clear.
Apparently not, since people get away with sending fraudulent takedown requests all of the time. Now that I think of it, has anyone ever been punished for abusing the DMCA?
> We also note that the source code prominently includes as sample uses of the source code the downloading of copies of our members’ copyrighted sound recordings and music videos, as noted in Exhibit A hereto. For example, as shown on Exhibit A, the source code expressly suggests its use to copy and/or distribute the following copyrighted works owned by our member companies
IMHO this wasn't the best move, I mean... the use of copyrighted music as an example DIRECTLY stated in the repo, as an example to show what you can download with the tool
When the RIAA sued me for operating Aurous a few years ago they nailed me for exactly this. Using copyrighted album art and song names to advertise my FOSS meant to stream music from sources like YouTube didn't exactly win me any points in court.
I doubt there's any "for better" in that. It's an easy bit for the RIAA to latch onto to make their case, and I expect a judge or reasonable person on a jury would make make a distinction between the two, but not enough to matter.
Does anyone have a local copy of the repo? I’m curious when that particular mention was merged into the repo.
Thought - It’s possible that someone in association with the RIAA made a code contribution that included that change for the purpose of creating evidence to file a DMCA.
Yeah, an example downloading a video of Elephant's Dream or a tech conference talk would have worked just as well and imply the tool has primarily legitimate uses
> at least not if you're doing anything that smells of copyright issues
Or lets people communicate. Or broadcasts news. Or can filter messages or news. Or directly applies encryption to anything. Or is related to accounting. Or can be indirectly linked to health services. Or, well, you get the idea.
I'm a contributor to gallery-dl and it occurs to me this exact same scenario can happen there. So I at least set up a cron job to backup the issues in case it gets trolled. Its the only really problematic part to get taken down from Github.
I'm sure the developers have the whole thing on their local machines and it would be terrible if it was uploaded somewhere in a country that doesn't give a squat about DMCA.
"RIAA blitz takes down 18 GitHub projects used for downloading YouTube videos"
aand isn't a DMCA 512 takedown:
Although GitHub classified the RIAA letter as a DMCA takedown request, it is not one. As Public Knowledge Legal Director John Bergmayer pointed out today on Twitter, RIAA isn't alleging the library infringed on its rights, but that the library is illegal in itself.
This isn’t really a DMCA request. I don’t see an assertion that youtube-dl is an infringing work. Rather the claim is that it’s illegal per sehttps://t.co/vQ16nVleCf
Even Google Research themselves use youtube-dl when assembling computer vision datasets. The only way to work on their data and reproduce the results is through youtube-dl, as video datasets are often only distributed as URLs and timestamps, and even the example codes use youtube-dl.
I wonder how this will impact the AI research community if there's some FUD around this tool.
Generally scraping is a gray area. I know researchers who scraped Google street view for large areas to train AI models without Googles approval and got hired by Google for their impressive AI skills instead of threatened.
I know researchers are a tiny group compared to consumers, but it's still interesting I think.
Is there any legislative or regulatory work that is trying to address the gigantic mess that is music (or media in general) copyright and licensing in the US?
The DMCA is over 2 decades old, and seemingly nothing useful has come up since. The current system seems to do not much other than provide a big stick for the RIAA and MPAA to wield whenever they get bored and try to extract rent using law that still seems stuck in some mire of player piano era logic. The last sane system I encountered was when I was doing college radio, where you had a license to play music, were required to log what music you played, and were assured that some clearinghouse would sort out the royalties that needed paying out of the aggregate license fees.
There seems to be mass confusion over what's legal on modern services like Twitch, where music is used in the same spirit as radio (background music chosen at the whim of the DJ/streamer), but isn't legal because it runs up against licensing schemes designed for including music in TV and film productions with massive budgets.
There doesn't seem to be any clear way to handle shit as any sort of small content creator, as the rightsholders seem to want to preserve some weird fantasy land where they're both entitled to complex negotiated rights deals (which make sense if you're say, some massive entity a la NBC, and want to include music in a new big budget show) while also not providing anything for the rest of society (if you're not NBC- or CBS-sized, the people who negotiate rights contracts won't give you the time of day). If you're not one of the mammoth-class media conglomerates, your options appear to be "do not use music ever" or "use music casually, and then be on the receiving end of a massive legal bludgeon". You can't get the time (or music) of day, but if you do somehow manage to get it, then you _do_ get the time of day, but in the form of massive retroactive fees or whatever that you "should" have paid had the licensing cthulu been willing to engage with you before you determined that the rightsholders weren't interested in dealing with you.
The DMCA was intended to give large content publishers a big stick to extract rent from third parties without needing to do any work. It is functioning as intended and is very unlikely to be reformed to favor the public interest.
If anything, the next DMCA will be tilted even further towards publisher interests. The latest EU publisher payout copyright 'reform' -- which, among other things, banned photography of buildings and skylines -- is the most likely model for the next US copyright 'reform' measure.
Congress only passes laws that large piles of money pay for[0], so the only prospect of copyright reform is if someone puts up a billion dollars in campaign contributions (bribes). Further money may be needed to re-stack the judiciary to ensure a reform will survive the wide-eyed fanatics on the USSC. This scenario is deeply unlikely as piles of money large enough to afford to spend a billion dollars purchasing legislation are very happy with the law as it stands.
>The latest EU publisher payout copyright 'reform' -- which, among other things, banned photography of buildings and skylines
That sounds like absolute nonsense, unless you can cite a source. First of all the EU has no power to actually pass laws, only make draft recommendations. Secondly the whole "copyrighted buildings" thing is about prohibiting commercial use of a structure's image in advertisements etc.
The point of the DMCA and US copyright is not to be reasonable, just, fair, or whatever. It exists to make large corporations money via regulatory capture.
There is no reform because reforming or fixing it is antithetical to the current intent - nigh unlimited power for a fortune 500 companies mob of lawyers (or affiliate) to take down and sue with impunity.
The moneyed interests here have a trillion dollar industry on the line. The people just have... freedom? and sanity? to gain in return. And those are nebulous, unfocused interests. If the collective citizenry cannot unanimously push for police to not crush windpipes on the street anymore its never going to voice disdain for a thousand page book of artificial made up scarcity built up over hundreds of years.
Because of how github works these moves are much more damaging than you might expect: In addition to revoking your access to the supposed "infringing" work, you also lose access to all your pull request comment traffic and issues -- which, unlike the source code, aren't continually replicated to the systems of all developers.
Those things are however exposed via their API, so anybody who’s worried about a similar situation may perhaps do well to utilize it and take regular backups.
As I understand, takedown is a 17 USC 512 (copyright infringement) safe-harbour, but not a required or indemnifying protection under 17 USC 1201, anti-circumvention:
Here's Debian's mirror btw, somewhat out of date and using the one-commit-per-upstream-release development model (in the upstream branch), so lacking a lot of history: https://salsa.debian.org/debian/youtube-dl
Youtube-dlc has merged a lot of youtube-dl's outstanding PRs, i remember -dlc being 350 commits/7 behind -dl some 2 or 3 days ago. So definitely base the fork off *-dlc
There's also that copy in the Arctic. I don't think that Github will remove that one.
Edit: On a serious note, though. I just realised that Internet Archive apparently doesn't archive most PRs? (https://web.archive.org/web/20201018122643if_/https://github...)
If so, that's a real shame, I had an open PR on youtube_dl and even though I still have the code locally, I would've liked to keep the PR conversation as it had some really helpful feedback and a bunch of people that were potentially interested in my feature.
That doesn't matter. As development stops, youtube-dl will stop being able to download videos in a matter of months (at best). This is an extremely brittle system that relies on youtube-dl being one step ahead of Youtube at all times. Without further development, the next update to Youtube's site will break the tool.
It was really a matter of time. I'm sure most of us were already amazed it lasted this long - and it did because it remained a relatively obscure tool for years.
It's also the case that the development of subversive/illegal tools requires a certain amount of subterfuge and sneakiness that the youtube-dl developers apparently weren't ready to engage in. While this is understandable, it also underscores the fact that such tools live on borrowed time (as does, I would argue, general-purpose computing itself).
While they may have made collaborative development more difficult for the moment, what hasn't changed is the strong motivation from a wide range of technical people to be able to download whatever they can watch in a browser. Something will rise from the ashes.
Here's a git mirror of the entire repo history up the the latest commit hash that I'm aware of. Compare against the commit hash on Google Webcache [1] for safety:
The copyright trolls are encircling Archive.org ever since they briefly offered the National Emergency Library. They need all the good vibes we can send them, please donate!
I give them money every month because their archives are essential to preserving our history. Not to mention, they have really saved my bacon before when I really needed to read some technical blog published a decade ago that has since been lost due to the website being reorganized or even being completely taken down.
Even though it takes a lot of bandwidth, I think preserving the source code on GitHub is an invaluable service and hope they continue to do so. I didn't know they were saving the zip file of every release, but I can understand why. It gives you point in time snapshots more easily and who knows how easy it will be to use a git repo from today 100 years from now. ZIP is a much simpler format if it needs to be reimplemented and is used all over the place.
Internet Archive seems to be heavily promoting Protocol Labs tech and File Coin specifically on their Twitter feed. I have donated small sums and ran a couple fundraisers via Facebook which benefited Internet Archive. The promo for File Coin is new. They pitch it as building a decentralized AWS, which I'm not sure if File Coin gets you 100% of the way there, but it's a start?
Assuming youtube-dl is dead and the web APIs become hopelessly obfuscated, how hard would it be to talk to youtube as if I were a samsung smart tv?
Perhaps the next iteration of this project can leverage google's own insatiable greed against them. Embedding youtube into every "smart" device on the face of the planet probably requires that google maintain a fairly consistent private API which all of these devices can communicate with. If someone were to reverse engineer one of these devices or just throw wireshark on the WLAN, it probably wouldn't take long to emulate the same approach...
What is stopping someone from using these types of internal interfaces instead of the public ones?
This should be about impossible to enforce? Every developer and everyone who has ever cloned the repo has the complete source tree with commits. I can think of a list of countries where United States laws are not a concern, I imagine that shortly this will be one of the most distributed repositories ever.
It also shows again that while free services like Github are convenient, and truthfully their interface is the one to beat, it is better to use them as a mirror of something you self host then the primary.
Some options: (I prefer gitea - easiest to install and maintain, very active development community, single binary, written in Go)
Understood, just waiting to see where the devs pop up. I imagine that someone will help them with a DMCA counterclaim also. RIAA has been beaten many times, they have a long history of creative interpretation that the courts do not always agree with, and US law is only valid in the United States and Australia (thats a joke, but do hope they get on the brick and road plan or stop acting like a US colony at some point).
That would be true IF youtube-dl was all about downloading YouTube videos only, but it's not. It's used by people to download videos from like a thousand other websites too.
I agree with your concept. The main problem though, is that each of those code hosting web app is a silo of its own. Any new contributor will have to create a new account for each of the self-hosted projects. Youtube-dl is one of those projects that can't survive in such an environment. Sourcehut is free from such requirements - but many complain about difficulty of email-based workflow. Another option is the upcoming federation protocol from gitlab.
Late reply, but replying since you mentioned gittorrent. The project's author recommended [1] the Radicle project (https://radicle.xyz) instead of gittorrent.
The more I look at the RIAA's complaint, the stranger it seems.
I'm not even sure that the RIAA has standing to sue or could demonstrate injury:
- The claimed anti-circ method is not the RIAA's, it is Google's (via YouTube).
- As a user agent, youtube-dl is simple an alternate Web access method which runs code from the YouTube website as a necessary part of the process of accessing and playing content ... meant to be accessed and downloaded.
- Youtube-dl has substantial non-infringing use. 17 USC 1201(a)(2)(B) https://www.law.cornell.edu/uscode/text/17/1201
This is the first time I've read a DMCA notice that also references EU Directives and German law too (admittedly it's a thin note saying it's materially equivalent to U.S.C.). Is that even meaningful in a DMCA takedown notice?
I believe the way you put it describes this part in the DMCA takedown notice the best way possible. Bringing up European laws on intellectual property and mixing it with US "copyright" is comical to me, especially after reading this [0] article on French law recently:
> France doesn’t have copyright. Sorry for US readers, your “copyright” is nonsense that doesn’t apply here, though the word “copyright” can be seen misused verbatim once in a while.
I believe this interpretation of "copyright" is all similar around Europe. US copyright law is all about "right to make copies", be it software or music/video and it just doesn't make any sense on the other side of the globe.
In the country where I live I can purchase a music or video file and legally make unlimited copies for my personal use. It is also legal to download it from any other source as long as I can prove that I paid for it some time ago in the past. Torrents are illegal as the protocol forces me to share the file, and sharing part is illegal. Downloading is fine xD.
There may be significant differences between US and EU copyright laws, but the anti-circumvention laws in question here are pretty consistent, as they implement the WIPO Copyright Treaty ratified by both the US and the EU: https://en.wikipedia.org/wiki/Anti-circumvention
Then I wonder if level of security a given anti-circumvention technology implements matters in the EU.
See, I strongly believe (and heard of such cases in the past) that where I live, if I "hacked" into a computer system which had administrator password set as "admin123" and the owner sued me, he would be laughed at at the court and I was let free. And I believe in the US I would be convicted for computer crime.
Isn't it the same here? If Youtube's anti-circumvention tech whatever it is that DMCA compliant refers to is so weak that source code how to circumvent it is in the wild for years and Youtube does nothing to address it, isn't it theirs fault? :shrug:
We're both IANALs, but it is interesting to put it into perspective that the same sentences that makes laws mean something totally different in practice on two sides of the globe due to cultural differences and/or origins of given laws.
Sorry for not being clear enough.
It's not that torrents as protocol are illegal. So yes, it is totally legal to distribute any content you have rights to distribute, such as Linux distros, creative commons material, you name it.
It would also be legal for you to share a music file to, for instance, your friend who lost it's original copy but already paid for the song. You simply can't redistribute the song on massive scale to people who didn't buy it, so that's torrenting weakness here. Also, the personal connections between you and the downloading party matters in determining if this was fair/"personal use".
The youtube cipher has probably not been tested in US courts as an "effective measure" so they are demonstrating that other reasonable courts, interpreting a materially equivalent statute have agreed it was an effective measure.
You see similar things with state laws. If say Wisconsin and California have a very similar statute, and Wisconsin has precedent but California does not, the Wisconsin precedent is not binding, but is persuasive for a judge in California.
YouTube-dl is a great tool that I've found use for a dozen times, and not once to download music or music videos. (Note that it works on sites beyond YouTube.) This takedown interferes with a number of legitimate uses that are completely independent of the RIAA's objectives.
Agreed. Once I discovered that "it also works outside of YouTube" when I want to archive something I'll just point it at a page and set it loose. It's also handy for archiving an entire podcast by feeding it only the RSS feed URL and turning it loose.
I think a rebrand would and a healthy amount of not-with-a-10-foot-pole-itis in their attitude towards any mention of youtube or music downloading would be helpful. Like a secret menu item at a resturaunt you could use <generic>-dl to download youtube videos, but don't specifically endorse it.
It’s also a valuable tool for making fair use of content from YouTube without further degrading quality with an additional re-encoding further ruining quality. Of course, little surprise the RIAA would ever admit these tools could be used for anything but piracy.
> The clear purpose of this source code is to (i) circumvent the technological protection measures used by authorized streaming services such as YouTube
Using this logic then OBS or any desktop recording tool is also violating the same measures because you could press record while a Youtube video is playing and wind up with your own locally recorded copy of the video.
Since we're here, let's also say any smart phone is also in violation since they could technically record a Youtube video playing on another device.
What about your brain when you remembered the copyrighted song that you listened to on YouTube and then you just listen to it in your head instead of playing a video? It's just ridiculous. These greedy organisations should be made illegal.
It makes perfect sense to the people who design these twisted legal machinations.
A tool like OBS is designed for generic desktop recordings, while youtube-dl is designed specifically to enable the copying of copyrighted works. Or at least that's what the RIAA will say, and unfortunately a judge will likely be very sympathetic to that claim.
I wonder where this will go defensively in court if it gets there.
I guess what the RIAA is really saying is that murder is legal depending on what was used to kill someone.
A hunting knife could be used to kill someone but it could also be used to slice a pizza pie. A pizza cutter was designed to slice pizza but it could also kill someone without too much effort.
If it's not ok for youtube-dl to create an mp3 of a music video but it is ok for OBS to do the same then it must also be ok to decapitate someone with a pizza cutter[0].
In that analogy, the RIAA is saying “hunting knives are illegal, because they’re primarily designed or marketed for hunting, which is illegal” and you are saying “that’s unfair because I use my hunting knife to cut pizza.” The analogy breaks down because hunting knives aren’t illegal, but copyright circumvention devices are.
The end result provided by both tools is what's illegal in both cases. Recording copyrighted material and murder.
In my analogy the RIAA is saying a specialized tool for recording copyrighted material (youtube-dl) is illegal but since they didn't file a DMCA request for non-specialized tools that record copyrighted material (OBS and the like) then they must be ok with allowing copyrighted recordings from those tools.
Thus the RIAA thinks specialized tools for murder (hunting knife) are illegal but generic tools not designed for murder (pizza cutter) are fine to kill someone.
You seem to be reading “the purpose of this source code is to circumvent technological protection measures” as though it means “this source code can be used to circumvent technological protection measures.” There is a difference.
They would have to prove that Youtube's lack of a download feature is a "technological protection measure" against copyright infringement.
A lack of a feature can be rationalized in any direction. Ultimately not enabling you to download increases youtube's revenues because of people rewatching the same videos online.
Unless Youtube states explicitly that this lack of a download feature is for the purpose of copyright infringement then they can pipe it and stop disrupting everyone outside the US.
It's not because OBS does not contain any code specific to circumventing streaming services protection measures. youtube-dl does contain code specific to such circumvention.
It is a bit of a tough question. How would I feel about someone borrowing a book from a library and then photocopying it to keep a local copy? If the intent was to re-distribute then I would not feel comfortable allowing it. However, if the proposed remedy was to ban personal ownership of photocopiers I would not even consider that a valid approach. But would I expect I could keep my own photocopied version instead of paying retail price for the book? And what if a purpose built photocopier was designed and marketed for the express purpose of photocopying books from the library?
My personal feeling, and obviously not a legal opinion or even morally infallible in any sense, is that storing a local copy of digital content that has been consumed should be allowed. Where it becomes grey (or my feeling tends towards disallowing) is if I share or re-broadcast that content in any form.
That is, I feel the DMCA is in the wrong here. Unless they can prove intent to re-distribute it feels wrong that they can ban my ability to maintain a copy for myself. I believe it ought to be a right to store such content locally.
While photocopying books for distribution is against the law, I disagree that it should be against the law.
If 3 people all borrow the same book sequentially then it's fine. If one person borrow it, photocopies it twice to share with two others, then they've broken the law. And yet nobody in either case has made more or less money.
I am in favor of copyright law that prevents profiting from another person's work, but not against copying. Once your idea is public knowledge, there is no reason for it not to spread freely given how easy it is to transmit information now.
> Once your idea is public knowledge, there is no reason for it not to spread freely given how easy it is to transmit information now.
This treads into territory I feel is grey. I imagine the complex case where I sell some creative content (e.g. a pdf, audio file or video). You pay me for access to this content and download it. I grant that you ought to be able to retain a local copy of that content for so long as you wish.
Then you create freecontent.com and publish it. You don't put ads on it, you don't sell it - you simply make it available for free at some URL without my express permission. In a world where that is legal, I feel it would materially harm my ability to earn from content I create. I have a hard time supporting that even though I am sympathetic to the idea that information ought to spread freely.
> I feel it would materially harm my ability to earn from content I create
Got any data to back up this feeling? I've seen plenty of cases when content creators have had big breaks due to their content being made freely available. If people love the work, they'll support the creator. This modern trend of needing to pay before you even know if you love the work is an inversion of what has happened in history, to our detriment.
> This modern trend of needing to pay before you even know if you love the work
How modern do you mean? It seems to me that I pay for a movie ticket before I sit down in the theatre and watch it (trailer not withstanding). Same is true for plays and operas which preceded that. I would pay for a book before reading it (cover excerpt not withstanding). In fact, I'm trying to think of any media that I would consume before I paid.
> Got any data to back up this feeling?
Meh, we're only going to throw anecdotes back and forth. I recall bands like Radiohead and comedians like Luis C.K. experimenting with "pay what you want" ideas. I would suppose the fact that didn't catch on (outside of humble bundle charity type things) would be evidence that it didn't work for a large enough segment of creators.
Also, it isn't like RIAA members are allergic to money. I mean, if there was any reasonable evidence that free sharing of content resulted in profits that are equal or greater (or even viable) rationality suggests that they would embrace it.
I have no issue paying for movie tickets or concert tickets, and believe that is the primary way movie and music creators should be supported. A theatre ticket covers the costs of running a theatre, a concert ticket covers the cost of running the concert. And the artists/creators receive a cut of that.
But if I copy a film, what's actually happening? The distributor has already spent the money on making blurays and distributing to streaming platforms. If I photocopy a book, the publisher has already spent the time and material to produce the physical copy. The only argument here is that the author deserves a cut of revenue, because another copy of their (already publicly available idea) is in existence. I find this notion absurd. Why is an author entitled to money when an idea they have already disseminated is put onto a new piece of paper? I own the paper and the photocopier. The materials are mine. The author should not have a monopoly on how ideas are spread. Nobody can compel them to share their ideas, but once they are shared, they are out there. I could read a book to somebody and a partial copy exists in their mind. Should authors receive royalties for mental copies too? Why not? They lost nothing physical when I made a paper copy either.
Our copyright system is broken, and is based on completely flawed premises.
It's a difficult problem to solve, but it's worth pointing out that our copyright system was originally meant to protect initial works, then when they expire, create a rich public domain for citizens.
> Meh, we're only going to throw anecdotes back and forth.
That’s a big problem with this whole debate. I think we’d be better off without copyright and that creators would find new, better ways to make a living. But it’s pretty difficult to see how this could be convincingly proved or disproved, so I guess we’re stuck with the status quo forever.
A law which can't be proven to be effective is a bad law. If it's difficult to prove whether or not copyright is effective then the laws which restrict freedom need to be removed.
Your example is a case where piracy had no profit impact, but it's not the general case.
The books are priced in part based on assumptions about how many people can read them over time. A book at a library can probably only be read by ~20 people a year. If 200 people a year want to read it, the library needs ten books. But, if we were free to post the scans online, the price per book would need to be astronomically higher.
While the usual naive extrapolations of MSRP-times-pirated-copies is also wrong, allowing people to freely and at-will render others' work unprofitable is a subversion of the purpose of copyright: To ensure that the creation of works is be profitable enough to pursue.
If someone wanted their work to be in the public domain, they could so choose.
Can you support the claim that creative work becomes unprofitable when copies are made freely available, but the option to support the creator still exists?
I mean it's not the best setup, but what else do you suggest? This was meant for protecting income of authors while not being too inconvenient for most users. Netflix primary model is this and it is working great for them and users. Many people do share the account but it does add some inconvenience that only some maximum number of people can watch at the same time, making people get subscription.
> It is a bit of a tough question. How would I feel about someone borrowing a book from a library and then photocopying it to keep a local copy?
If you're photocopying a library book in order to avoid buying your own copy, I don't feel great about that—we need to support authors. Yes, everyone's financial situation is different, and not every under-the-table photocopy is a lost sale, but there has to be some incentive to actually go to the bookstore.
But here’s the thing—for 99% of Youtube videos, there is no bookstore. There is no other way for me to acquire an unencumbered video file, regardless of how much I'm willing to pay.
And to stretch the photocopy analogy a bit, there are a lot of other reasons someone may want to photocopy a book:
• If the book has small print, you may want to enlarge the text.
• If you prefer listening over reading, you may want to OCR the pages and use text-to-speech.
• If you're doing research, you may want to OCR the pages so the text can be digitally indexed and searched.
• If you have an eReader, you may want to digitize the book so you don't have to carry around a paper copy.
And, sure, in some cases it may be possible to buy an official audiobook, or an eBook, or a large print edition. But in other cases, that might not be an option.
Downloading a Youtube video affords similar freedoms, allowing you to experience the content in the way that makes sense for you.
I don't think anybody really disagrees that redistribution is a copyright violation and the youtube-dl software doesn't provide any facilities for uploading or re-broadcasting content. This takedown is completely frivilous.
I agree with your moral analysis here, and that the prohibited thing should be the distribution of protected IP, not simply retaining a copy of something you already had rights to view (which I think there is substantial precedent for).
This is the big problem with the DMCA. It shortcuts the messy dirty work of dealing with IP violations, to the benefit of large corporations and the detriment of individuals. The former engage in rampant abuse of their powers under the DMCA, apparently without any fear of significant consequences. It's just another example of the degree to which large corporations own America.
Aren't books kinda a special case ? Given all the past (and even current!) cases of censorship and book burning, shouldn't we strive to never allow that ever again and to protects books for future generations ?
Finally we have a way to preserve books in perfect form forever digitally yet people somehow try to shackle this new technology with paper book technology limitations. The same limitations that coat us so much ideas, knowledge and stories as books would burn, rot or turn to dust.
Frankly any form of technology trying to prevent digital book distribution and archiving really is a digital equivalent of the inquisition book burning (or helping make that happen again).
What is the fundamental difference between a book and a video that would make books a special case? Yes, they were around earlier, and yes, that history has shown what can happen if we start censoring expression. But that's not unique to books, and the exact same reasoning applies to video in the current world.
Then maybe we should strive to protect all of our culture for future generations ? Instead of trying to artificially limit it's spread for a quick buck and risking loosing it all in the process.
How many old movies have been lost, old TV shows that were live only, old software with source code lost for ever and even many games that no one can play anymore due to game servers and DRM servoces shut down.
Instead of breaking out of this vicious cycle when we finally have the technology to do that, there are people actively working against that, including sabotage of those who want to do the right thing...
Am I the only one who uses youtube-dl for downloading silly mp4s from Twitter and Reddit, and all the other aggregators? I mean, sure: some Youtube videos are copyrighted, and youtube-dl was originally made to download Youtube videos. But despite the project name, it's evolved beyond just that. Don't kill the whole damn project when the legal issues are limited only to certain backends to begin with.
How can a program be in violation of DMCA? Is a knife in violation of the criminal justice system because some people use it to kill and therefore no one can use it anywhere, ever? How ridiculous.
> Is a knife in violation of the criminal justice system because some people use it to kill and therefore no one can use it anywhere, ever?
I mean, guns are banned in many countries using precisely the same reasoning. And I might totally be wrong about this but I heard that in the UK you need to be over 18 to buy even just kitchen knives.
> in the UK you need to be over 18 to buy even just kitchen knives
There's a "Challenge 25" (formerly "Think 21!" IIRC) policy which covers these kinds of situations - although it is just a voluntary agreement from the major retailers.
> It’s illegal to [...] carry a knife in public without good reason, unless it has a folding blade with a cutting edge 3 inches long or less
> The maximum penalty for an adult carrying a knife is 4 years in prison and an unlimited fine. You’ll get a prison sentence if you’re convicted of carrying a knife more than once.
This blows my mind a little bit. I have a Swiss Army knife (among a ton of other things) in a waistbag that I carry most places I go. It proved very useful a few times, but other than "in case I need it" I don't have a particular reason I carry it. It seems really dystopian to me that in the UK, I could get 4 years in prison for that.
You'd need to combine location (possession at school, or in prison, or at a place where there is serious public disorder) or effect caused (causes serious alarm or distress), and also intent (crime based on hostility to religion, race, disability, sexual orientation or transgender identity of the victim), or the blade would need to be a "highly dangerous weapon" (ie, not a swiss army knife).
Carrying a swiss army knife, and not having a good reason to do so, would be culpability D and harm 2, and so the sentence at mags would be a band C fine (about 1 week of your pay) or a medium level community order.
Does your Swiss Army Knife not fold? Is the blade on it over 3 inches long?
Unless I'm mistaken it looks to me like that law was written almost specifically so that Swiss Army knives in particular are considered an exception to the rule.
My particular knife is also longer than 3 inches, but it's a larger model and I think you would be correct to point out that most Swiss Army knives are shorter.
Guns are not banned in any country. They are restricted in almost every country, for good reasons. The level of restriction may vary based on culture, history etc.
Also people who claim the same logic applies to kitchen knife and guns are mentally still living in the wild west of the 1800s.
AFAIK guns were banned by the Tokugawa Shogunate during the Sakoku period till the Meiji revolution & gun ownership is still very limited in Japan even today.
Countries where guns are "banned" only include a handful of outliers. I think only Eritrea has a blanket ban on gun possession by civilians. "Applicants for a gun owner’s licence in Laos are required to establish a genuine reason to possess a firearm, for example hunting" (https://www.gunpolicy.org/firearms/region/laos).
Ah, sort of like how concealed carry isn't "banned" in Hawaii because a permitting process exists, but in reality <10 permits have been issued since the system's inception.
The primary intended purpose of a gun is to wound or kill humans or animals. You _can_ kill people with a kitchen knife, just like you can with a beer bottle or with your hands. Not exactly the same thing tho, is it?
This isn't a new debate; in the early days of the DMCA, it was used to go after the author of DeCSS [0], despite the fact that legitimate Fair Use cases for the tool exist (personal backups, playback on unsupported devices at the time, like Linux PCs). The case was in fact stronger there, as DeCSS explicitly circumvented encryption [1], which AFAIK youtube-dl does not.
And, of course, the infamous case of Napster [2]; while the vast majority of user behavior was obviously piracy, the tool/network itself was content-neutral, and could also be used for public domain content, or works published with the permission of the copyright holder.
From the youtube-dl source code, in a file helpfully called youtube.py:
def _decrypt_signature(self, s, video_id, player_url, age_gate=False):
"""Turn the encrypted s field into a working signature"""
if player_url is None:
raise ExtractorError('Cannot decrypt signature without player_url')
It definitely does do decryption, as stated in the DMCA claim:
> is a technology primarily designed or produced for the purpose of, and marketed for, circumventing a technological measure that effectively controls access to copyrighted sound recordings on YouTube
.. and some claims referencing a 'youtube to mp3' site ruled illegal by a German court.
Not defending this, 'effective technological measures' are a horribly broadly-scoped hole, but there is decryption at play here.
Could you make the argument that the technological measures are not effective and therefore not "effective technological measures" since youtube-dl is able to access the recordings in spite of them?
You could make the argument that the technological measures are not effective (the RIAA says this was rejected by a court in Hamburg), but not in that extreme form. If the existence of a working circumvention tool implied that the technical measures were not “effective,” then all circumvention tools would be legal and the law would have no effect. “Effective” must mean something more than “so ineffective that it can be circumvented with common sense,” and something less than “so effective that there’s no need to make its circumvention illegal.”
The DMCA contains provisions that criminalize circumvention tools. The plaintiff only has to prove that a tool is mainly designed to aid in copyright infringement and/or that's the most common use. It's a super super bad law, but has unfortunately been used quite successfully over the past 20 years by the likes of the RIAA and MPAA and others.
> Is a knife in violation of the criminal justice system because some people use it to kill and therefore no one can use it anywhere, ever?
Many jurisdictions in the US consider carrying a hidden knife beyond a certain length as illegal carry of a concealed weapon.
> Some knives (switchblades and gravity knives especially) are illegal in most places.
I think it's usually about carrying them in public outside your house. Likely not as illegal to have them at home.
Gravity knives are scary in that the police have occasionally argued that certain common pocketknives (e.g. Leatherman) can be used as a gravity knife and arrest people (usually minorities of the wrong color). I once was going on a road trip across multiple states and had to research the laws of each state because I was carrying a Leatherman.
I don't get why you where downvoted. the analogy is pretty accurate. knifes are utilities which can be used to kill. guns are made for killing only.
There are plenty of legitimate uses for youtube-dl. There is even fair use in the US. How can i make fair use, eg. remix or a commentary if i can't access the videos outside of youtube.
IANAL, but as far as I know GitHub has to comply with DMCA requests. Otherwise, they would lose their safe harbor protection and become liable for all distributions of copyrighted content through their service.
However, GitHub is also required to reinstate `youtube-dl` if the creator files a DMCA counter-notice.
This is not a valid DMCA takedown request, as the claimant has not asserted copyright ownership of anything in the repository.
This notice is a conflation of two separate aspects of the DMCA, the copyright takedown process and technological circumvention devices. If the RIAA wishes to claim that youtube-dl is a circumvention device, the proper route is to sue the authors of youtube-dl. This notice is an abuse of process, and highlights the need for a penalty for fraudulent DMCA requests.
This is a good point, but I think ultimately Github has to comply with it to maintain their legal immunity, it's not their responsibility to determine if a copyright claim is valid.
Similarly, youtube-dl can issue a counter-notice, and Github will have no responsibility to determine the validity of that either. They simply restore access unless they have been notified that a lawsuit is in progress.
That's exactly how it works. The content carrier is on the hook to be responsive to DMCA takedown requests, and they are ~allowed~ (actually, also required) to be responsive to counter-notices as you describe.
Their responsibility begins with removing the hosted data in question, where a valid DMCA notice is issued (and there is no incentive for them to make a judgement about whether the notice is valid or not.) If the authors of youtube-dl want to file a counter claim, that is their right, (which would put GitHub within their rights to restore the content too.)
All of these declarations are made under penalty of perjury, both claims and counter-claims:
> The DMCA requires that you swear to the facts in your copyright complaint under penalty of perjury. It is a federal crime to intentionally lie in a sworn declaration. (See U.S. Code, Title 18, Section 1621.) Submitting false information could also result in civil liability—meaning you could incur a financial penalty.
The civil liability here is a liability to the party who was damaged, (the author or copyright holder), so even if GitHub wanted to assert by themselves that the DMCA takedown claim was invalid, they would not have standing to sue anyone about it. So pretending even if you did believe youtube-dl authors are in the right and that the courts would be inclined to rule in their favor, and you're Microsoft, you have to honor the DMCA request and take down the content in order for there to be justice, since there can be no party with standing unless there are actual damages. (IANAL, you probably already figured that out by now, and I have no idea what the legal definition of "actual damages" is, but I do know what standing is.)
Personally I agree that this does not represent a valid DMCA claim, but for GitHub to assert that and ignore the claim based on the way these laws are written, and those safe-harbor laws as well, I think any lawyer would say this is not possible.
> DMCA takedown claim was invalid, they would not have standing to sue anyone about
If this exact same logic were extended to YouTube: an invalid DMCA claim will absolutely reduce YouTube ad revenue causing measurable financial damage.
Besides arguing: "they should have known it was invalid and refused to comply," how exactly would this not grant standing?
That may be true, but this is not a claim on YouTube, (or the case of many frivolous claims made by these same RIAA folks on YouTube, that I know we're both thinking about.) There is no advertising sold on GitHub that I am aware of, and unless the youtube-dl authors are paying subscribers, I'm not sure how there could be any monetary damages to GitHub or Microsoft.
YouTube was just an example as it's easier to show damage and remedy.
GitHub?
- How does this third-party unlawful request not constitute tortious interference between GitHub and all users (or just the paying member who owns this repo)?
- If not directly tortious interference, this action could absolutely result in the loss of paying members and reputation damage.
- The very fact we're discussing this means GitHub has suffered damage to their brand.
- How does this resulting loss of source code not diminish the value of GitHub as a company?
As I said, I am not a lawyer and you may have out-lawyered me here already, but I'll do my best to respond. The law prescribes this path for youtube-dl authors to respond to the claim, if youtube-dl authors want to put their names behind the project and make a legal case out of it. That severely limits the calculable damage that is possible, (especially if youtube-dl won't pursue the matter further.)
The claim in the takedown notice that is required to be submitted under penalty of perjury is simply that the party submitting the claim actually represents [copyright holder] and that notice which RIAA submitted also does not make any demonstrably false claims. It does not entirely fit the format of a regular DMCA copyright takedown request for copyright enforcement, it has two sections (one is called "Anticircumvention Violation"). It goes into detail about how the rights holders which RIAA lawyer represents are aggrieved, with language like:
> we have a good faith belief that most of the youtube-dl forks are infringing to the same extent as the parent repository.
# (This is probably the most dubious claim, and since the channel for takedown notices is for copyright enforcement, if your argument had a leg to stand on, I think it's this one. But is it calculable damage? And is the mention of Taylor Swift and other RIAA member artists in the README not plenty of evidence that there is actual infringement that is happening, or at least that it could have been asserted in good faith as it were that those rights holders believed there is a valid claim, as this infringement was happening?)
and
> the youtube-dl source code available on Github (which is the subject of this notice) circumvents YouTube’s rolling cipher to gain unauthorized access to copyrighted audio files, in violation of YouTube’s express terms of service
I think for this to be tortious interference, you would have to demonstrate that there was any intentionally false information in these claims, and that's going to be tough. There is part of a DMCA takedown claim that must be asserted under penalty of perjury, and after re-reading the law and jogging my memory I understand again that for the party sending the takedown notice, that is very limited. (Unlike the counter-claim, which has to assert ownership under penalty of perjury, the claim must only assert that claimant represents an owner as identified in the claim and that the factual claims made in the notice are true, in good faith.) Otherwise it's hard to argue that this notice is anything but an effort to enforce multiple sections of the law as it is written, by asking nicely for a hand through the channels that GitHub has made available for enforcement.
Whether or not it meets the definition of a valid DMCA takedown notice, it is a letter with many demonstrably true factual points, which GitHub has accepted through their channel for enforcement of claims. GitHub has "voluntarily" complied with their interpretation of the law here, in response, and there is an avenue for redress for the authors, if youtube-dl authors feel this is worth pursuing.
The DMCA takedown request process is exclusively for content owners and their representatives to gain remedy for their own works. Youtube-DL is not their own work.
The takedown request process is improper: they should have filed in an appropriate United States jurisdiction.
As you've noticed: the format is strange because this is an illegal attempt that GitHub really should not have complied with.
It makes both a copyright claim and a claim about circumvention devices. I don't agree, as you don't, that the copyright claim is valid, youtube-dl git repo clearly isn't hosting any copyrighted materials owned by the RIAA members represented in the letter. But the letter also never claims that it does.
The law does not demand automated enforcement of claims or the establishment of a channel for automated enforcement. That is a compliance device invented by GitHub/YouTube/etc. for managing the substantial volume of requests they must receive with as much transparency as their customers demand and its operational characteristics are not covered by the law, it's simply a tool that GitHub uses to make themselves responsive and in compliance with as little overhead and manual intervention required as possible.
The law does prescribe the "claim, counter-claim" process, which GitHub must respect if they are to maintain their compliance and safe harbor. If they were in the habit of reviewing every claim for validity (strictly not required by the law that insulates them), then I might agree with you, but I think that singling out this one claim and handling it specially would in fact open them up to a great big world of even criminal liability, that their straightforward compliance with the law insulates them from.
The law prescribes almost exactly how GitHub should respond to claims and counter-claims, down to how many days the content may be removed for if a counter-claim is laid.
> If you send a counter-notice, your online service provider is required to replace the disputed content unless the complaining party sues you within fourteen business days of your sending the counter-notice. (Your service provider may replace the disputed material after ten business days if the complaining party has not filed a lawsuit, but it is required to replace it within fourteen business days.)
What must happen now, is youtube-dl either responds with a counter-claim or they don't. Then either a lawsuit is filed by RIAA within 10-14 days, or it isn't. Possibly one is filed later. (They don't waive any rights by not filing the lawsuit right away.) By managing the claim this way, GitHub has ensured at least that they need not be party to the lawsuit. (They will not be on the receiving side of a lawsuit. This does not preclude them from going on the offensive and claiming tortuous interference, but it does protect them from imminent danger.)
So, whether this was a valid claim by RIAA or an illegal attempt at tortious interference is surely a matter for the courts to decide, but suffice it to say I am far less confident than you are that GitHub would be safe from any kind of legal reprisal if they stood fast here, and tried to hold the position that you are arguing without letting the compliance channel play out however that goes.
It is a chilling law and we've known this since it was penned. I don't agree with the law and I am interested to see this play out, I hope this takedown is not the end of the story.
GitHub has voluntarily complied with this (bad IMHO) law. If that were true, and frivolous requests were being made and dismissed routinely, then GitHub might curb their voluntary "compliance" machine. Is that actually happening, or are you trying to argue that it's a slippery slope?
If bad complaints are not dismissed by the courts, then it's a really bad law, or a bad court. That is a problem for GitHub, granted. If you are shopping for a source code hosting service that will insulate you from such DMCA claims, then sure, GitHub has just shown they won't do that. I guess!
I'm not sure that will have any measurable impact on their business model. They were never to my knowledge in the business of providing that kind of protection, before or after Microsoft.
That logic is all fine and well, but that requires GitHub to determine if a takedown is valid or not. And if they determine incorrectly in a case, they’re open to damages in that case.
So, is it worth it? Or is it worth just letting the parties figure it out?
If the DMCA is truly invalid, a counter-claim can be filed. If the other party doesn’t want to file one, I guess GitHub wonders why it should keep the content up when the creator doesn’t have faith in it.
Obviously I note the possible flaw in the above logic, in that there’s a difference between an individual developer deciding it’s worth starting a legal faff with a big company by filing a counter-claim, verses GitHub doing it, but their service would go broke dealing with legal requests otherwise.
Correct way to deal with this is through your lawmakers, not saying Microsoft should foot the bill for a broken law.
If the notice had claimed copyright ownership of youtube-dl, then Github would have to act on it even though it was incorrect. But since it's not an actual well formed takedown notice, legally Github does not have to do anything with it - just as if it were missing contact information or were not signed. Unfortunately there is little downside for Github to act on it regardless.
It seems like the right process is to mosey on over to gitlab. If gitlab properly defends the developer, that will continue the gradual github exodus to more open platforms.
“For all distributions of copyrighted content through their service”
I don’t think that’s true? I think that only extends to this particular DMCA. Obviously it wouldn’t extend to eg me claiming Ruby on Rails is copyright infringement.
Not really. They're legally required to do so. The DMCA notice (despite what someone suggests downthread) is unfortunately quite properly served. Even if it is flat-out wrong, GH/MS has no reason (and likely no resources) to investigate whether or not that's the case. And if they did, and got it wrong, they'd lose their safe harbor status and be liable for damages.
If the youtube-dl author believes it to be bullshit, they can send a counter-notice, and GH/MS will then put it back up. If the RIAA still has a bone to pick, they can file a lawsuit. Unfortunately, they very well may.
> It's not that far from targeting wget or curl, were it not for the widespread use of them in industry.
I get really confused when I hear things like this, because this makes no sense. Targeting a program called "YouTube Download", which has the main purpose of downloading clean copies of YT videos, against the wishes of the content creators is absolutely not the same thing as targeting a generic HTTP/FTP download tool.
I think the DMCA is garbage, but it feels like willful ignorance to be at all surprised about things like this, and to compare this to something obviously non-infringing.
Because there's no upside and only downside. If they refuse to comply and it turns out that youtube-dl did infringe, then they won't have DMCA safe harbor status and could be liable for damages.
While the takedown request is outrageous, I'd probably respond the same in MS's shoes. Frankly defending it is not worth the corporate lawyering required from MS's perspective.
That said, I think if Youtube-dl self-hosted on Gitlab or something and received a similar takedown, they could probably mount a successful defense.
Made a torrent of the latest version from pypi. Hope it works.
magnet:?xt=urn:btih:da76788b4d05583f8a3a7ed60f136c5647daa113&dn=youtube%5Fdl-2020.9.20.tar.gz&tr=http%3A%2F%2Ftracker.bittorrent.am%2Fannounce&tr=http%3A%2F%2Fopen.acgtracker.com%3A1096%2Fannounce&tr=http%3A%2F%2Fretracker.krs-ix.ru%2Fannounce&tr=udp%3A%2F%2F9.rarbg.com%3A2710%2Fannounce
Is there anything stopping someone from creating a new youtube-dl repo on GitHub with the README examples in question removed?
On that note... how do you actually remove copyrighted content from a git repo? Even if you fixed the problem on the HEAD of the master branch, it would still exist in the version history.
Git history, just like human history, can be rewritten, if you only know how.
(It gets a bit harder of it's cryptographically signed)
EDIT: To whomever is downvoting, I'm not making a remark about some specific event, is a tongue in cheek poke at "history is written by the Victor". Chill.
But it can also be sued for downloading uncopyrighted material. It's like submitting DCMA for Office Word because people can use it for creating pirate copies of Harry Potter.
"For example, as shown on Exhibit A, the source code expressly suggests its use to copy and/or distribute the following copyrighted works owned by our member companies"
That's quite unwise to be honest. But these examples should be removed, not the code itself.
To be fair, more like Microsoft® Office® OneNote™; it has a camera feature and an automatic OCR feature and a “copy text from image” convenience feature.
So why does the Recording Industry Association of America get to decide whether a tool for downloading content on a service that is produced by people around the world and released under many different licenses exists or not?
The RIAA and America in general has no right to police the rest of the world.
What is the percentage of content hosted on youtube actually under control of the RIAA vs other content? If less than the majority of content on youtube is theirs, what gives them the right to have a tool removed for downloading content from a service that's not theirs and which they don't own the majority of the hosted content?
Why does the tool being hosted on an American website make any difference?
YouTube's content doesn't all belong to them, they don't even own the majority of the content on there and a huge number of users and creators on youtube do not live in or fall under American jurisdiction which means neither does the content they create, so again, why should the RIAA have the ability to do this?
I am guessing they'll find a country with more respect for freedom than the USA and host it there. All the devs will obviously have the full repo and history to put it elsewhere.
Stuff like this is why I consider it unethical to pay for recorded music, unless distributed directly by the artist. Haven't bought music from a major distributor since I was a teenager.
I don't want my money funding this sort of overreaching censorship.
Most of the comments so far are ignoring the bigger picture: this isnt something new, its just the RIAA playing whack-a-mole with the DMCA hammer. Theyve been doing it for 20 years, and in those 20 years the most they have managed to accomplish is building a better, more resilient mole.
Napster was followed by bittorrent, bittorrent by popcorntime, and youtube-dl. in the past 20 years the industry has quietly capitulated and delivered some content users really want like streaming audio services, but in the grande cosmos of the DMCA-related war on piracy the industry itself continues to do more to smite its own face than it does to offer a more reasonable and accessible product to their audience.
There is nothing to keep me from writing something now that scrapes puseaudio for content triggered by mpv. the only real factor thats of concern is that this new backflip would be even harder for the RIAA to prosecute.
Also, a recommendation for the youtube_dl crew is to use a self-hosted solution (if GitHub/GitLab/SourceForge wont do). Find a cheap Linux hosting provider and run Gitea on it: https://github.com/go-gitea/gitea
As others have mentioned, I believe that the main problem here is that youtube_dl is "showing intent" to violate DMCA. If they modify the readme, they might be able to prove that the intention of the software is not necessarily to violate DMCA, but maybe just being a general purpose code or one for educational purposes.
Regardless, it's possible to host PyPi wheels yourself if necessary. The installation process wont be as straight-forward as "pip install youtube_dl", but it's still doable with one command.
I was also able to apt install it on my distro, but the version I got was too old to actually work. So I cloned one of the git repos mentioned in this thread (Chinese copy) and ran it from there.
Many (thousands, if not tens of thousands) YouTube videos are being deleted right now, crazy censorship taking place. If tools like those get banned then it gets harder to keep copies of videos before they will be banned from YouTube.
That’s what we get for unrestricted proliferation of a platform offered by a big company. Is it even surprising anymore? Just saddens me but we can’t do anything.
I find this amazing, essentially Google has been scraping every piece of content they can get their hands on, when a few individuals decide to get data, that wasn’t even created by YouTube, they get take down notices. The more I think about it hypocrisy should be a defence against these things.
Perhaps it's time to take a closer look at projects like Fossil that combine distributed version control with wiki and issues tracker built in. If the devs behind youtube-dl were using Fossil then picking up right where the DMCA leaves them is no sweat.
Pagure is a git forge you can self host, where every repo contains not just project source code but also all related metadata (wiki, issues, etc.): https://pagure.io/pagure
This makes it very easy to backup and move all project data as needed. In comparison most other forges hold project metadata in an instance wide database, making it much harder to extract & import when needed.
Keybase, outside of the distributed bit along with the question of their future, provides zero-knowledge git repositories (they’ve literally got no idea what is in your repositories, including metadata).
https://github.com/forgefed/forgefed is a github alike that is federated via ActivityPub. this distributes content to a bunch of servers, but it is not cryptographic, not meant to be censorship-resistant. i think this could be layered in to ActivityPub, particularly by making use of Signed HTTP Exchanges to verify content origin, & then you'd still need a way to find alive hosts.
This should serve as an example to people who want (for example) the GNU project to relax their contributor copyright assignment practices. It only takes a single moment of complacency and the vultures will swoop in. In this case it was because of sloppiness around which urls were used in a demo. Yeah, all urls are the same to the guy who is building a url slurping service (which is why the take down will likely be defeated), but there is an entire profession dedicated to nothing but nit picking, loophole hunting, and general levels of pedantry that we have just come to call it lawyering. Layers are like cliffs or handguns. Stay as far away from them as possible, they are facts of life, but you really don't want to have anything to do with them unless you have no other option.
The whole copyright industry is based on toxic premises that do not hold true anymore in the internet age.
By now, different models have been proven to work. Make them the norm. Abolish copyright. Or turn them back into what they were supposed to be: a TEMPORARY protection of a work since first publication (originally 21 years IIRC).
Old Disney characters, superheroes invented in the 40s and 50s, even the "more recent" Starwars are part of culture now just like Othello or Moby Dick are. Allow to use them as such.
If they did, it'd be still complicated. A real example, a modder makes some content for an old abandoned game. He needs some voice over, so he contacts the original voice actors, but they deny to do that job on the grounds of being a member of org like this[1] which strictly prohibits to take side jobs.
And to make it even more complicated, consider tools like for making deep fakes; if somebody makes a neural network that emulates the original voice, should it be sub-licensed or copyrighted? Can a voice be copyrighted?
Youtube-dl (2020) would be an easier case to present to the public than DeCSS (2000).
Everyone knows what Youtube is. It's easy to understand the utility of being able to download a video from Youtube to save it on your computer. If they didn't already know this was possible to do, they'd immediately want to start using it as soon as you explained it was possible.
DeCSS was exploiting a weak encryption scheme's weak key distribution scheme. Where the only final explanation for why this matters is that it can be used to rip off DVDs.
So the RIAA has tech folks just like any other organization. Some of those tech folks likely read HN. Question for you folks (use throwaways if you feel it could jeopardize your job): how do you ethically justify working for such an organization?
Time to upload youtube-dl-legal a computer program created for the express purpose of downloading only videos with permissible licenses. The readme shall note that any use of youtube-dl-legal to download illegal videos is expressly forbidden and even thinking about using it in this way is thoughtcrime of the most serious degree.
I'm going with that this whole thread is extremely astroturfed and that the shills are out in full force. For the sake of my own sanity. FUCK the RIAA.
It's the same for me. Computers, networks, and mice are all used by "criminals" to download copyrighted material without permission, I'm not sure how youtube-dl is any different. I think github simply doesn't want to fight this because basically they weren't making any money off youtube-dl, so they took it down. They'll pry my trackball mouse from my cold-dead hand though. F the RIAA and MPAA.
This is lousy! I depend on youtube-dl to archive videos for later use. Nothing MAFIAA would be interested in; just stuff from topical channels that I want to have around for personal use in case they get deleted.
I really hope this doesn't stand, because what it's basically saying is that you can't even tell someone how to download something that might be copyrighted. Not only that, but this was brought forth by a murky technicality.
I would like to add to the discussion that there are many perfectly legal uses of YoutubeDL:
* Downloading a video you uploaded and no longer have stored locally.
* Downloading a video to create a fair-use response video.
* Downloading video/music that is free commons (or some other non-restrictive license).
* (Gray) Downloading content to archive it.
* Downloading content you have already purchased and have in your possession.
* (Dark gray) Downloading content you have a paid subscription to view, but don't have reliable internet.
All of these anti-piracy measures need to answer one simple question - what stops somebody from just screen recording your material? At the point in which somebody can view your material on another device, you've lost a lot of control.
> If anyone has an up to date repo of the github pages repo
> that'd be great too.
The webpage seems to be still up [1], it should be possible to grab those resources.
The releases can be rebuilt from the tags - the only other thing is the issue tracking. It would be a super pain to lose 3.3k issues (and the discussions they contain) [2].
what stops somebody from just screen recording your material?
The end game is every device having a watermark detector. The PS3 wouldn't play BDs with pirated in-theater movies for example, due to audio watermarking.
> The end game is every device having a watermark detector.
That would be a concerning future, but thankfully one that would very hard to realize. You would need to control all hardware & software players, as well as all watermark removal techniques.
I guess the end-game is really just cloud-computing. If every device is just a dumb terminal, you don't really have the power to bypass any such measures.
So... what is going to happen to youtube-dl? Will it get renamed considering it supports ~1155 websites (based on docs/supportedsites.md)? If it does get renamed, how are we going to know its name? Where do the developers going to push their changes, where is the development being continued?! Fuck everyone who complies with such retarded laws. Corruption is sometimes good, in cases such as these. :)
They'll still take down a repo and block the user if it is hosted. And self hosting something isn't free, plus quite possibly puts more legal exposure on the team.
This isn't a problem with technologies or the platform. There fundamentally needs to be a narrowing of DMCA, a presumption of innocence rather than guilt, and penalties for issuing unjustified takedowns.
Re: your edits, yes, DMCA reform is also important, and quite arguably more so. But decentralizing from GitHub would still slow takedowns down, and have other benefits.
It was clear that youtube-dl has always been used for its utility. And the deeper problem here is why aren’t we allowed to do whatever want to whatever is streamed onto our screens? TV shows could be vhs taped without issue as long as not redistributed. For sure we cannot take this fight against google with the American laws, but I think the software was morally correct and should be legally permitted.
I'm surprised they haven't gone after browsers. They would surely have asked Google to display certain messages when a user visits known piracy sites
This website is currently disabled due to a DMCA takedown notice. The website you are trying to access hosts copyrighted content. Please contact support, or seek the copyright holder's permission to access the content.
Don't they ? It might not be really obvious, but take a Walled garden platform like iOS for example. Already third party developers can't build their own browsers and all are efectively a skin over the Safari web engine.
What this means is that iOS is effectively one lawsuit (ore even major bribe) away from RIAA or other similar unscrupulous group dictating what sites you can access and what you do with the browser. And you can't just sideload another browser due to the walled garden!
And it's not just iOS as there are unfortunately many Walled garden platforms these days - smart TVs, game consoles, browser extensions for some browsers, etc.
Even Android limits what you can do with a ROM that is not rooted - and some high profile apps will refuse to run on a rooted one!
You can use Chrome to download from Youtube - you just need to know the temporary URL. One way to get this is to play the Youtube video in VLC - the media information window will tell you the temporary URL, and then you can use Chrome to download the content. So maybe the RIAA should issue a takedown request against the company that makes Chrome?
Some time in the last few hours the devs have updated their site (https://youtube-dl.org/) with a notice about the takedown and removed the broken github links. You can now download the latest executables again. I'm looking forward to seeing their new home.
I'd think the RIAA and Google are well acquainted with the Streisand effect by now... I'm just hoping the takedown will prompt a whole bunch of people to contribute to youtube-dl out of spite, as I know it had been lagging behind due to simply not having enough contributors. I'd even go ahead and throw down the glove.
Is there an alternative to github that is resistant to denial of service attacks^1 like this?
1: At this time this is just a baseless accusation and there are no repercussions to the RIAA for blatant abuse. Why wouldn't they simply send a takedown for anything they don't like no matter whether it is legal or not?
IANAL, but DMCA takedowns do not have "no repercussions" for false claims. If the DMCA takedown was actually baseless, they would be opening themselves up to damage liabilities, as specified under 17 U.S. Code § 512 under section f[1]. This is different than YouTube copyright claims, which as far as I'm aware don't actually have any repercussions for false claims unless YouTube decides to take action[2], since copyright claims on YouTube are not DMCA takedown requests.
> DMCA takedowns do not have "no repercussions" for false claims.
They mostly do.
> If the DMCA takedown was actually baseless, they would be opening themselves up to damage liabilities, as specified under 17 U.S. Code § 512 under section f[1].
The basis for liability there is knowing misrepresentation of infringement. So as long as RIAA believed (and that belief need not be reasonable) the legal theory of infringement that they advanced, there's not a liability problem.
SUre, if they misrepresented their right to act on behalf of the legal owners of the works they claimed were infringed by it, or that would be an issue, but no one even suspects that they are doing that.
While this is true, I was responding to a post about abusing DMCA takedowns, which have the assumption that they're using it to knowingly misrepresent infringement. And even though most abusive DMCA takedowns end up without any counter action, the law does provide a way to fight them, which is the disincentive from "simply send a takedown for anything they don't like no matter whether it is legal or not"
Courts calculate damages for fucking with an open source software project as basically zilch. For all intents and purposes, that is "no repercussions" for a pile of lawyers like the RIAA.
Who is the defendant here? Do they have resources to take this to court? If not, is there any movement on raising a legal defense fund and finding competent counsel? Anyone from the ACLU team here, and interested in weighing in or at least bringing this to your leadership for consideration?
1. Clone the repository. Make an insignificant change to the initial commit in order to change all commit hashes. Push to github as a new repository.
2. Create a password "protected" zip file (or smaller volumes) containing the repository. Use a password that's easily found in common wordlists. Commit it to another project and push to github.
Microsoft GitHub may be centralized, but it's not omniscient. RIAA may be a control freak, but it's not omnipotent. Let information be free for all.
This isn't really much of a help. There is no danger of losing access to the archive; it's popular enough that's it's essentially impossible to wipe from the internet. The issue is that now there is no central place where developers can pool their efforts to keep the code working. And it does need constant updates to address changes in the websites it downloads from.
The extractors directory had 765 extractors in it, only one of which is YouTube. The facts seem cherry-picked to support their case (well duh). Hopefully that will matter. Given that youtube is a tenth of a percent of the extractors maybe there's hope.
FWIW, it's easy to find the code on Google. The release tarballs have the format youtube-dl-YYYY.MM.DD.tar.gz and one can look in the Homebrew Cellar, for example and see there was a release on 2020.09.20. ;)
Even if YouTube was the only extractor, it shouldn't make a lick of difference - not everything on YouTube is owned by the RIAA as they'd like to believe!
When you clone a repo from Github, you now have locally an equally as valid and complete repository as Github. If you expose access to it over the Internet, I could clone that repo from you, work on it, and send patches to you. Etc.
Git was designed to facilitate a network of repos. For better or worse, most use cases naturally gravitate towards a single clone as the "canonical version", and unfortunately we've all got too comfortable in having that version be owned by a third party service provider.
Legitimate question, as most people see this as hosted on a server somewhere and your client doesn't sync with other clients... usually!
You do, in fact, have a client capable of working without a central server. It's tedious but sending patches over email is definitely one way to make it work without relying on a single system. You can also have and push to or fetch from multiple servers with your client, which can be other developer's own servers, or a server reachable over Tor as a hidden service, etc. It's very flexible if you want to go that path.
git was designed to be used decentrally. Every clone of a git repo is technically an equally valid source of truth for the repository. In practice though, pretty much every project has a single git repo that is used to synchronize all the other copies of the repo, because it's much easier to coordinate.
When people say decentralized they mean something like bittorrent or ipfs, often as opposed to http. Saying http is decentralized is... stretching the definition. With this logic a USB cable is decentralized because "you can use it against any target you like". USB mass storage dead drop devices can be connected to by anyone. And USB "is a protocol", just like the examples you mentioned. But I doubt anyone would claim USB is decentralized.
Though git is also not really what people would usually mean by decentralized (as it doesn't, by itself, try to connect to a pool of servers, DHT network, or something like that), it's definitely closer to it than http.
I'm also not sure "for real?" helps the conversation.
> having at least some of the processing done by the individual workstations and having information shared by and often stored at the workstations
Decentralized:
> the dispersion or distribution of functions and powers
(Both from Merriam Webster)
BitTorrent definitely fits the distributed definition (as you said), but whether HTTP is decentralized depends on how you view it. Yes, there can be more than one HTTP server, but again, there is more than one USB cable and I wouldn't call that decentralized. HTTP doesn't distribute the functions and powers between the client and the server (the two parties in any HTTP request): the client can hardly serve the response and the server can hardly issue a request. But it does distribute functions and powers between multiple servers because there isn't one global HTTP server or party that serves the Internet (now that would be a scary thought--looking at you, CloudFlare).
So it depends a bit on the explanation of that definition.
I think what I said before might be right: it's "stretching" the definition (interpreting it in a way that includes this). I can certainly see where you're coming from (anyone can host their own HTTP server just like anyone can host their own email or git server or bittorrent node) but it's not really how the word is usually used. But perhaps we use it wrong, because it does seem like a useful distinction to make (a centralized (proprietary) game server vs. a decentralized protocol like HTTP vs. a distributed protocol like BitTorrent).
It would be terrible if youtube-dl.com would digitally sign and release youtube-dl source as zips on thepiratebay and other torrenting sites instead of github.com.
If you still have youtube-dl on your system (at least the version distributed on homebrew) your youtube-dl file is compressed. You can get the full source code by chopping the shebang line off the top and unzipping the file.
This is a really sad moment for open source, especially for content creators and devs in media/content spaces. I've shipped youtube-dl for a user-facing (production) experience before. This sucks.
The "under penalty of perjury" part of DMCA has always been fascinating to me. Has there ever been a single case of this being enforced against inappropriate DMCA takedowns? What's next? DMCA against Intel for making a chip that can facilitate copyright infringement? Maybe a power company for providing power to the machine that could do it?
(i) is strange claim as youtube-dl simply implements various streaming protocols public to anyone, most commonly used protocol is HLS which is just a simple list of URIs of small portion of video files in text file over HTTP/HTTPS. No technological protection whatsoever.
(ii) can be easily avoided by simply removing or changing the example usage.
Welcome to the USA where the court system isn't about the law or justice. It's about who has the most money and resources to win a war of attrition in court.
"Download Web Videos"
"Keep your favorite web videos safe on your PC by downloading them.
You can save videos from popular sites in one click – including YouTube."
This will do nothing. The tool will instantly be hosted outside the US. Even if the developer is American it's just going to get instantly scooped by someone else.
Saw this coming. We are working on https://dgit.sh for the last couple of months. Dgit is a decentralized code collaboration platform where we harness the power of git for versioning and arweave blockchain for permanent data storage. We also have a Dgit community on https://community.xyz where the stakeholders take all decisions transparently via a vote.
Dgit will be available for use after its launch on 2nd November. If you are interested in what we are doing feel free to join our discord and chat with us https://bit.ly/dgitchat
If the video is viewed directly on youtube, the majority of viewers will also be served ads which generate revenue that is shared with the copyright holder (note how youtube identifies the music in the video and who the copyright holder is below the description of the video). So it's not about not wanting it downloaded, it's about not wanting the ads circumvented.
Very true, but it was inevitable. The tool worked way too well to remain under the radar for too long. What will be interesting to watch will be where the forked versions of Youtube-dl will end up.
Considering YouTube allows Creative-Commons licensed videos[0], how exactly do they suggest we "reuse and edit" videos, as per their own documentation? I'm not seeing any "Download video" button on a CC-licensed video's page, so... am I missing something here, or is one not forced to use a 3rd-party video download utility like youtube-dl to actually "reuse and edit" a CC-licensed video?
Strategically / tactically, the most interesting aspect of the RIAA attack on youtube-dl to me is that it puts Microsoft on the spot to show its true colours. Is it Friend of Free Software, or Copyright Maximalist?
Yes. And since Microsoft and the RIAA are both in the contrived/artificial scarcity business, it’s pretty obvious to me what it’s going to be.
The propertied classes won’t let this crisis pass without using it as an opportunity to further enclose and plunder the commons even more for the working classes.
What does it matter if I watch a song on YouTube or just dl the video. Mp4 and watch it,
The riaa might say the reasons the videos are on YouTube is
they promote the artist like old videos on MTV
and someone gets paid ad revenue ,
In theory someone could just
use a pc dl 1000s of videos put em on a pc and avoid watching ads
Also video streams count to get a song in the charts
and the riaa employs lawyers
so they have to do something
to justify their wages
even if it will have no effect on the music marketplace or the behavior of the average music fan
So it looks like the takedown notice has nothing to do with the actual developer of youtube-dl. I.e., the developer could distribute their code somewhere else and the RIAA would be left playing whack-a-mole.
Anyone working on ytdl will have a full copy of the history at home, undisturbed, so distribution is working as it should. There is no single point of failure.
I sometimes imagine how wonderful it'd be if there were a viable alternative to the Web that is decentralized and infeasible to censor, only to realize that how great it is for the freedom, is the exact reason why it doesn't exist. It's just too inconvenient for those in power. That might be why Tor was funded by the government. Its primary functionality is to strengthen the existing Web, rather than to be some competing force to the Web.
There are multiple extensions in Google's own Android Chrome stores for downloading videos from YouTube and everyone else. I just used a few to download and HLS stream that was having severe buffering issues.
It would seem hard to argue that Google is completely against it when they could be considered a contributor to the "problem". Providing apps that violate their own TOS. Not just source code, but actual apps/extensions.
Not a lawyer, software guy working in licensing & copyright for 20+ years. Was paid for a few years to talk about this stuff with tech and publishing people.
They're requesting the takedown under 17 U.S. Code § 1201 - Circumvention of copyright protection systems. [https://www.law.cornell.edu/uscode/text/17/1201]
It's a few paragraphs of the actual law at stake here. There's no much to it.
Essentially, they're arguing that Youtube's normal stream distribution technology is "effectively control[ling] access to a work." Given 3A & B from the link above, that will take a fair amount of arguing - there's no encryption, there's nothing that requires information under the authority of the copyright holder (like a key) to descramble the information.
Unless the repo has code that's breaking browser-based DRM, in which all bets are off - breaking DRM is by definition circumventing a technical protection. Doesn't matter if it was easy to break-- you break encryption, there's no more argument over whether you're circumventing. Decryption is right there in the text of the law.
Github agreed to the takedown because they don't want to be distributing a circumvention tool, and they don't feel like going to court over whether this is a circumvention tool or not. There are a lot of repos out there, you can't go to court over every single one. I'd be surprised if it stayed up on GitLab for much more than a New York minute, either.
The EFF might fight this, because there's a pretty good argument around the noninfringing uses; however, they also might not, because there's not much of an argument around whether it violates the Google Terms.
Some us are mentioning that there are use cases for this software that don't infringe copyright. That goes back to Sony v Universal, the VCR/Betamax case, which permitted the production and sale of technologies with "substantial noninfringing uses." In the case of the VCR, the particular noninfringing use was time-shifting of broadcast television, taping shows to watch later. The noninfringing uses here are around downloading works that are in the public domain or Creative Commons, and definitely around offline use. Easily a colorable argument.
The file sharing cases of the early 2000's have drawn some lines around the noninfringing use defense, though. Napster and Grokster both claimed, in court, to support noninfringing uses. However, both products promoted their products as offering free access to copyright-protected works, and the courts took notice of that in both cases-- I believe that the Grokster opinion may have noted that Grokster had never mentioned a noninfringing use outside the trial.
IOW, if you're providing a dual-use technology for noninfringing use that is also capable of infringing use, you absolutely cannot promote the infringing uses to the exclusion of others. Not only do you draw unwanted attention to yourself, you may actually (as in Napster and Grokster) invalidate the most important defense that you have for your activities.
> The file sharing cases of the early 2000's have drawn some lines around the noninfringing use defense, though. Napster and Grokster both claimed, in court, to support noninfringing uses. However, both products promoted their products as offering free access to copyright-protected works, and the courts took notice of that in both cases-- I believe that the Grokster opinion may have noted that Grokster had never mentioned a noninfringing use outside the trial.
That's an excellent point. It seems like youtube-dl may have started as a tool primarily used for ripping music off YouTube, but it has grown into a tool that is used for so much more than that today (offline viewing of content, backups of freely licensed material, fair use such as extracting clips from videos, etc).
Given that no one is getting sued over this, at least not yet, perhaps it makes sense to not fight this and simply allow youtube-dl as it stands to be pulled and re-imagined as a new piece of software that is explicitly focused on the positive and legal use cases. If RIAA still wants to go after that software, the case against it would be far weaker than the current product that has "YouTube" in the name and explicitly references ripping copyrighted music in its source code.
Correct. Distributing and developing illegal software (as RIAA has declared youtube-dl to be) is a solved problem technically.
I'd like to see a case surrounding software like this actually defended in a court, though. It would be helpful to clarify what is legal and what is not on the modern Internet in terms of fair use and time shifting.
I am confused. The complaint seems to be that copyright infringement is happening with the downloading from YouTube, but I thought it happened with the uploading to YouTube. Could you clear that up?
Courts have ruled betamax Vcrs were legal, its legal to record tv shows and movies to watch them at a later date.
Even though in theory Vcrs could be used for the purposes of piracy.
Just because a device might be used to pirate content does not mean its can be banned.
Like bittorrent is used by many non profits to distribute
Open source software like
Linux distro iso, s
> It only means that we received the notice on the indicated date. It does not mean that the content was unlawful or wrong. It does not mean that the user identified in the notice has done anything wrong. We don't make or imply any judgment about the merit of the claims they make. We post these notices and requests only for informational purposes.
(IANAL) Github follows US copyright law (and probably other countries' copyright laws too), so they're required to take it down upon receiving a DMCA takedown request. If it's not a proper request, the repository owner can file a counterclaim, but that would open the repository owner to lawsuits.
I remember books (with the code inside) being used as a workaround for cryptography export controls.
I wonder if the same could apply here (if this notice holds up to begin with), either as a book with code, or as a book with instructions in English language that are equivalent to what the code does.
A book. Or any other medium of expression protected by 1st amendment, such as t-shirt [1], poetry [2], music [3]. And more broadly, any way of encoding a number in an artform via steganography [4].
This is just the next terrifying development on Planet China. YouTube-dl went unmolested for years. About week ago, I was party to an online conversation a week ago about how youtube-dl is an important tool for archiving videos of public officials before they can be disappeared.
Coincidence?
After the RIAA won a case against Limewire in 2010, the next significant legal action I can find in a bit of looking is that the US Supreme Court ruled against the RIAA in Allen v. Cooper (March 23, 2020).
I think that they should update the readme and rebase the history and eliminate any references to the original copyrighted material of the readme file. possibly even making a request of GitHub to help them clean the repo or evidence of any logging information with regard to the copyrighted content. I think it would be relatively easy to argue that a web browser would be guilty of every single little thing that can be done through YouTube DL binary in the right hands. The only copyrightable information that YouTube - DL offers is an instruction set or a direct correlation to the fact that they can use this tool to do some things that are implicitly prohibited.
Radicle[1] can't come soon enough. Git already works over I2P[2] (TOR alternative) btw ;)
The more often this happens, the more we'll learn about reproducible builds, decentralized (and/or anonymous) code hosting, and setup tools and software that uses this more. I'm sure the distributed tar.gz is next on the list for this DMCA and we can't rely on things hosted on the clear web anymore.
This was bound to happen with proprietary services like GitHub. It's better to use self-hostable services like GitLab & Gitea, where we can have regular backups of everything - code, issues and any other metadata. So, the service can be up shortly.
Sure, GitHub like features offer more than just a space to host our code. It has become a goto site for example, finding new and interesting repos to contribute to.
It's important that the devs or community that develop a software think about the potential censorship it might have to encounter from thugs like DMCA, based on what is it that they develop and evaluate the choice of hosting.
BTW, I just installed it using `choco install youtube-downloader`. Nice to have while they don't find a new location.
It also showcases a marvelous advantage of using git as a VCS, they automatically have multiple backups and can easily transport the project. And it showcases that all the other project info, like issues and comments should also be under version control and downloaded in developers machines. You can't depend on an external service for your project.
BTW, is it possible to use GitHub features in a distribute way? E.g.: create issues in my machine and pushing it to the server?
I have created the youtube-dl repo at Darktea, feel free to create your anonymous accounts and join the project, until we find a better/decentralized place.
I will give the main contributors the neccessary access for reviewing/merging/etc.. or will entirely hand over the project if you can prove you are the maintainer.
I just installed it from archive.org using the url homebrew uses. It's a simple matter to run brew install -d youtube-dl plug the url that into archive.org, download the archive, cp it to the dl location (minus the .incomplete) that brew expects, and then run it again without the -d so it thinks it is already downloaded.
I wouldn't have installed if they hadn't done this, and I'll probably never use it, but this rubbed me the wrong way.
Can't I just FORK it and change the Readme and/or tests to not include references to what could be constituted as infringing acts, and purposely state that the purpose of MY FORK is to download YouTube videos that are in the public domain?
If it's been taken down I am sure it will pop up on some torrent. The authors and all those who have contributed to it have copies.
How can a court tell me not to publish generally useful software with a legitimate intent?
Have we heard anything from the youtube-dl developers yet?
Have they made some sort of statement?
Are they really going to get sued?
Is it possible to support them (other than through the EFF: https://eff.org/donate/)?
Has github made a statement yet?
(Oh and don't think for one moment that the RIAA's actions have anything to do with supporting the struggling artist.)
So, are they going to also issue a takedown for YouTube Premium next? Premium allows you to watch/listen without ads and also allows you to download videos for offline use. If I pay for YouTube Premium, there should be no problem with me using youtube-dl to timeshift the content I've already paid for. It's no different than using a DVR to record a show off a cable channel I pay to subscribe to.
Really, the RIAA should be going after YouTube for better remuneration, rather than going after youtube-dl. Unless I'm missing something, they get paid no matter whether the view comes from a browser user-agent or youtube-dl user-agent. How is this any different than recording a song off the radio, which is, AFAIK, legal under fair use?
It would be interesting to see who added the testcase that has the copyrighted video. Maybe honest mistake, maybe it was intentional to kill the project.
YouTube-dl is actually in pypi and other places, GitHub is not the sole distributor. However, it is their sole development hub, as far as I can see, and that should change. After all, Git is distributed by nature. I suspect they’ll have to investigate a bunch of those new tools that try to do issue-tracking on top of pure git, and the main developers will have to go underground. It’s DeCSS all over again.
I've been hoarding significant YouTube channels for years, at a cost of many terabytes of HDD space. Even though they were always available for free, I was always betting on the fact that YouTube's status as being incredibly easy to archive would not last forever.
I feel vindicated, but also sad that the end of this particular era has finally arrived :(
Even if the examples in the source code point to the code as deliberately enabling copyright infringement, I thought the DMCA takedown process was for actual copywritten content. Even if they are found, in a napster-like way, to be "illegal", it doesn't seem like a DMCA takedown notice is a valid mechanism to enforce the law here.
This fight against software is growing into bizarre forms. What's next? cURL?
I really wish there was some kind of retribution in the typical OSS licenses. You censor free software, free software censors you. I think these organization would think twice to take down a project if they would immediately lose access to Linux, Apache, Python, et. al.
I’ll admit that I’m ignorant of US law specifics here, and I’m not sure about YouTube’s DRM and/or policy regarding downloading videos is.
So I’ll ask: is this DMCA request justified? Why would the RIAA be going after YouTube-dl, rather than Google? Wouldn’t it make more sense for the RIAA to go after YouTube instead?
The RIAA's logic is that a youtube-dl user is equivalent to someone in a movie theater with a video camera. The situation they're concerned about is somebody downloading a music video that they've authorized to be on Youtube. They make money on Youtube views, but they're losing precious fractions of a cent when you download it and watch it offline.
This is obviously not ethically justified, but I have no idea if it's legally justified.
The problem with their argument is that youtube-dl is a video camera. The US has already rules that video cameras, VCRs, DVD recorders, etc are all devices with legitimate uses, and you can't stop them from being made or sold. A movie theater is within its rights to ask patrons using video cameras to leave, and Google would be within its rights to lock down Youtube.
The RIAA is fishing, and all the precedents are against them pulling up even a minnow.
Even further, they are saying that the primary use of youtube-dl is reproduction and distribution. Distribution is the actual illegal act.
I can't speak to the average youtube-dl user's experience, but I've used it a lot and have never distributed a video. I've saved videos to watch later on my own, that's it.
I guess it was only a matter of time, the more popular it became. I have Youtube Premium and still use this utility every day for legitimate reasons (converting talk videos to audio file that I can listen to offline). Sad day for youtube-dl but I expect there will be many contenders to fill the void.
Unless the RIAA is actually going to take the owner of youtube-dl's domain to court, there's nothing (for now) stopping yt-dl from setting up another development platform of some sort. DMCA takedowns are cause for concern but they're not quite the be all and end all of a dispute.
Youtube-dl is not a Microsoft's project. If they send a counter-notice to GitHub (they should), per DMCA Youtube-dl is exposed for liability when GitHub restores the repository (but GitHub is shielded from liability after they restore)
"We have a good faith belief that this activity is not authorized by the copyright owner, its agent, or the law. We assert that the information in this notification is accurate, based upon the data available to us." Quick call Pop, Timberlake, and Swift to end this!
The actual content of the legal argument being made by the RIAA in this and
associated documents is lying by omission at best, and arguably is straight up
perjury.
The only _concrete_ circumvention they level at youtube-dl is that it
"circumvents YouTube’s rolling cipher". I looked into this more, and before I
go into how totally bulshit it is that they've apparently conned judges into
believing this, you should read their full accusation (or just read the full
DMCA letter from the RIAA):
For further context, please see the attached court decision from the Hamburg
Regional Court that describes the technological measure at issue (known as
YouTube’s “rolling cipher”), and the court’s determination that the technology
employed by YouTube is an effective technical measure within the meaning of EU
1 See https://github.com/ytdl-org/youtube-dl/blob/master/README.md#readme.
and German law, which is materially identical to Title 17 U.S.C. §1201 of the
United States Code. The court further determined that the service at issue in
that case unlawfully circumvented YouTube’s rolling cipher technical
protection measure.2 The youtube-dl source code functions in a manner
essentially identical to the service at issue in the Hamburg Regional Court
decision. As there, the youtube-dl source code available on Github (which is
the subject of this notice) circumvents YouTube’s rolling cipher to gain
unauthorized access to copyrighted audio files, in violation of YouTube’s
express terms of service,3 and in plain violation of Section 1201 of the
Digital Millennium Copyright Act, 17 U.S.C. §1201.
So that's what the RIAA is saying that youtube-dl is doing. However, they're
referencing a document that I _presume_ was attached to their original email,
the document from the Hamburg Regional Court, but we don't have that email, as
Github didn't publish that document for us to see.
So I went looking, and it turns out that the RIAA has used this exact same
excuse to go after some other people, their documents are available, and we can
see more of what they wrote. I'm referencing this[1] document which I found
through this[0] blog post about a 2016 case where the RIAA went after an online
service called TYMP3. Here are the links, and here's what the RIAA said:
< The following is found on page 8 of the PDF linked above >
39. Plaintiffs are informed and believe, and on that basis allege as follows:
YouTube has adopted and implemented technological measures to control access to
content maintained on its site and to prevent or inhibit downloading, copying,
or illicit distribution of that content. YouTube maintains two separate URLs
for any given video file: one URL, which is visible to the user, is for the
webpage where the video playback occurs, and one URL, which is not visible to
the user, is for the video file itself. The second URL is generated using a
complex (and periodically changing) algorithm - known as a “rolling cipher” -
that is intended to inhibit direct access to the underlying YouTube video
files, thereby preventing or inhibiting the downloading, copying, or
distribution of the video files.
< further down, on page 12, they lay out their accusation >
Among other things, Plaintiffs are informed and believe, and on that basis
allege, that YTMP3 employs a means to circumvent the YouTube rolling cipher
technology described above, and other technological means that YouTube employs
to protect content on its site.
So, let's go see what the Youtube-dl source code actually is doing. The tl;dr
version is that youtube does some slight rearranging of the characters in the
URL of the remote resource, but they also supply you with the JS code to
un-arrange that code into the actual working "signature" which you can use to
request the video from youtube. So youtube-dl downloads the rearranged URL, and
the JS that youtube provides, and uses a Python implementation of the JS
interpreter to run YOUTUBE'S OWN JS THAT YOUTUBE SENT US IN CLEARTEXT TO FIGURE
OUT HOW TO DOWNLOAD THE VIDEO. See the source code (hosted on gitlab for now,
hopefully that stays up):
So to summarize, youtube creates two URLs: one that's a public video URL, and
one that's the URL to the actual video content. The URL to the video content
changes on a rolling basis, and is slightly rearranged. All that's true.
However, what the RIAA is avoiding saying, and which completely changes the
context of this discussion is:
YOUTUBE SENDS YOU BOTH URLS IN CLEARTEXT, AND INCLUDES THE CODE FOR HOW TO
DOWNLOAD THE VIDEO, SO YOU AND YOUR WEB BROWSER CAN DOWNLOAD THE VIDEOS WITHOUT
USING ANY ENCRYPTION/DECODING.
So when a judge asks "how is it that you're getting around this 'rolling
cipher' to access the video?" all you have to say is "Youtube told me where to
download the video, so I followed Youtube's instructions and downloaded it from
the URL that Youtube gave me."
Frankly, I'm amazed that any judge, or any lawyer, would ever lay out or
believe such bare faced lies as is being spouted by the RIAA in this
document.
Let me be clear, basically the "rolling cipher" is DASH/HLS streaming for automatic quality changing. This has been an argument RIAA has been making since 2016, but outside of the judgement in Germany (which is wrong). All they have had on it are default judgements where no-one has even tried to counter it in court.
There is a lot of CC0 content on youtube that exists so you can download it, like stock video, sounds, background videos etc. How are we going to dowload those now?
Also couldn't the youtub-dl team claim that the whole "drm video download test" was a security test?
This is going to be difficult to find the authors' comments if there are any. I am still curious where will the development continue because downloading from YouTube often breaks and requires some fixing, i.e. update youtube-dl and it works! :/
Does YouTube embed any copyright metadata on the videos? An improved product could check for that first and prompt the user with a legal confirmation that they have the right to download the content if it was marked as copyrighted.
I don’t follow, the argument seems to be along the lines of:
Guns can be used to shoot people, they’re explicitly advertised as being for shooting people, shooting people is a crime. We request you stop selling guns.
Isn't DMCA working the way that if you disagree with dmca takedown and fill certain form, the side asking to take down content (RIAA) needs to get court order?
DMCA takedowns are filed under penalty of perjury:
"Under penalty of perjury, we submit that the RIAA is authorized to act on behalf of its member companies on matters involving the infringement of their sound recordings, audiovisual works and images, including enforcing their copyrights and common law rights on the Internet."
Perjury may or may not be the right term here, but it's definitely bad faith. EU and German legal definitions hold no weight on a US law. The repo contains no copyrighted material.
More importantly: they are not the copyright owners of the content being removed.
The DMCA doesn't magically give you the right to file "takedown requests" for circumvention devices: as stated elsewhere in this thread, they must sue in an appropriate United States venue.
This filing is absolutely in bad faith and the preparing attorney should actually face professional censure.
Perjury?
> Under penalty of perjury, we submit that the RIAA is authorized to act on behalf of its member companies on matters involving the infringement of their sound recordings, audiovisual works and images, including enforcing their copyrights and common law rights on the Internet.
Absolutely none of these things are applicable to this case.
Great! Then they should have sued the responsible party. Circumvention devices are not something the quintessential "DMCA takedown" process allows for or covers: these claims need to go to court where an injunction may be granted.
So if you did not fork youtube-dl but instead had cloned it, changed the repo to be the private nootube-dl and pushed it there - would github detect it was the same code and also take it down?
You could use your rifle/pistol/firearm to shoot unlawful transpasser, but since it's also able to shoot down innocent children in our neighborhood, please cease and desist.
They should take down all browsers and Internet we can use it too download stuff... this is so stupid. Don't want your stuff to be downloaded, don't put it online.
The latest version is: 2020.09.20, yes?
I already grabbed the source code days ago, but forgot the grab the Windows binary. Anyone keep the binary, or perhaps simply have to compile it?
Even if youtube-dl doesn't get re-hosted on GitHub, is it likely that it will show up again on another site such as GitLab or a self-hosted repo by the maintainer?
Damn this sucks. Luckily I just recovered a tar from the homebrew cache with the source code. Lets hope someone will create a creative-commons-dl or something soon.
This thing with YouTube-dl makes me consider that one quality that a "The Adventures of Huckleberry Finn" of computer science should possess is having been banned. Of course YouTube-dl might not be the Huckleberry Finn, but maybe it is something like The Satanic Verses (which I was never a fan of).
Sad but true! At least at the OBS level, it's an application running on an operating system instead of in a browser controlled by a corporation (ok Windows is becoming more walled too...)
can RIAA be hit back? - to me it looks like the RIAA actions to take down software intimidate the authors of the software and obstructs the authors from exercising and enjoying of the copyright of their software.
Microsoft are in a strategically very interesting position, one which could render the RIAA's actions suicidal.
Microsoft could pursue alternative copyright or music regimes which undermine the RIAA's stranglehold. Notably, the Microsoft Store online marketplace dropped books and music in 2017 (https://www.bbc.com/news/technology-47810367), meaning the RIAA has minimal leverage here. At the same time, an unencumbered alternative could provide an opening against two of Microsoft's biggest rivals, Apple (music), and Amazon (books). Possibly Google (both, plus, obv., video) and Netflix (video) as well. A large-corporate-backed Creative Commons media service would be a game-changer.
It's much dumber even than. A youtube web page contains everything necessary to view a youtube video. The concrete action the RIAA is accusing youtube-dl of is that it "circumvents YouTube’s rolling cipher". The RIAA has used this same complaint to have other sites/tools taken down. I've looked into the youtube-dl implementation, and it turns out the Youtube's "rolling cipher" is at most merely rearranging the characters of the CDN url of the video, and they send you JS code in the page to correctly arrange the characters of the URL so you can download it. Youtube-dl is using the Google-supplied JS and a JS interpreter to transform the Google supplied URL into the URL they need to download the videos. Youtube is asking Google what to do, and Google is saying "here's how you download the video".
IMHO the biggest problem here is the US government is policing the world with DMCA: you have to comply even you are not with physical US jurisdiction. Like the world's biggest cyber-troll, just dressed in business suits.
The legal reasoning here is shaky. Notice that they cite a German court and assert that the law there is materially the same as that in the US.
I did some research on this specific issue at one point, and I'm skeptical that Youtube's controls qualify under the law in question.
RIAA cites two sections of the law:
>the provision or trafficking of the source code violates 17 USC §§1201(a)(2) and 1201(b)(1).
It almost certainly doesn't violate 1201(a)(2), which is for access controls. This is intended to be used by someone who already has access to Youtube, so no access controls are bypassed.
R. CHRISTOPHER GOODWIN & ASSOCIATES, INC. v. SEARCH, INC., Dist. Court, ED Louisiana 2019:
>While the user id/password combination required for access was surely a "technological measure" that controlled access to the works at issue, Pevny did not circumvent that measure. She validly accessed the system using her id/password combination while she was still an employee with Plaintiff. Even if the use that she made of that access is not something that Plaintiff would have authorized her to do, i.e., copy the materials at issue, it remains that Pevny's alleged abuse of her logon privileges does not rise to the level of descrambling, decrypting, or otherwise to avoiding, bypassing, removing, deactivating, or impairing anything. As the district court observed in Digital Drilling Data Systems, LLC v. Petrolink Services, Inc., No. 4:15-CV-02172, 2018 WL 2267139, at *14 (S.D. Tex. May 16, 2018), many different district courts have held that using the correct username and password to access a copyrighted work, even without authorization to do so, does not constitute circumvention under § 1201(a) of the DMCA.
Youtube-dl either involves access to files that don't require a login, or it uses your password / cookies to access the file, so it doesn't bypass access controls.
The claim under 1201(b)(1), which is for copy controls, has more potential.
There are the subsections:
>(A)is primarily designed or produced for the purpose of circumventing protection afforded by a technological measure that effectively protects a right of a copyright owner under this title in a work or a portion thereof;
>(B)has only limited commercially significant purpose or use other than to circumvent protection afforded by a technological measure that effectively protects a right of a copyright owner under this title in a work or a portion thereof; or
>(C)is marketed by that person or another acting in concert with that person with that person’s knowledge for use in circumventing protection afforded by a technological measure that effectively protects a right of a copyright owner under this title in a work or a portion thereof.
A and B clearly don't apply. The primary purpose of youtube-dl isn't to download copyrighted content, but simply to download Youtube videos, whether they're copyrighted or not. There's clearly more than limited legitimate uses (such as downloaded public domain videos.) The question here is about C - there's an arguable case that the examples in the repo that this letter cites are "marketing" usage for infringing purposes. I'm somewhat skeptical that counts as "marketing", however, and it could be easily remedied by removing those examples or replacing with public domain examples.
The concrete action they're accusing youtube-dl of is that it "circumvents YouTube’s rolling cipher". The RIAA has used this same complaint to have other sites/tools taken down. I've looked into the implementation, and it turns out the Youtube is at most merely rearranging the characters of the CDN url of the video, and they send you JS code in the page to correctly arrange the characters of the URL so you can download it. Youtube-dl is using the Google-supplied JS and a JS interpreter to transform the Google supplied URL into the URL they need to download the videos. Youtube is asking Google what to do, and Google is saying "here's how you download the video".
That is in fact, exactly what youtube-dl is doing. They download the JS code provided by Google, then use regexes to figure out which function is the function that Google provides for un-arranging the characters, then they load Google's JS into an interpreter and provide it with the Google supplied URL to get the original signature. See the code here:
So yeah, Youtube/Google is doing (basically) nothing to protect the content, and for the absolutely token obfuscation they do use, they also provide you with the way to get right back to directly accessing the data without any protections.
The RIAA is lying in saying that Google is using technical protections, and they're lying in saying that youtube-dl is doing anything other than what Google tells them to do in order to access videos.
Are they lying when they say ‘YouTube’s “rolling cipher” is an effective technical measure within the meaning of EU and German law, which is materially identical to Title 17 U.S.C. §1201 of the United States Code’? That seems quite plausible to me. Executing Google’s code in a regular web browser doesn’t give you a way to save an .mp4 file on your computer.
You can use Chrome's Network Tools to download the files. Hard to argue that it's effective when Google's own software can bypass it out of the box.
Just check the network tab, copy the URL and remove the range parameter. You'll get one for video and another for audio, which you can merge to recover the original file. This is effectively what youtube-dl does.
(A) seems applicable to me. It is obvious that the primary purpose of youtube-dl is to download videos from YouTube. It is also obvious that most videos on YouTube are copyrighted, and the absence of a ‘download’ button protects the copyright holder’s right to prevent viewers from redistributing the videos. The contentious part is whether not YouTube has “effective” anti-downloading controls that youtube-dl “circumvents.” The fact that it needs to be continually updated to defeat attempts at blocking it suggests that this is a fair characterisation.
The conspicuous lack of a feature is not an active measure to be circumvented. Also, no one says you need to consume HTTP payloads with a traditional browser, no matter how much the rest of the worldwants to think that the Internet is all about the WWW.
Finally, there is most definitely gobs of YouTube public domain or CC-by-SA. Copyright owners who reserve all rights are not the center of the Universe.
Just a couple of days ago, I replied[0] to a comment about how the RIAA/MPAA won. Looks like I was right. They just made peace with youtube and now have them enforce their rights, despite the silliness of this "takedown"
Tldr all these comments - youtube dl got in trouble because they link to copyrighted material in the readme which from a legal perspective shows intent to circumvent copyright. If they had just linked to videos they had uploaded themselves as examples everything would be fine.
What if I remember the song I listened to on YouTube and I can remember any copyrighted material? Are they going to serve me with DMCA to disable part of my brain? These organisations are ridiculous.
I have kept an eye on a massive amount of content and it's truly horrifying how much content is lost each month. It's not even clear violation of copyright, it's just that nobody small has the energy to fight for fair use.
There should be no DMCA, all ligitation should cost the person suing a percent of income. The tyranny big players have is disgusting.
now i'm super glad that i ran it when i did, as it must have been before it got pulled. it updated without issue. i also followed the Micah provided to download the source. you know, just in case.
> this seems outrageous the same way DMCA'ing a Bittorrent client would be
Why stop there? I can use my browser to illegally download content, so I guess we better issue a DMCA takedown that too. But who even needs a browser? Let's issue a takedown for the GNU Project while we're at it because I could use wget to do the same thing. In fact, I could write my own program to illegally download content, so we better just get rid of computers altogether.
Stop attacking useful tools just because they can be used to do bad things! Youtube-dl should obviously change their README to get rid of the copyright-infringing example, but this DMCA takedown is otherwise rotten from the core.
It's kind of amazing that computing in general, and the internet in particular, is as open and free as it is (contrast with the closed end-to-end "appliance" model of gaming consoles, or to some extent iOS). Cory Doctorow has been ringing alarm bells for over a decade about both technical and legal efforts to end general purpose computation itself, or at least to make it more the exception than the norm:
> end general purpose computation itself, or at least to make it more the exception than the norm
I'd argue, cautiously, that general computation is already an exception. That's why I prefer Linux to Windows. On Linux I can issue a command from a general command interface (the CLI) to just play a video. If I only want audio, it's an option away. I can script things together. Most of my tools are interoperable. That's because I use FOSS, free protocols, free formats, free tech in general. Everything works together and everything augments each other. Windows, the popular workstation, is no that. It's a system of systems, where everything is a monolithic closed box that you can't get inside. It's inside your computer, you use it, but it's not yours. It's on loan from someone else. Interoperability is virtually non-existent, and there isn't such a thing as a usable CLI (an environment that would connect everything together). That's not general computing, I argue. General computing involves ther power to generalize, use the computing technology in arbitrary ways. Closed software, customer lock-in and all that other corporate bs is the anti-thesis of that.
Longer rant than expected. I find it a frustrating issue. Mostly because I intimately feel like we're paying a very high price for the greed of the few.
> On Linux I can issue a command from a general command interface (the CLI) to just play a video. If I only want audio, it's an option away. I can script things together...Windows, the popular workstation, is not that.
I use the same video player on Windows that you use on Linux, mpv. And I have a ton of scripts I use to navigate my video library. Windows doesn't put any burden on apps to not be interoperable. Plenty of apps interoperate just fine.
That's great, I wasn't aware that mpv was portable to Windows. Writting the above I vaguely realised that the video player example didn't have many legs to stand on. I used it because, for me, the interoperability of mpv and ytdl is a poster child for taking content that's on a closed platform (Youtube) and lifting it out for high interoperability with the rest of the system.
It's a fair point that Windows doesn't put burden on applications to be less interoperable, but it doesn't facilitate it either. The UNIX philosophy has completely bypassed Windows. You can do things on its command-line, especially if you augment it in various ways, but do you ever feel like it's a first-class citizen on Windows, or its ecosystem? I'd argue there's reasons for why, as a rule of thumb, only the biggest FOSS projects are compatible with Windows.
One thing that might be coming up is CPUs reducing the user capability to fully control the system (regardless of whether you run Linux or Windows).
One such example is Intel ME.
In the future, if the compute paradigm shifts towards something cloud-like, we might all be "stuck" inside an isolated Intel SGX container (or vice versa).
(2)No person shall manufacture, import, offer to the public, provide, or otherwise traffic in any technology, product, service, device, component, or part thereof, that—
(A)is primarily designed or produced for the purpose of circumventing a technological measure that effectively controls access to a work protected under this title;
(B)has only limited commercially significant purpose or use other than to circumvent a technological measure that effectively controls access to a work protected under this title; or
(C)is marketed by that person or another acting in concert with that person with that person’s knowledge for use in circumventing a technological measure that effectively controls access to a work protected under this title.
Can you argue that youtube-dl meets any of those conditions?
You can argue that youtube-dl facilitates making copies of copyrighted works; that's easy. But the items A, B, and C that you quote all require circumventing a technological measure that controls access to a protected work. And youtube videos, in the general case, have completely uncontrolled access. You can't circumvent measures that don't exist.
YouTube videos don't have a right click option to download the video (a browser builtin) therefore there's a technical measure that controls the downloading of the video
You don't have to be technically correct, you have to be legally correct. It's like technically correct only it's way more pedantic
Legally correct isn't a more (or less) pedantic version of technically correct. Legally correct means primarily correct with respect to the colour[0] of a thing. Technical correctness disregards colour entirely.
Absence of "Download" button on a site, or in a context menu, is not technically a technical measure, particularly when you can press F12 and poke around the Network tab to get to the same resource, all entirely a browser built-in process. But it legally is a technical measure, because the little obstacle carries a colour of "intended to prevent downloads". That's usually enough.
--
[0] - See https://ansuz.sooke.bc.ca/entry/23 for detailed explanation of what "colour" is. In a rough tl;dr, colour as a concept is a blend of provenance and intent. Bits don't really have colour, but the chain of events that made particular bits be what they are does have it. Law is in a large part an exercise of dealing with colour, but the concept lies entirely outside of computer science, so it fundamentally can't enter it, and is thus usually ignored by the tech crowd. Colour is not data, and not metadata: it's the causal context.
Agreed and here the law actually defines this term:
> a technological measure “effectively controls access to a work” if the measure, in the ordinary course of its operation, requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work.
In the ordinary course of using YouTube you cannot save copyrighted videos. This isn't so much the RIAA overreaching as it is them taking full advantage of a bad law.
(Also, Google actually did go out of their way to make it hard to save the files. Go hit F12 yourself and try. There's a reason a whole project exists to make it easier.)
> In the ordinary course of using YouTube you cannot save copyrighted videos.
On the contrary. Any ordinary use of YouTube (that is, using it to watch videos) necessarily involves making a local copy of the video. That's what you watch.
It doesn't matter. The bits arrive anyway. You don't get to run roughshod over what other people do with the bits you send them. End of story. If you didn't want me to have it, you probably shouldn't have pointed me at it, told me where to find it, and said go right on ahead. Don't mind if I do.
It's like someone getting angry at a kid or a tinker taking apart a gift. You gave it. It's mine. Thanks much, why are you so bent out of shape?
Except IP laws don't go this way. I feel like shouting into the wind in these threads.
The bits don't matter. How you got them does. If you'd pull the exact same sequence of bits from /dev/urandom on your first try, you'd be fine. But you didn't, you used a program to download the video from YouTube. You didn't download it through publisher-blessed means. In fact, the publisher and their proxies expended effort in shutting down the expected, "normie" ways of downloading it. In this way, you circumvented the technical copy protection mechanism (no matter how ridiculously trivial it was).
If you write an extension that automatically saves the streams your browser renders for you, that'd be "circumventing technical means" too, at least in case of YouTube.
That's the thing with intellectual property: it tags bits with colour, out of band, and you can't get rid of it without engaging with IP laws.
(Note that I do use your argumentation to defend ad blocking. But that's a different situation. IP laws don't recognize "free to view if and only if you view attached ads" as a colour, but it does recognize the "copyright" colour.)
> you circumvented the technical copy protection mechanism (no matter how ridiculously trivial it was)
They can't do ridiculously trivial copy protection legally, depending on the country they might be required to do at least authentication and authorization with disabled access to the sources and maybe even hardware DRM garbage, which neither Google nor publishers want to do because it will significantly reduce ad views. Basically there is no copy protection mechanism at all in this case.
>You didn't download it through publisher-blessed means. In fact, the publisher and their proxies expended effort in shutting down the expected, "normie" ways of downloading it.
Except that doesn't fly. Get back to me when they stop curl or wget with "Access by this User-Agent not supported", and I'll buy it. You are explicitly, not implicitly telling the user I don't support access via that mechanism. Then if they tamper with the User-Agent string anyway, you've got solid mens rea. Then have fun with your IP case. How this stands, is "oh, we want you to walk our little maze and view our adds as a prerequisite to viewing this particular content", but we'll tell you where to go afterwards (I.e. pay the toll, get the secret location to view your prize.) The toll for access is the add to a very large proportion of the world, that's you buying it. You have the right to back up what you buy.
It is a special defect of American jurisprudence that corporate entities reserve the right to shape the behaviors of everyone around them through something as flimsy as "well, we intended, your Honor." Guess what? You can intend in one hand, and poorly implement in the other and guess which one is real at the end of the day? The legal system is not an excuse for poor communication with large numbers of people. It simply does not pass my bar for actually implementing a technical safeguard. As it stands, YouTube was an unexpectedly successful platform for growth hacking, and the RIAA is attempting to roll up the ladder behind them.
My major contention, all else being equal is if you're doing the decoding step in the clear in JavaScript on the client you aren't enacting any control.
If the industry would like to produce a hardware platform where they can guarantee perfect IP law conformance, they are welcome to do so, but they haven't, or their attempts to do so have produced far less adoptance because gasp people aren't so gung to about spending money on things they can't own or functionally make their lives more difficult in order to make someone else's life easier.
They bought into the YouTube environment because they wanted their artists to reach the widest audience possible. They got that. And way more. It's a bit underhanded to come back and say "Hey, you people using that thing we deliberately switched to to make fat stacks of cash knowing it'd be leaky, and knowing we could have developed something better fit to the job, but not wanting to because there was business to be done now, stop using your machine in ways we don't like!"
They made their bed, let them sleep in it! Stop letting the tail wag the dog! This is also why IP is largely self defeating. IP doesn't incentivized actual furthering of the Arts and Sciences half as much as it does incentivizing litigation on whether a long enough period has gone by where a work or discovery can finally be considered endemic enough to build off of without being sued. By putting in place these established lines of legalized cartelry, the question of innovating becomes one of "how long do I have to wait to get this knucklehead out of the picture so I can build on common sense without inviting a bunch of lawyers into my life."
I can assure you. Legal issues for the everyday person is more than a generous reason not to try to push forward the state of the art, because for every guy that gets it right, there's someone who gets stomped on too.
Though, thank you, Temporal, and know you are not just shouting into the wind. I do hear and understand what you mean on the color as applied through the lenses of legalistic reasoning. I just object that the direction the legal profession is starting from were sound in the first place, and while I know that answer yields "Go talk to Congress", it's nice to occasionally have someone throw things at to see how they hold up when exposed to ration scrutiny.
So thank you.even if this seems like an inconsequential Internet argument, I appreciate it.
What about the words "with the authority of the copyright owner"? Nothing about doing it manually via Chrome's Network Tools or the Firefox or MS equivalent involves the authority of the video copyrightholder. So to me it doesn't seem within the legal definition.
Thanks for the response and interesting site to have a browse of rather than just dropping a "That's not how law works."! Pedantic was the wrong word to hinge my comment on.
That article the most enlightening things about law in general, and IP laws in particular, that I've ever read, so I'm always eager to remind HN about it :).
I've seen lots of words being wasted here and elsewhere in debates around piracy, copyright and patents, that essentially boil down to not understanding that, from the point of view of the law, bits have colour, and that colour is of paramount importance.
Absence of button not a "technological measure". Otherwise any browser having "view source" is a copyright violation tool - no site has "view source" button, and site code is certainly copyrightable material, so any browser - and in fact any text-mode HTTP client - that allows to view source is a "circumvention" tool.
No, but the various technological measures that Google uses to make it difficult to download a user copy of the video file, to the point where the compilation and use of an external tool is the easiest option, definitely are.
Seriously, youtube makes it more of a pain in the ass to download a plain video file than basically any other site on the web. You can't just view-source and get it, and you can't even nab the file from the event timeline like you can most sites that obfuscate that.
Like it or not, youtube-dl is popular in part because it does circumvent a lot of measures that youtube intentionally puts in place.
> but the various technological measures that Google uses to make it difficult to download a user copy
Which measures are those?
> to the point where the compilation and use of an external tool is the easiest option
Browser is the easiest way to do HTTP too, but one probably shouldn't claim HTTP is a technical measure to prevent using the Web (though some may be tempted to say so after a long day of debugging... ;)
> Like it or not, youtube-dl is popular in part because it does circumvent a lot of measures that youtube intentionally puts in place.
The only times I've used it was to download some lectures which were freely available to watch them over a long flight and a trip in places where network sucks. Surely, there are a lot of people who probably use it to download some RIAA-tainted crap, but it's not the only use, and the tool still would be useful if all RIAA stuff vanished from existence.
This is correct; the most common commit to the youtube-dl repo is fixing the js decoding that YT changes regularly to prevent eaxctly this type of access.
Obfuscation is clearly an accepted technological approach to security and control, if not always a good or effective one.
> You don't have to be technically correct, you have to be legally correct. It's like technically correct only it's way more pedantic
That's not how the law works. Legally correct is much less pedantic than technically correct. The difference is that legally correct often takes millions of dollars to ascertain.
I use youtube-dl all the time, and never illegally. Most of the content is CC-licensed educational content, and the major use is working in contexts without guaranteed bandwidth.
Browsers are not the only user agent out there, and that's not an active measure to prevent downloading, that's a decision not to implement a particular functionality.
There are also reasons that aren't infringing to grab your own uploaded YouTube content. Maybe you switched to another computer and left your portable drive at home. You have the right to access copies for personal use.
That they had the nerve to go for the tool is yet another extension of the war on first sale, and buyer freedom. Also, the people who made youtube-dl are not committing copyright infringement.
There are a lot of arguments against this counter example, including the fact that the browser does not facilitate you getting access in any other way than originally intended (legal) and it honors the caching policy defined for the resource (technical)
I would counter argue that if you are able to use youtube-dl you can explore the cache
The opposite cannot be taken for granted
But usually someone with very little technical knowledge can find files on their hard disks
It requires more than that to be able to run youtube-dl from the shell
The technical argument is even weaker, there are dozens of browser extensions that inject a "download video" button in video on demand websites
Video downloader professional has over 230k users, it can't download YouTube videos anymore because Chrome blocked it, because Chrome and YouTube are Google's and they don't care if you download videos, they only care about their videos, that show their ads, that make their money
youtube-dl serves a niche, a tiny one
What RIAA is doing is scaring people off from even trying, because the truth is that the real money is on mobile where youtube-dl doesn't exists...
BTW youtube-dl is a f*ng good piece of software, it should be praised not blocked
The referenced german court ruling, which is probably "Schutzgesetzverletzung: Umgehung von wirksamen technischen Maßnahmen auf Streaming-Portalen zum Schutz urheberrechtlich geschützter Musikwerke durch Konvertierungssoftware" found that the signature cipher used by YouTube counts an effective TPM. The code in youtube-dl that bypasses this is `YoutubeIE._decrypt_signature` in youtube.py
Unfortunately the law defines access control VERY broadly. If they take any steps at all to make it difficult to download the source video then that is a technological measure to control access. There is no requirement that it be effective.
Ah, sorry, that was a confusing choice of words. In the law they are using "effective" to mean "has the effect of" not "works well."
In any event the entire phrase "effectively controls access to a work" is defined in the law so what the words mean in english is irrelevant.
Here it means anything that "requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work." Which I think we can all agree is very broad.
Ah, but it isn't the copyright owner putting it in place. YouTube is. Therefore, it's just a protocol quirk of speaking YouTube.
You can say it's a selling point meant to entice ordered an the pot for rightsholders, but frankly, there is nothing but bandwidth consumption, storage, and processing limits that keeps anyone from just fuzzing the CDN namespace.
Stop thinking keys to locks. YouTube isn't there for that. I can pull off the equivalent of driving a fleet of minivans up and walking out with copies of the drives if no one else is eating up the bandwidth for long enough.
If there weren't any technological measures preventing you from downloading and saving YouTube videos, then youtube-dl wouldn't exist. You would just download the video from YouTube yourself.
"Preventing" is not the same as failing to enable. As far as I know, there's nothing that youtube has implemented that prevents downloading. It is simply inconvenient as a result of not being the primary goal.
Unfortunately it's well established that accessing resources that, even if not protected what so ever, without permission is illegal. YT's policy T&S on how and when you can consume it satisfies this.
I believe in the youtube-dl case allowing you to consume videos outside of the T&S is the crime and the automated scale is the punative factor.
IANAL and I don't agree with this; just responding to the parent statement of "You can't circumvent measures that don't exist"
As I understand it, there are two definitions of technological measure in the DMCA. One is in the anti-circumvention portion, the other in the anti-cirvumvention-tool portion. In the latter case:
17 U.S.C. Sec. 1201 (b)(2) (B):
a technological measure "effectively protects a right of a copyright owner under this title" if the measure, in the ordinary course of its operation, prevents, restricts, or otherwise limits the exercise of a right of a copyright owner under this title.
(A) to “circumvent protection afforded by a technological measure” means avoiding, bypassing, removing, deactivating, or otherwise impairing a technological measure; and
(B) a technological measure “effectively protects a right of a copyright owner under this title” if the measure, in the ordinary course of its operation, prevents, restricts, or otherwise limits the exercise of a right of a copyright owner under this title.
I don't believe the protections that youtube-dl works around qualify under the definition 1201(b)(2)(B) here, but I would definitely want to confer with a lawyer before posting a DMCA counterclaim.
I think youtube-dl failed 1201(a)(2)(C) and 1201(a)(2)(C) because of that README. Like I said, they should fix the README. However, I still consider it rotten that they would forcibly take down a project as big as youtube-dl because of something so innocuous.
A simple "cease and desist" against the youtube-dl project regarding their README examples almost certainly would have been sufficient. Instead, the RIAA took needlessly drastic measures with a DMCA takedown that paints RIAA as a poor defenseless victim from start to finish. This was not an attempt to right a minor copyright infringement, this was a public declaration from RIAA that they are aware of and object to the youtube-dl project.
This part of the DMCA takedown document is particularly rotten:
> The clear purpose of this source code is to (i) circumvent the technological protection measures used by authorized streaming services such as YouTube, and (ii) reproduce and distribute music videos and sound recordings owned by our member companies without authorization for such use.
Lawyers are not engineers. Corporate lawyers are mercenary thugs with assistants, expensive suits, and very very very high daily rates.
This is the kind of thing is that lawyers do, because this is what they're paid to do.
You cannot win this by simply saying "Hands off our code - this is outrageous" because that's not how the law works.
If you want to make an argument agains this you literally have to make it stand up in court, and that is not easy.
While lawyers are sometimes foul and shameless creatures, the engineering community does not seem to understand that it is not playing on its own turf here.
If you do not take the time to understand the rules of the game you will lose hard. In this case the RIAA could easily have sued for damages and loss of earnings - and it would probably win that case if it came to court, although someone in counsel probably argued (wisely) that it wouldn't be worth the Streisand Effect damage.
Reading (A) and (B), I cannot help but notice that it doesn't matter whether the primary purpose of the circumvention is to infringe copyright. It is enough that the software/service is primarily about circumventing the "technological measure".
The technological measure itself doesn't even have to be primarily about preventing copyright infringement. It suffices that it effectively controls access to relevant works, even if it's not its primary purpose.
We could even argue that YouTube's restriction are primarily a means of getting people back to YouTube, with copyright enforcement being only a secondary concern. Sadly, this argument would be irrelevant with respect to (A) and (B).
It does, "ordinary course of operation" means "the most obvious use" and they took the tool as circumventing, looking at the test cases that are intended to succeed in circumvention.
No, really, it doesn't. It just makes the RIAA's case that much easier, makes YouTube-DL look bad. (A) and (B) above however are broader than that.
It doesn't matter that the technological measure is primarily about restricting access to protected works. It only matters that it effectively does restrict that access.
It wouldn't even matter if Youtub-DL is only used to access public domain videos, because their primary mode of operation would still be to circumvent the technological measure (assuming that measure restrict access to all works, not just the protected ones).
A "new" tool branded as a way to download public domain videos hosted on various web sites such as YouTube, (let's call it "Public Domain Tubes Archiver"), would still infringe on (A) and (B) if downloading those public domain videos primarily involved going around a technological measure that happens to restrict access to (unrelated) protected works.
The RIAA had a hard time too until the EU wrote the shitty laws their entire argument is based on (though what relevance those have to the DMCA is anyone's guess).
> Let's issue a takedown for the GNU Project while we're at it because I could use wget to do the same thing. In fact, I could write my own program to illegally download content, so we better just get rid of computers altogether.
I think the argument here is that explicitly, you can't with wget. youtube-dl specifically has circumventions for access controls for things like encrypted HLS, YouTube's ciphered player, etc.
It could download instructions and coordinating communication for drug manufacturing, money laundering, and terrorism! Add them to pædo porn and you have the Four Horsemen of the Infopocalypse! https://en.wikipedia.org/wiki/Four_Horsemen_of_the_Infocalyp...
Why stop there? Telnet can be used. Or what about wireshark? Let's ban those too. While we're at it, C++ can be used and other programming languages as well. We could keep going.
Digital Audio Tape DAT -- they tried REALLY hard to keep this technology out of the US market. Eventually they got a the authorities to impose a surcharge per blank DAT tape for 'lost income'.
Writable CDs came soon after which was probably going to kill DAT market no matter what.
Since the original version of DDS tape is basically just DAT tapes being used to store computer data, many of the commercially-available DDS drives could be re-flashed to allow them to read DAT as well. (Re-flashing was necessary to remove the software restriction that otherwise recognised DAT tapes and refused to read them).
I'm not going to post any links, but there's plenty of info online.
Even if we restrict the target set to "tools with a high likelyhood of being used for an illegal purpose" which I believe youtube-dl belongs in, when is the RIAA going after "guns"?
If you sell a "murderizer 3000" and explain in the owner's manual how to inflict a fatal wound and maybe also not leave any evidence behind it doesn't take a genius to argue you're selling a murder weapon, to murderers.
Right, that's my point. You can't make a tool called Youtube-dl with source controlled test cases that download copywritten material from Youtube and then claim it's not for downloading copywritten material from Youtube.
As a technical aside (to the main topic of this HN thread), I had written a blog post some years ago, describing some uses of youtube-dl, and some commentary giving an overview of what its source does:
Very pathetic that Github took this repository down. I was about to move our company code over to Github from self hosted Gitlab, this move has put the a the brakes on that.
If anyone thinks that Github had no choice but to follow the legal notice, I want to mention that youtube-dlc [1], a community fork of youtube-dl, is also taken down. This fork is not even mentioned in the DMCA notice [2]. Github is complicit in this.
Don't do this. This is how gamergaters destroyed people's lives. It starts with a little bit of doxxing and it ends with well meaning humans (who you happen to disagree with) hiding on their high school friend's couch, two states away from their families.
I get that, and yeah it's bad. But there's also a deep frustration with how these fuckers can do this stuff and get away with it. So how does one push back?
If they’re willing to fight it, help pay their legal fees. Win in court, set a better precedent.
That is how change happens in the world, not by trying to ruin the lives of individuals emblematic of a flawed system but quite likely perfectly decent people in and of themselves.
I’m not sure that justice was the goal here; what the RIAA does is not illegal, and nor are the annoyances and other shunning behaviors that were suggested.
I don’t think “vigilante” or “angry internet mob” are accurate descriptions, either.
You don’t need to be angry, or a vigilante, or seeking “justice” to wish negative consequences for certain (legal) choices made by others in society, such as working for the RIAA or other such jobs that make our world and society worse.
It’s a false dichotomy to think the only two options are “do nothing to hinder them” or “angry internet mob”.
Legal, harmless ways of discouraging certain choices are perhaps one of the best tools available to us for improving our society, in many different contexts.
Making dubious legal arguments and demands is what the sovereign citizens do and that's the same thing as what the RIAA is doing here. We shouldn't legitimize their techniques because it's couched in a pseudo-legal framing, but we should engage in action-for-action.
Github is obligated to take down the "offending" content as soon as they receive a DMCA notice. It's then on the owner of that content to file a counter claim to restore it.
Even if the content is not in violation of DMCA, your files will be gone for a day or two, or longer depending on how slow the publishing platform operators are to process the counter claim and how long it takes to file the counter claim.
> Github is obligated to take down the "offending" content as soon as they receive a DMCA notice.
No, they aren't obligated to do anything.
Github is immunized from any liability they would otherwise have to the complaining party for hosting the material affected by the notice if they comply within the parameters of the DMCA safe harbor provision (which requires action "expeditiously" rather than "immediately") when they receive a notice.
This is semantics. Because github absolutely would not be able to exist if it lost its safe harbor protections.
So, it is "obligated", in that if it does not follow these laws, then it will 100% have shut down, eventually, due to business reasons.
If the alternative to doing a certain action, is that your business will almost certainly be shut down eventually, then I think that is a reasonable situation to use the word "obligated" for.
> Because github absolutely would not be able to exist if it lost its safe harbor protections.
It wouldn't lose them generally, just with regard to the act of hosting that specific item. Without commenting on the particular case, if the claimed theory of infringement was patently frivolous on its face, even if the notice was formally valid under the DMCA, it would be reasonable for a provider to ignore the notice because they had insufficient risk of liability to concern themselves with.
(This is conversely why providers tend to be less good at responding to counter-notices, again, the only hammer is liability shield, but this is for any liability they would have to the person whose content was taken down for taking it down. As this is usually none to start with, they are quite free to be cavalier with counter-notice process.)
Has anyone tried sending automated DMCA for the entirety of Github? Once half of github is under bogus DMCA, maybe that'll make them think for a minute.
You as a random person would be committing what's essentially (or actually?) perjury and I'd expect you'd either be ignored or prosecuted. Big companies seem to get freebies on this, doubt you would.
It sounds like the RIAA is comfortable filing DMCA takedowns when the logic is questionable.
If so, then I'm curious about the legality of a counter-attack: Look at any websites, photos, music, videos, and text presented online by everyone represented by the RIAA. If anyone in a competent jurisdiction sees any similarity to prior art that they've created, even if it's their 2nd grade writing assignment, hit them with a DMCA takedown notice.
After all, we just need a good-faith belief that it might fly in some court somewhere, right?
This is part of the DMCA process. Github takes it down until they get a counter-claim from the repo owner, don't think they really have much of a choice in it, legally.
> This is part of the DMCA process. Github takes it down until they get a counter-claim from the repo owner, don't think they really have much of a choice in it, legally.
They have a choice, but if they would be liable for hosting the content but for the DMCA safe harbor, failing to take it down when they receive compliant takedown notice means that they are then exposed to that liability because they are outside of the safe harbor.
It is messed up in practice, yeah. The counter to that is supposed to be that if you submit totally bogus claims you can be prosecuted for an actual crime, but as far as I know that never happens, at least for the big players.
What is the simplest way to store source code repos in some decentralized file system? Like store git repo in IPFS folder, would others be able to clone it and submit pull requests?
it's already decentralized. now developers just need to setup a different remote. as in git remote add whatever. the problem is how to publish the software.
I'm speaking exactly about decentralized publishing. Where the repository is mirrored in content addressed network, so there is no specific location(s) to take down.
(I realize it is problematic, because even with content addressed mirroring, the people who actually host the replicas of the content, can be accused of distributing prohibited content, but still it's more difficult to censor, and maybe those problems are solvable).
Super surprising that software like this could exist in the legal space and with known creators. I mean, it's obviously a pirating app, it makes every effort to circumvent download protection right?
It's a generalized tool just like a hammer, the dreaded murder or construction weapon depending on intent..
The DMCA has always been a way of forbidding tools, as if that's the kind of nanny state we want: trusted with assault rifles but not trusted with a python script.
I doubt there will be many pro-RIAA perspectives here so as someone familiar with their leadership and goals, I might as well add some perspective.
Imagine yourself stumbling upon some incredible technology breakthrough. Let's say, it's some magical script you wrote that automatically improves the efficiency of any container by 70%+. You've worked for years on this specific problem, went broke a couple of times trying to figure it out, and finally struck gold. You form a company, issue that IP to the company, and start getting rich.
Then one day, literally Google comes along and posts your script to some website they own, without your permission. They did this illegally, without your permission, by using this other neat script called gofyourself-dl. You have a problem now. Every is improving their containers or whatever for free. Your company loses revenue every day because why would anyone pay you for tech they can get for free from Google?
What can you do? Sue Google? Good luck with that! No, you would complain to a regulator, which is the only real power (sort of) against that kind of money. You would try and convince that regulator to stop Google from stealing your IP and getting rich from it because it is YOUR IP and YOU should get rich from it. In the meantime, since gofyourself-dl is the way people are stealing your IP, you naturally try to get that taken down because IT IS BEING USED TO STEAL YOUR IP.
Stealing IP is exactly what YouTube is - and has been - doing, for years. There is this weird idea that the major record labels (who fund the RIAA) have unlimited money and are just as evil as blah blah blah, in reality the entire music economy is a minuscule fraction of Google's market cap, power, size, influence, everything, and large tech companies have no real incentive to deal with them in the standard cases because why would an elephant concern itself with an ant.
It sucks to do this to an open source repo, but everything they are saying in this memo is true - this technology is obviously being used to STEAL IP. Its primary focus is the THEFT OF IP. DMCA is a shitty blunt instrument that no one likes, don't for a second think the RIAA is thrilled with that mechanism, but what else are they supposed to do? What would you do if it was someone stealing your proprietary code and posting everywhere after having stolen it from you?
Your proprietary code analogy is incredibly weird. Why would anyone need gofyourself-dl to download your container code? And what does Google have to do with the creation of youtube-dl, which is used to download stuff hosted on Google's website? And you talked about publishing code, but where does youtube-dl publish the videos it downloads?
Or are you just implying that not executing all of Google's code and not watching a gazillion ads to download and view videos is some sort of "theft of IP"? Or is it that youtube-dl doesn't automatically delete the video after watching? I seriously don't get it.
> don't for a second think the RIAA is thrilled with that mechanism
What would they prefer doing? Arrest people who are using youtube-dl to listen to music? Go after people who are rehosting music from youtube on their website?
https://news.ycombinator.com/item?id=24872911&p=2
https://news.ycombinator.com/item?id=24872911&p=3
https://news.ycombinator.com/item?id=24872911&p=4
https://news.ycombinator.com/item?id=24872911&p=5