Steve Ballmer would be proud!* Developers, developers, developers!!! *) and throw chairs at the RIAA
YouTube-dl's repository has been restored
371–380 of 686 posts
Re: YouTube-dl's repository has been restored
#372Earlier quoted context omitted.
Right, but the law makes no mention of secret keys, it just says you can't go around anything that controls access to a copyright work; and you can't provide tools to do so. The actual legal definition of tools covers both actual technical purpose as well as marketed purpose. Rebranding, say, OBS as "Recorder for YouTube" and talking about how you can use it to get around YouTube's downloading protections by screenca…
The rebuttal to your reasoning is in the letter. Basically a federal judge has previously ruled that utilizing a publicly available password is not circumvention of a copyright protection mechanism. The code containing the "sig" (as google calls it) or "rolling cipher" (as RIAA calls it) is available to anyone by viewing the JavaScript. This sig / cipher being public means it is not a copyright protection mechanism.
I can see this as ending up with Youtube being forced to require sign-ins. Massive expense for Google. Then Youtube-dl adds one parameter for the password, and we're back to square one.
Re: YouTube-dl's repository has been restored
#373Earlier quoted context omitted.
That won't work, because Youtube applies the particular sort of protection that those tests exercise only to copyrighted music.
Interesting. Do you know how hard it would be for someone to upload a bunch of original videos with same copyright as the videos in question?
Which is why they were in the test suite.
Re: YouTube-dl's repository has been restored
#374Earlier quoted context omitted.
Sure, it would be "effectively a web browser". But it would also require a secret key. If the program is not licensed to hold the key, that could be considered circumvention.
Other browsers have the key, why would this one be different ?
Re: YouTube-dl's repository has been restored
#375Earlier quoted context omitted.
AFAIU the argument is more that youtube-dl is effectively a web browser and doesn’t do anything that a web browser doesn’t do. Further, it does not include any “secret” key for DRM circumvention like might be bundled with e.g. Chrome in the case of Widevine, where browser vendors agree to protect the secret key.
If a program had its own implementation of widevine, why wouldn't you also be "effectively a web browser" ?
Re: YouTube-dl's repository has been restored
#376Earlier quoted context omitted.
I wonder how much MS funds the RIAA as a member of it.
Dues are $2500/y if you have revenues of $1-5MM, $5000/y if you have revenues of $5-15MM, and "contact us" beyond that: https://www.riaa.com/wp-content/uploads/2015/09/RIAA_ApplyFo... Since one presumes that Microsoft does not sell much music (didn't they shut down their music store a few years ago?), I can't imagine they've negotiated dues that scale linearly on Microsoft's total revenue - so, in fact, I'd expect th…
Re: YouTube-dl's repository has been restored
#377Earlier quoted context omitted.
If you want to put your everyday Amazon spend to good use, don't spend on Amazon.
Where do I spend it wise one
edit.... don't use google. Use duck duck go. :-)
Re: YouTube-dl's repository has been restored
#378Earlier quoted context omitted.
To be honest, I had no idea youtube-dl did anything else other than download YouTube videos. What other functions does it have?
It supports a lot of video sources [1], not just Youtube. [1] https://github.com/ytdl-org/youtube-dl/tree/3f1748b9445e9d93...
Re: YouTube-dl's repository has been restored
#379Earlier quoted context omitted.
I don't believe that Github actually needed the EFF's writing for this, or that they don't have the necessary technical expertise themselves. That is probably rather a protective assertion not to lose face. But at least they seem to have learned something from it now and want to review such requests technically before they (unjustifiably) act.
Github links to the EFF letter [0] in the DMCA repo. This letter spells out in clear, convincing and explicit detail why the RIAA was wrong. Profit-making Github and Microsoft could have performed this analysis and championed developers themselves, but it was the non-profit EFF that actually did the work. EFF deserves more credit than just a link for fighting against this shit. [0] https://github.com/github/dmca/blob…