I am getting the following error after upgrading yt-dlp

ERROR: [Piracy] This website is no longer supported since it has been determined to be primarily used for piracy. DO NOT open issues for it

Does anyone know any forks that still works.

  • Stefen Auris
    link
    fedilink
    English
    587 months ago

    Wow really? That’s kind of a shitty stance for them to take.

    • @laz@pawb.social
      link
      fedilink
      English
      337 months ago

      True, but sadly the kind of one they must take to avoid being hit with a cease and desist.

      • @Moonrise2473@feddit.it
        link
        fedilink
        English
        57 months ago

        Especially when downloading from the other supported sites (example: YouTube) is already against their tos and technically, piracy

        • @far_university190@feddit.org
          link
          fedilink
          English
          127 months ago

          Copyright troll. They even hit manga reader app. Not even distribute any material, just a reader. Just because can load manga from piracy site.

  • @ReversalHatchery@beehaw.org
    link
    fedilink
    English
    38
    edit-2
    7 months ago

    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.

  • @HouseWolf@lemm.ee
    link
    fedilink
    English
    297 months ago

    Can you remember the last version that worked for you? A quick workaround could be downloading an older build off the github.

    Still this is extremely disappointing and hopefully someone forks it.

    • @Lemmling@lemm.eeOP
      link
      fedilink
      English
      167 months ago

      It used to work last year 😀 . The debian yt-dlp version: stable@2023.03.04 is giving a different error

      ERROR: [Einthusan] 9r1H: 9r1H: Failed to parse JSON (caused by JSONDecodeError(“Expecting value in ‘’: line 1 column 1 (char 0)”)); please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U

  • hendrik
    link
    fedilink
    English
    247 months ago

    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.

  • @themoonisacheese@sh.itjust.works
    link
    fedilink
    English
    127 months 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)

      • TXL
        link
        fedilink
        English
        157 months ago

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

        • Snot Flickerman
          link
          fedilink
          English
          167 months ago

          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
            link
            fedilink
            English
            97 months ago

            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’.

            • TXL
              link
              fedilink
              English
              27 months ago

              Right. Site plugins or something.