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
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.
> 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.)
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'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?
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.)
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.
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.
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.
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.
Obfuscation is clearly an accepted technological approach to security and control, if not always a good or effective one.
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.
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.
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.
The name is literally YouTube-dl not generic-video-stream-dl.
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
Meanwhile people will keep using JDownloader