every once in awhile i get a bug up my butt about sharing my massive, curated library… but every time i get distracted by the volume of steps it would take to create the necessary shit to seed and then find a place that would even take those seeds to index.

ami doin it wrong? why is it so hard? napster was easy.

  • Chewy@discuss.tchncs.deEnglish
    23·
    2 days ago

    Most public trackers don’t take uploads from unknown people to combat spam/malware.

    If you create a torrent and enable DHT/PEX it might get indexed by something like btdigg.com for people to find. It won’t be available on sites like 1337x.to. The advantage is your free to create a single torrent or any other organization you desire.

    Private trackers generally accept uploads or make it simple to request upload access. But they have upload rules you must follow.

    If you want to automate uploading there’s Upload-Assistant. UA makes it easy by creating a proper name and uploading to multiple trackers automatically.

    In any case you must have port forwarding configured to greatly increase the likelyhood of others actually being able to download from you. If you don’t want to do that on your router a VPN with port forwarding is the private option (ProtonVPN, AirVPN, IVPN, njalla and few others).

  • EtzBetz@feddit.org
    3·
    1 day ago

    I got into a private tracker and setup my stuff with radarr, sonarr, etc. to hardlink between my library and my tracked stuff. That way it’s quite nicely automated at least when downloading stuff there. I once moved my library to a new system which was a bit of a pain and I also dislike creating new stuff in the tracker… but I’m quite happy at how good automated it actually is for not being a product.

    • originalucifer@moist.catsweat.comOP
      5·
      1 day ago

      im at ~36000 episodes and ~2800 movies in a hierarchical library primarily used for kodi and jellyfin. each series/movie is in its own folder… season of series are in their own folders… all have xml data regarding each file, created by mediaelch.

      i already have a deluge container running over a vpn container so upload/download shouldnt be an issue… except i get a different ext address on the tunnel when i reconnect every once in awhile.

      it just feels stupid i have this beautiful thing i cant share with the world without a mess of scripting

      • onlinepersonaEnglish
        3·
        1 day ago

        Hmmm, is your goal to share each season folder separately? Is that why you would need scripting?

        Or are you looking to share everything at once without worrying about creating individual torrents? If this is what you’re looking for, then maybe Retroshare is what you’re looking for? I don’t know if stuff using eDonkey, Gnutella, or Kademlia are still around, but retroshare has file-sharing similar to those where you point the client at a folder and it just shares the entire thing.

        IPFS would’ve been great for this, but they honestly screwed the pooch on that (it hogs resources, doesn’t have good clients, and doesn’t have a bridge to torrents or other networks i.e you can’t go “oh, I have a torrent file, let me see if the files for this are on IPFS and download them from there”).

        Anti Commercial-AI license

        • originalucifer@moist.catsweat.comOP
          2·
          1 day ago

          id prolly be happy with it at the series level even, not necessarily the seasons… but one torrent seems like a pain to create… thousands seems arduous. without a lot of scripting that is. i’m checkin out retroshare also, thanks!

          • onlinepersonaEnglish
            9·
            1 day ago

            Hmm, creating torrents isn’t that hard.

            for folder in * ; do
  transmission-create -o "$folder.torrent" "$folder"
done

            You can add a tracker by adding the --tracker "$trackerUrl" option. There isn’t much more scripting involved, AFAIK, unless you want to upload them to the tracker too. But if you join the DHT and share the magnet links somewhere, you should be done. Or is there more to the process I’m missing?

            Anti Commercial-AI license

              • onlinepersonaEnglish
                7·
                1 day ago

                You can use transmission just for creating the torrent. You don’t have to use the actual client. If qbittorrent is your client, it’s possible to add the torrents to the list at the same time with

                for folder in * ; do
  transmission-create -o "$folder.torrent" "$folder"
  qbittorrent --save-path="$folder" "$folder.torrent"
done

                Then you create the torrent and start seeding it immediately. If you’ve already created the torrent files

                for torrentFile in **/*.torrent ; do
  folderName="$(basename -s .torrent "$torrentFile")"
  folderParent="$(dirname "$torrentFile")"
  folderPath="$folderName/$folderParent"
  qbittorent --save-path="$folderPath" "$torrentFile"
done

                Depending on the setup, you could also just sym link the folder into qbittorrent’s download directory and copy your torrents into a folder that qbittorrent listens to. There are many ways to skin the cat. Check out the command line parameters for your torrent client.

                Anti Commercial-AI license

  • Xanza@lemm.eeEnglish
    11·
    2 days ago
    1. Create Torrent
    2. Upload torrent to torrent cache website
    3. Torrent eventually propagates to DHT network