621–630 of 686 posts
I do fear though that this is going to lead some more and more paywall content and less and less publicly available content.
Earlier 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.
> When Petrolink learned that one of its largest customers, EOG Resources, might switch over to Digidrill’s visualization service, Petrolink took action. Instead of paying Digidrill for access to the corrected drilling data via LiveLog, Petrolink obtained a laptop running DataLogger – along with the corresponding USB security dongle – and then, after realizing DataLogger used an open source Firebird database, managed to gain access to the database by using Firebird's default administrator username and password. Armed with this access, Petrolink developed a program named “RIG WITSML” (dubbed “the scraper” or “the hack”) that could be installed on an MWD company’s computer running DataLogger in order to – in real time – query corrected drilling data from the DataLogger database and transfer that information to PetroVault for visualization. Petrolink then began installing this RIG WITSML program on MWD computers running DataLogger at more than 300 well sites.
[1] https://www.courtlistener.com/opinion/4765801/digital-drilli...
Earlier quoted context omitted.
Honestly, the name is problematic. Why do some developers insist on bad names? Stop the bad names .. unpronounceable crap like xoyx-mp4, zycx10 should also be avoided .. what's wrong with vidl, or something simple like that? .. I'm half joking, but it's worth underscoring.
They literally had a test case in the repo for circumventing copy protection on youtube. I'm somewhat baffled they managed to get the repo reinstated given that's very much a violation of the DMCA.
Earlier quoted context omitted.
Fun fact, that inscription also contains of the few continuity errors in published Tolkien material. It starts with: > The Doors of Durin, Lord of Moria but as the Tolkien Gateway explains: > The name Moria means "Black Chasm" and was a derogatory description of the place which the Dwarves did not like, and was given after Durin's Bane took over the city in the Third Age. It is therefore a mystery why that name appea…
Another fun fact is that, the doors were built in cooperation between Elves and the Dwarves. Celebrimbor (also the guy who made all the rings except the one) and Narvi. The friendship between an Eleven and Dwarven kingdom was kinda rare. And thus, speak friend and enter
Earlier quoted context omitted.
AFAIU the argument is more that youtube-dl is effectively a web browser and doesn’t do anything that a web browser doesn’t do. Further, it does not include any “secret” key for DRM circumvention like might be bundled with e.g. Chrome in the case of Widevine, where browser vendors agree to protect the secret key.
that's how understood it as well: "youtube-dl stands in place of a Web browser and performs a similar function with respect to user-uploaded videos. Importantly, youtube-dl does not decrypt video streams that are encrypted with commercial DRM technologies, such as Widevine, that are used by subscription video sites, such as Netflix." "We presume that this “signature” code is what RIAA refers to as a “rolling cipher,”…
The forks still seem to be borked, hopefully they will get resolved. My fork[0] is still showing DMCA notice and shows that it's a fork of some repo I'm sure I never forked, I forked the original ytdl-org. [0] https://github.com/ozburo/youtube-dl
Yeah, my fork of the original also shows the same never seen before repo as source: https://github.com/ppawel/youtube-dl
Earlier quoted context omitted.
It's possible to duplicate your key from the lock. You need access to the key hole, a blank, and a file. The lock leaves scratches on the blank until it's been file down to the right spot
Ok, obvously I have too little experience in picking locks; or maybe you have different locks than we in Switzerland.
Earlier quoted context omitted.
I even sidestepped the obvious of loading widevine.so, running it, symbolic execution, etc. It's mostly a thought experiment to show how everything is stupid in the end. I'm afraid in a few months/years, we'll see the hardware security level to become mandatory for Netflix, etc. And then YouTube.
In the old days, someone who wanted to send you this kind of content would build and sell hardware for you to receive and play it (like a DVD player). Online streaming services have, in part, scaled so quickly because they run on the general-purpose computers that people already own. So they don't need to bear that hardware cost. These general purpose computers have been fertile soil to grow and nurture the seeds tha…
Earlier quoted context omitted.
You already have to sign in to view some videos, don’t you? Does YT-dL not have a way to handle those right now?
It does, but it's broken. https://github.com/ytdl-org/youtube-dl/issues/23860 The developers are not responding to the issue, and from what I understand it is borderline impossible to fix, because there is an entire security team behind the Google login protection. The only workaround is to login with a browser and copy the cookies from it to youtube-dl.