I don't think a fork will solve anything. I'm pretty sure the reason they did this is to cover their asses (don't forget that it was very near to being taken down just a few years ago).

Further, yt-dlp has implemented plugin support, for this exact reason. I think that's a new feature compared to youtube-dl. You can add your own extractors as plugins, wherever you find them. As I remember there are a few plugins that are even maintained by a yt-dlp maintainer.

If you find this to be ok or better, please consider changing the title to let those know about what's happening who have already read the post, because they wouldn't know it otherwise.

[–] Flatworm7591@lemmy.dbzer0.com 28 points 1 year ago* (last edited 1 year ago)

See https://forums.freebsd.org/threads/yt-dlp-error-piracy-this-website-is-no-longer-supported.93995/ for some pertinent comments.

See list of forks here https://github.com/yt-dlp/yt-dlp/forks. If you find one that works, let us know.

[–] DoucheBagMcSwag@lemmy.dbzer0.com 28 points 1 year ago (1 children)

Time to fork it with a non pussyfied version

[–] KomfortablesKissen@discuss.tchncs.de 11 points 1 year ago

A plugin for yt-dlp will suffice. It's also easier to maintain.

[–] hendrik@palaver.p3x.de 24 points 1 year ago (1 children)

Maybe you can find some more discussion and the reasoning in their documentation or Github issues or pull requests. I bet this has been discussed before someone implemented it. Maybe there's also a way to restore the old behaviour.

[–] ReversalHatchery@beehaw.org 7 points 1 year ago

There is, they added plugin support. See my top level comment for details

[–] winterayars@sh.itjust.works 17 points 1 year ago (1 children)

This isn't going to make the copyright holders hate them any less.

[–] KomfortablesKissen@discuss.tchncs.de 9 points 1 year ago

But it IS giving the copyright holders less attack surface to bite into. Haters gonna hate, let them.

[–] themoonisacheese@sh.itjust.works 12 points 1 year ago

The most likely explanation is that their previous implementation broke due to a website change, and they didn't want to bother with fixing it. People began opening issues for them to fix it, but now it looks like they're aiding people explicitly asking for piracy, so they can't win (and also I'm willing to bet it fucking sucked trying to support that particular website)

[–] mbirth@lemmy.ml 8 points 1 year ago (1 children)

Is that an indirect plea to open an issue for it? We should do this.

[–] Lemmling@lemm.ee 16 points 1 year ago (1 children)

They are closing all issues citing piracy https://github.com/yt-dlp/yt-dlp/issues?q=is%3Aissue+piracy+is%3Aclosed

[–] XTL@sopuli.xyz 15 points 1 year ago (1 children)

Could be a liability for them to have to work on support for those sites when it breaks.

[–] SnotFlickerman@lemmy.blahaj.zone 16 points 1 year ago (1 children)

Sounds like its time for a pirate fork... maybe yt-dlpirate?

I mean, fuck it, one of the big private trackers could do releases, kind of like how Bibliotik does releases of those tools to strip DRM from ebooks.

[–] adarza@lemmy.ca 9 points 1 year ago (1 children)

some way to call a custom or 'third party' (not compiled into the program) extractor would probably be enough. then let other people work on ones for the, um, 'problem sites'.

[–] XTL@sopuli.xyz 2 points 1 year ago

Right. Site plugins or something.

[–] onlinepersona@programming.dev 7 points 1 year ago* (last edited 1 year ago)

Fork it and put it on radicle or I2P. The MAFIAA can go fuck themselves.

Anti Commercial-AI license

[–] beeng@discuss.tchncs.de 5 points 1 year ago

What sites for eg?