discuss I2P

For those who like me have trouble with the automatic start of torrents in I2PSnark (integrated into the router or standalone), I used to place in the webapps folder, the famous transmission.war (https://github.com/i2p/i2p.plugins.i2psnark-rpc)

After restarting I2PSnark, I install transmission-remote (depending on your system you have to install the package that contains transmission-remote, I think it's the transmission-cli package) and i run the command "transmission-remote 127.0.0.1:8002 --torrent all --start" every 30 minutes with a scheduled task

And I don't have to worry about starting torrents anymore

yup turns out doing this with standalone is easy, this is a good solution. eventually i'll change tuckit to do it this way instead of through webscrape and just keep scrape for changing settings

would be cool to have a way to stop seeding specific torrents this way - like have a master instance for peer counts and each of the slave instances stop that torrent as seeds come online

If you run "transmission-remote 127.0.0.1:8002 --list" you get the list of torrents.
You can then pipe the command and sort the name of the torrent to find its ID (with awk, grep, what you prefer)

When you know the ID, a simple "transmission-remote x.x.x.x:8002 -t TORRENT_ID --stop" stops the torrent

I consult the clearnet link https://commandmasters.com/commands/tra ... te-common/ to remember the main commands, but there are many other useful links on the web

what i'm thinking since i didn't word it very well is to get seed counts on all torrents from a master instance on snark periodically, and send the commands to the slave instances if seeds go over/under a threshold for each torrent

basically pump up a new swarm quickly and cut down my seeds when it can stand on its own. i end up doing this manually sometimes, more now than before since switching to 32 outbound tunnels and less snark instances. or some other slightly more complex logic like starting to cut down instances as peers get in the 80-90% range so if they want to complete they must stay.

any case it's a lot easier to do this kind of stuff with transmission lol

As zzz says, transmission.war is currently a basic RPC implementation, but I think the currently implemented options are sufficient to do what you want to achieve, and just with a script. I'll look at the different possibilities on my side and I'll make you a comeback

The full list of options is here, if needed:
/!\ clearnet link
https://manpages.debian.org/testing/tra ... .1.en.html

Yup. Instructions at http://zzz.i2p/topics/3688 and in the standalone readme.txt.

If you find some RPC call that's unimplemented or partially implemented that you'd like fixed up, please ask.

It makes me think that I may be the only one using this module every day since its publication, so I would like to thank you personally for making it available. The current features are sufficient for what I do, but other users may be more demanding in terms of possibilities. IMHO, leaving this war file as an independent module that is added "if needed" is for the moment a good idea.