yt-dlp VS youtube-dl-server

You can put these options in a config file and they will become the default: https://github.com/yt-dlp/yt-dlp?tab=readme-ov-file#configur...

Yep. yt-dlp and youtube-dl

https://github.com/yt-dlp/yt-dlp

https://github.com/ytdl-org/youtube-dl

Will also start to feel the impact. My theory is that we will see a bunch of new video hosting sites as youtube itself attempts to lock down its ecosystem. They haven't paid attention in any adversarial way as far as I can tell.

When they do, it wont be great.

The points you make aren't unreasonable.

It is necessary to establish clear boundaries of what can and can be provided by the maintainers. If not done at an earlier stage of the project, the support burden becomes too much to bear at which point the maintainer transfers ownership, and the project suffers from catastrophic consequences such as the xz backdoor we're talking about here, or other cases where the project mostly stalls and serves as an ego-boosting platform for the new maintainer, as was the case with PhantomJS[6].

This can also happen in your life, where a "friend" sees that you possess a certain skill, and then gradually tries to push an inordinate amount of their personal work related to this field onto you.

Personally, I think it's best to use an approach with extremely clear communication as to what the maintainer can and cannot provide. This can be seen, for example, in yt-dlp[1], where the consumer is clearly informed upfront that not providing detailed information as requested will lead them to block said consumer; or sqlite where their position regarding contributed patches[2] and support[3] is similarly made clear.

Having a shouty BDFL like Torvalds can also help improve code quality[4] and questionable contributions[5], though it is better that the shouty BDFL makes statements that are professional and do not show as much aggression; so for example, "Mauro, shut the fuck up"[7] would become "Mauro, your response is completely unbecoming for a Linux kernel maintainer, and is not in line with the promise of not breaking userspace."

[1] https://github.com/yt-dlp/yt-dlp/issues/new?assignees=&label...

[2] https://www.sqlite.org/copyright.html

[3] https://www.sqlite.org/support.html

[4] https://www.theregister.com/2024/01/29/linux_6_8_rc2/

[5] https://cse.umn.edu/cs/linux-incident

[6] https://github.com/ariya/phantomjs/issues/14541

[7] https://lkml.org/lkml/2012/12/23/75

Or just "yt-dlp "

yt-dlp ( https://github.com/yt-dlp/yt-dlp ) still works pretty well at the current state of Twitter.

To download audio from YouTube videos, you'll utilize the widely used yt-dlp library, which can be installed using the pip command as follows:

Use: `yt-dlp with --write-comments --no-download --batch-file FILE`

- FILE is a text file with a list of YouTube id's/URL's

- https://superuser.com/a/1732443/4390

- https://github.com/yt-dlp/yt-dlp

> Then youtube-dl wasn't a thing anymore (maybe it is again?)...

yt-dlp is definitely a thing: <https://github.com/yt-dlp/yt-dlp>

Second, you need something to download the youtube videos so that they are available as files in Plex. for that I use the youtube-dl-server project because it does a few things:

I use a youtube-dl-server fork which has the yt-dlp as option with nbr23/youtube-dl-server:yt-dlp

Not quite the same idea/feel, but I've been using youtube-dl-server for some time. It supports/has yt-dlp as an option. if anyone is just looking for similar projects in general.

Or better yet, just host something like youtube-dl-server.

If it's something I'll be watching in Plex, I use a docker container running youtube-dl-server+youtube-dl to import it. I have an identical container set up for my SO so she can add her own stuff into her Plex libraries. I'll eventually be swapping out youtube-dl for yt-dlp in these containers.