In this case I'm not sure why a convenience wrapper is even needed, yt-dlp already works with playlists just fine

    yt-dlp -o "%(channel)s/%(playlist_title)s/%(title)s.%(ext)s" -a playlists.txt

You can get RSS feeds of channels still. I use that in my feed reader

I, on the other hand, turned off YouTube recomendations with UnDistracted. Maybe I'm missing out; who knows.

Revanced you can still have the same algo. Also smarttubr

Exactly. There’s been account ban reports from it too. Id be very careful if it’s your normal google account that’s tied to YouTube. Always use a burner account when using the cookies param to be safe.

It’s wrapping a somewhat opinionated and mildly bizarre yt-dlp invocation, for each line of a file doing a mkdir/cd and then invoking yt-dlp.

—⁂—

From the “Features” section of the README:

> • Organized Structure: Creates separate directories for each channel.

… depending on you mentioning that name in your playlists.txt file, so that if you were writing a script you’d just be doing a mkdir/cd yourself, trivial.

> • Smart Sync: Skips files that have already been downloaded (--no-overwrites).

That’s not really what --no-overwrites does. The default of --no-force-overwrites is probably actually what you want: “do not overwrite the video, but overwrite related files”. You probably do want metadata files to be updated on subsequent runs.

> • Clean Naming: Saves files as Playlist Title/Video Title.mp4 (no numeric prefixes).

This is an Opinion.

> • Batch Processing: Reads multiple playlists from a playlists.txt file.

Meh, you’re invoking a script, putting the stuff in the script would be at least as easy.

—⁂—

From the script itself, going through the arguments passed to yt-dlp:

        --cookies "$COOKIES_FILE"

My impression is that this is discouraged unless necessary. And if you need it, --cookies-from-browser will be more convenient.

        -f "bv*+ba/b"

That’s equivalent to the default.

        --merge-output-format mp4

This is an Opinion.

        --no-overwrites

I’m not convinced this is desirable. Videos already won’t be overwritten by default, this just stops metadata from being updated on subsequent runs, though I’m not sure what things might be updated.

        -o "%(playlist_title)s/%(title)s.%(ext)s"

This is an Opinion.

—⁂—

Instead of having a playlists.txt file containing `Channel Name|https://www.youtube.com/playlist?list=x` and having a separate 73-line file download_playlists.sh, you might as well have just one download_playlists.sh file containing:

  dl() {
    mkdir -p "$1"
    pushd "$1"
    yt-dlp -o "%(playlist_title)s/%(title)s.%(ext)s" "$2"
    popd
  }

  dl 'Channel Name' 'https://www.youtube.com/playlist?list=x'

By dint of its simplicity, easier to work with and tweak to your own requirements (such as dropping `--merge-output-format mp4` as I did here). Also more obvious how to invoke it just once. (Aside: use pushd/popd instead of `cd "$channel_name"` and `cd ..`, because then $channel_name containing a slash won’t bork it.)

Or... just pay them that thing called money, and use the buttons in the YouTube app.