3 ms·
> 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 librari
by AnthonyMouse 6y ago
> 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"?
- TeMPOraL 6y ago> 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.
- Reelin 6y ago> 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?)
- ldarby 6y ago> 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).
- feanaro 6y agoPeople 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.
- ldarby 6y agoIt 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.