I am the developer of a project with a small community known as Offflix. Now I recently discovered that Yts has an api, and it is too irresistible for me to integrate it into my project as a simple in app click to download any movie.

So, would doing that and making the code open source be illegal? I am not a US citizen and I am not technically ripping movies, I am just packaging yts’s functionality inside my app. Would github flag and destroy me repo if I do this?

  • madnerds@lemm.ee
    link
    fedilink
    English
    arrow-up
    23
    ·
    5 hours ago

    Probably a bad idea. If you really wanted to do it, you should add plug-in support to your main project, then create a separate repo, maybe under a different account, with the potentially illegal yts download plug-in. That way only the plug-in repo would get DMCAed and could be mirrored by other people, or hosted off GitHub.

    • IsoSpandy@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      But even if I developed a plug in, for the plug in to work, I would have to bundle a torrent engine and anything that allows movies/series to be downloaded might get flagged I guess

  • zbyte64@awful.systems
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 hours ago

    GitHub definitely would and has in the past. YouTube-dl is on GitHub and gets a pass because it is used by researchers and archivists, both are fair use. forgejo.org would let you be your own fedi-github and might be worth checking out (could be easier than designing a plugin system and additional repos).

    • IsoSpandy@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      Codeberg wouldn’t mind according to that principle right? I cant fathom how a plug in would work when essentially adding yts would mean bundling a Downloader with a torrent engine and any system that allows downloading movies/series via torrent would get dmca.

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    8
    ·
    5 hours ago

    I think the way lots of projects handle something like that is to add a plugin system to the main project, and then offer it as a plugin in a different repo.

  • thetaT [none/use name]@hexbear.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 hours ago

    make this functionality into a plugin that you publish under a different account, that way you can have this functionality while maintaining plausible deniability