bandcamp-downloader VS yt-dlp

Two projects I greatly appreciate, allowing me to easily archive my bandcamp and GOG purchases (after the initial setup anyways):

https://github.com/easlice/bandcamp-downloader

https://github.com/Kalanyr/gogrepoc

And I recently learned about archivebox, which I think is going to be a fast favorite and finally let me clear out my mess of tabs/bookmarks: https://github.com/ArchiveBox/ArchiveBox

Reminder to archive all purchases

https://github.com/easlice/bandcamp-downloader

I have a windows oriented “get past setup pain points” tutorial here: https://github.com/easlice/bandcamp-downloader/issues/21

For generating a cookie file, I suggest just using https://github.com/hrdl-github/cookies-txt

Make sure to archive your bandcamp collection, which you can do with the following script: https://github.com/easlice/bandcamp-downloader

I have a straightforward guide on how to get up and running on windows here: https://github.com/easlice/bandcamp-downloader/issues/21

You should always archive your collection anyways. One negative thing about bandcamp is that artists/labels/bandcamp can remove anything at anytime for any reason, so things you paid for can straight up disappear. This was very disappointing to discover. Note that sometimes things are set as hidden, rather than outright removed. This info may be outdated, as the relevant support page seems to gave changed from the last time I looked at it.

Because of their no DRM policy and full on downloads, not just streaming, Bandcamp has basically become the only place I’ll buy music outside of CDs.

I’m happy enough to hand artists money if it’s easy and I can archive a lossless copy, but if they start fucking around with things, I’ll go right back to doing what I was before. That said, if they fix the outright removal of paid things problem, and start treating “artist” as first class instead of “label” in searches and links, I’ll be singing their praises.

Bandcamp is what I use.

One thing to note, is that the artist/label retain full control of what music is present, and as such can be removed at any time, even ones you paid for. See: https://get.bandcamp.help/hc/en-us/articles/4406122372119-Wh...

I use https://github.com/easlice/bandcamp-downloader to immediately archive flac files to my NAS after a purchase, then convert to those to a lossy for space saving format for mobile playback/family sharing as desired with a playlist. This way I have my archive, and the artists I like get their support.

2) Download this code from the repo

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>