It's worth noting that YouTube is trialling a new player and a lot of applications (invidious, new pipe, etc) are experiencing some issues in the last couple of weeks.
It's worth noting that YouTube is trialling a new player and a lot of applications (invidious, new pipe, etc) are experiencing some issues in the last couple of weeks.
Besides how would you like to work in the YouTube "DRM" team, where every few weeks you'd show up to work and the news is "well, they cracked it again, your last few months' of work is useless.".
They aren't investing because its a CLI tool. Its not really a threat.
If it was, like, a "1 click download free music from Youtube!" app that was trending like crazy, Google would focus more on fighting it.
The project is balanced between reasonable accessibility and not drawing too much attention from Google. Its kinda like the AI Wars video game, where you undermine a distracted/disenterested AI without drawing too much of its attention.
Google, close your eyes!
https://f-droid.org/en/packages/free.rm.skytube.oss/
Bad Google! No dividends for you!
For example, mpv uses youtube-dl automatically if you give it a URL (or yt-dlp since it installs the same binary).
Last I checked (which was a very long time ago) the only way to rip a Blu-ray was through a commercial program.
That's probably partly because Blu-ray waned in popularity compared to streaming. Still I definitely think it's wrong to assume that Google couldn't win this battle.
I can rip Blu-Rays easily with freely available tools [0] - even shiny new UHD ones. Doesn't seem the industry won that one.
Pirates don't distribute the leaked device keys anymore so you need to get disc-specific encryption keys derived from that but that's all done automatically for you and I imagine is only because this is currently the path of least resistence - if this was not an option then device keys would leak faster than they can be removed from new releases.
> Still I definitely think it's wrong to assume that Google couldn't win this battle.
DRM is an inherently unwinnable battle. Won't stop anyone from trying and making things worse for regular users in the process though.
We would put in weeks and months of work to come up with a new method of fighting spam that would actually work [0], and over the span of a weekend after launch, the spammers would already have worked around it.
[0] As opposed to the random crackpot ideas that every damn stupid AOL VP came up with that started with "Why don't you just ...". If I had a nickel for every damn stupid AOL VP crackpot idea, I'd be a multi-millionaire by now.
I hope you used https://craphound.com/spamsolutions.txt as your resignation letter.
For me, by that time AOL had become a sufficiently toxic place that we came to a mutual agreement that it was time for me to leave.
If it hadn't been for that, I would never have gotten a chance to work at Collective Technologies, where we had more O'Reilly authors on staff than any other company in the world!
TPM1.2 (used up until a few years back) is already broken because it uses SHA-1. If someone finds an exploit for TPM2.0, a dedicated team could manipulate the entire sandbox down to the hardware to simulate a “blessed browser”, making it even harder for google to detect until nearly everyone moves to devices which don’t even exist yet.
If this were to change, then I'm sure the battle would look very different, both legally and from a technical viewpoint.