Feature Request - Smart Ratio Management

[informationinsecurity]

This is going to sound a bit confusing at first, but bear with me:

In addition to the current workflow for downloading files, implement the following -

On each indexer, create a new setting which specifies if an indexer should be used for downloading AND seeding, or just seeding.

Once that's done, the normal download workflow continues - (item picked, downloaded, etc.)

Once the file is downloaded /completed, search each indexer that is marked as "seed only" for the exact file that has already been downloaded. If it exists, download it at add it to transmission.

Transmission should then see the file already exists, add the second torrent, but should automatically verify local data and begin seeding.

This allows a user to not just download a file, but to auto seed it on other trackers where they might be worried about ratio.

[codsane]

What you're describing is often referred to as "cross-seeding".

I too have been interested in an automatic solution for this, and even considered implementing this into Radarr/Sonarr until I realized they were C#.

I'm going to be taking a deeper look at nefarious over the next couple of days, if we find that this is something lardbit may not have time for I'll take a look into it as I'd love to contribute in any way possible.

[lardbit]

Sorry for the delayed response. I wasn't getting notifications when issues were created. I welcome contributions so let me know how I can help get you up and running with the guts of nefarious. I suppose adding any development instructions in the README would be a good start...

[lardbit]

I added some initial development instructions. Let me know how it goes!

[lardbit]

I delved into this a while ago and there isn't a trivial solution with the current jackett/transmission workflow.

You need unique torrent hashes for transmission to seed the same torrent simultaneously. Private indexers with the same torrent will have a unique hash for each torrent. However, what makes this difficult is that jackett doesn't always include the torrent hash in the results so you'd have to guess if/when a search result is the same as the one you already downloaded purely by the name of the torrent. Then, once added to transmission, you'd retrieve the hash and then have to compare the actual file hash to know if it's truly identical to be able to cross seed.

It's a tricky one involving extra engineering I don't plan on doing anytime soon.

[rogerleecormier]

I haven't used Transmission, but I do know that qbittorrent handles this option perfectly fine, as I often cross-seed new EVO releases between private trackers to get my ratio up on them all. I am sure some private sites may repackage/rehash some torrents, but I regularly use 10ish private trackers for zero-day/general, and I can cross-seed maybe 95% of my downloads, which usually I get from one of the sites.

BTW, I am a heavy user of radarr/sonarr, but I am also actively engaged in learning Python at a fast rate of speed due to work needs, so I think I may be toying with some potential feature addons with the fork I just did. Nefarious is a good, simple application, that has the basic components without all the fluff...but its code-stack is on point, and is exactly what an optimized web app should be using, imo.

[lardbit]

Thanks for the positive feedback. I'm open to any contributions to nefarious so let me know how I can help.