Hey rg3 your link https://yt-dl.org/supportedsites.html is broken. Great tool btw thanks for all your efforts.
Origins of the youtube-dl project
41–50 of 66 posts
Re: Origins of the youtube-dl project
#42I've had a personal playlist of videos I maintained since 2008, a collection really, with multiple fads I once used to share with the various social circles I had during the last decade at college and university. But now more than half of the videos are gone due to the various ban episodes YouTube had (FU cancel culture, FU Carlos Maza). Fortunately with YTdl I can save at least half of what has been my good fairly big portion of my adult life.
Re: Origins of the youtube-dl project
#43Earlier quoted context omitted.
If I run that script in an infinite loop, downloading the same persons photos, can I make they go bankrupt?
this is as stupid as saying "evolution isn't real otherwise I could grow eyes on stalks when I want to see around corners"
Not really, being against copyright (or at least against calling it theft) is a pretty defensible stance.
Re: Origins of the youtube-dl project
#44Earlier quoted context omitted.
This story clearly illustrates the purpose behind "web APIs". To limit access. As a user (not a web developer), I personally never saw the practical point of web APIs; I have always just "scraped the HTML". Many times the solutions I write outlive the corresponding "API"; IME, often the non-API method of data retrieval is more robust and reliable than using the so-called API. YouTube used to have a freely accessible…
The purpose of APIs it to provide a “uniform” interface. HTML layouts can change. JavaScript could be added to download the images after page load. An API shouldn’t change as often. And if the API is “versioned”, you can usually use the old version (old HTML layout) for a while before you upgrade (compared to your tool breaking as soon as the HTML changes).
In theory, yes. In practice, no.
Re: Origins of the youtube-dl project
#45Thanks for this. It is weird how long it’s been. I totally forgot that Wireshark was once called Ethereal. I hope that the DMCA takedown issue can be resolved reasonably, but it’s starting to seem more and more like a move off of Github is overdue. Especially in a world where anyone can stand up a Gitea or Gitlab CE instance.
> I hope that the DMCA takedown issue can be resolved reasonably, I don't think it can be solved on Github. "GitHub’s CEO suggested that YouTube-DL won’t be reinstated in its original form. But, the software may be able to return without the rolling cipher circumvention code and the examples of how to download copyrighted material." https://torrentfreak.com/riaas-youtube-dl-takedown-ticks-of-... This pretty much make…
it's not working since a couple of days, but i have been using mpv+youtube_dl for bandcamp listening for years.
Re: Origins of the youtube-dl project
#46Earlier quoted context omitted.
This story clearly illustrates the purpose behind "web APIs". To limit access. As a user (not a web developer), I personally never saw the practical point of web APIs; I have always just "scraped the HTML". Many times the solutions I write outlive the corresponding "API"; IME, often the non-API method of data retrieval is more robust and reliable than using the so-called API. YouTube used to have a freely accessible…
The purpose of APIs it to provide a “uniform” interface. HTML layouts can change. JavaScript could be added to download the images after page load. An API shouldn’t change as often. And if the API is “versioned”, you can usually use the old version (old HTML layout) for a while before you upgrade (compared to your tool breaking as soon as the HTML changes).
That is the promise of APIs, but there is no guarantee.
Re: Origins of the youtube-dl project
#47Earlier quoted context omitted.
> I hope that the DMCA takedown issue can be resolved reasonably, I don't think it can be solved on Github. "GitHub’s CEO suggested that YouTube-DL won’t be reinstated in its original form. But, the software may be able to return without the rolling cipher circumvention code and the examples of how to download copyrighted material." https://torrentfreak.com/riaas-youtube-dl-takedown-ticks-of-... This pretty much make…
it's not working since a couple of days, but i have been using mpv+youtube_dl for bandcamp listening for years.
What? youtube_dl supports bandcamp?! It's great news for me (I knew youtube-dl supports a huge number of video sites, but didn't know bandcamp). I'll immediately start using it today. Just like you, not really that interested to actually download the music but just to use it with mpv. Thanks for the tip.
Re: Origins of the youtube-dl project
#48Earlier quoted context omitted.
While I can understand your frustration, I also understand the frustration of photographers and other creators trying to make a living who have their work stolen. Their anger was wrongly directed at you, but it is a real problem.
I would argue that the "stealing" does not happen at the time of download; after all the photos are free to view on Flickr as many times as you want, and your browser needs to 'download' them in order to show them to you. Saving a copy to your own hard drive for offline viewing does not fundamentally change that interaction. It is only when you re-publish the photos that it becomes theft of intellectual property.
Try convincing the RIAA of your (perfectly valid IMO) argument...
Re: Origins of the youtube-dl project
#49Earlier quoted context omitted.
This story clearly illustrates the purpose behind "web APIs". To limit access. As a user (not a web developer), I personally never saw the practical point of web APIs; I have always just "scraped the HTML". Many times the solutions I write outlive the corresponding "API"; IME, often the non-API method of data retrieval is more robust and reliable than using the so-called API. YouTube used to have a freely accessible…
The purpose of APIs it to provide a “uniform” interface. HTML layouts can change. JavaScript could be added to download the images after page load. An API shouldn’t change as often. And if the API is “versioned”, you can usually use the old version (old HTML layout) for a while before you upgrade (compared to your tool breaking as soon as the HTML changes).
The purpose of an API is like a company mission statement: There's one version written on the wall and then there's the actual version everybody knows is true but they don't say it out loud.
You described the written one above. GP described the actual one.
Re: Origins of the youtube-dl project
#50I don't know if this is related or not but back when Flickr was popular in like 2005 or 2006 my friends and I were uploading pictures of our events there (they're all still there AFAIK. We'd upload them to either our own accounts or for certain events to a shared account. One shared account is here: https://www.flickr.com/photos/sourpower/albums I wanted copies of those pictures and the easiest way to get them was th…
I have a very similar story!
I maintain a similar project for SoundCloud called SoundScrape: https://github.com/Miserlou/soundscrape which I started for a similar reason, to save my own 'likes' and tracks that I've made and my friends have made.
SoundCloud made this very easy, as they had an API which exposed the endpoint MP3/WAV location in a field. The tool used an API key provided by SoundCloud to fetch the response.
Overnight and without warning, they removed that field from responses, changed the terms of service, banned my application for terms of service violations, and deleted all of my personal music and likes because I had used my own account to create the API key.
I was very angry at the time since all my my music got deleted, but these days I'm just sad. Things like this have little by little destroyed all of my enthusiasm for technology.
I want to be a carpenter now.