Client Challenge
pypi.org

tubeup uses yt-dlp to download a Youtube video (or any other provider supported by yt-dlp), and then uploads it with all metadata to the Internet Archive using the python module internetarchive. It was designed by the Bibliotheca Anonoma to archive single videos, playlists (see warning below about more than video uploads) or accounts to the Internet Archive.

Prerequisites

This script strongly recommends Linux or some sort of POSIX system (such as macOS), preferably from a rented VPS and not your personal machine or phone.

  • Dessalines@lemmy.ml
    41·
    1 day ago

    I like this idea, but I wish someone would create a torrent-based project based on yt-dlp, and in particular a browser plugin that checks a torrent search site or index to see if that youtube video torrent exists.

    Internet archive isn’t as fault-tolerant as torrents, and also wouldn’t be able to handle so many massive files.

    • black_flag@lemmy.dbzer0.com
      4·
      1 day ago

      This seems like a really great idea. In theory, it’s just a simple key value store with the key being the YouTube tag and the value being a magnet link. I see a problem though. When a user submits a new association between a Magnet Link and a YouTube tag, what verifies that that’s actually the appropriate file? It seems almost like the server would have to download the video itself, which could pose a really unreasonable load on it. Especially compared to the very simple task it initially set out to do. But without that verification, it seems very prone to abuse (e.g. someone submits every tag and says they’re all the rickroll video)

      It definitely seems worth doing though.

      • Dessalines@lemmy.ml
        3·
        1 day ago

        When a user submits a new association between a Magnet Link and a YouTube tag, what verifies that that’s actually the appropriate file?

        In one sense, its not really a problem, since torrents are static data. Incorrect files would not only look wrong (and not be seeded as a result), but have different hashes than the youtube ones. But the service which hosts / shares these magnet links would need to source the uploaders, so that their torrents could be removed if it turns out they’re spam.

        I run a csv-based torrent service, but after many years, I’ve been the only one to really contribute to the data. There the process of adding data is tracked via pull requests. Any other service though which allows ppl to upload magnet links / torrent files would need to have a login system / tracking to prevent spammers.

        • black_flag@lemmy.dbzer0.com
          3·
          16 hours ago

          Wow, thank you very much for your service in creating that.

          I don’t think this particular thing would need a login feature, since there’s a known genuine source we can check their work against. Like you said, it’s hash based, so the first time someone posts a video, you just download that from YouTube official and check the hash, no?

          • Dessalines@lemmy.ml
            2·
            15 hours ago

            Like you said, it’s hash based, so the first time someone posts a video, you just download that from YouTube official and check the hash, no?

            Yep, that’d be the case. But also for that service at least, it only stores currently active / well-seeded torrents. And the main issue is that people aren’t creating and seeding youtube videos as torrents. That would require some effort and a push from the datahoarder-type communities to start doing that.