yt-dlp VS yt-dlc

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>

(Installation instructions are included in the documentation provided by both forks)

I) https://github.com/blackjack4494/yt-dlc

youtube-dlc is a fork of youtube-dl with the intention of getting features tested by the community merged in the tool faster

We love yt-dlp which is a youtube-dl fork based on the now inactive youtube-dlc. The main focus of the project is adding new features and patches while also keeping up to date with the original project.

ERROR: Channel Restricted; please report this issue on https://github.com/blackjack4494/yt-dlc . Make sure you are using the latest version; type youtube-dlc -U to update. Be sure to call youtube-dlc with the --verbose flag and include its complete output.

$ git init # initialize folder as git repo # add remotes to compare $ git remote add youtube-dl https://github.com/ytdl-org/youtube-dl $ git remote add yt-dlc https://github.com/blackjack4494/yt-dlc $ git remote add yt-dlp https://github.com/yt-dlp/yt-dlp $ git remote update # download info from remotes # show number of different commits $ git log youtube-dl/master..yt-dlc/master --oneline | wc -l # in yt-dlc, not in youtube-dl $ git log yt-dlc/master..youtube-dl/master --oneline | wc -l # in youtube-dl, not in yt-dlc $ git log yt-dlc/master..yt-dlp/master --oneline | wc -l $ git log yt-dlp/master..yt-dlc/master --oneline | wc -l $ git log youtube-dl/master..yt-dlp/master --oneline | wc -l $ git log yt-dlp/master..youtube-dl/master --oneline | wc -l # print list of different commits in a file $ git log youtube-dl/master..yt-dlc/master > orig-dlc.txt # in yt-dlc, not in youtube-dl $ git log yt-dlc/master..youtube-dl/master > dlc-orig.txt # in youtube-dl, not in yt-dlc $ git log yt-dlc/master..yt-dlp/master > dlc-dlp.txt $ git log yt-dlp/master..yt-dlc/master > dlp-dlc.txt $ git log youtube-dl/master..yt-dlp/master > orig-dlp.txt $ git log yt-dlp/master..youtube-dl/master > dlp-orig.txt

yt-dlc

Not who you responded to, but I use youtube-dlc. It's a command-line based utility with a ton of options for downloading YouTube videos.

https://github.com/blackjack4494/yt-dlc/commits/master

The previous update was July 25, and the one before that was December 2020.

While the July update dealt with the updater, having 2 days of small changes since December is not very active.