Michael Goodnow

I definitely appreciate someone else other than me saying that this feature area is out of scope for cross-seed, I totally agree! 😅 @SweetMNM are you the tqm dev? What...

would `action: "save"` be enough in this case then? I just feel like this is something that would be better handled downstream entirely - if we're going to implement this...

> it should never skip recheck on purpose to avoid facing the issue I disagree - in the other clients this is really the best option. - New torrent thinks...

Take a look at https://github.com/transmission/transmission/pull/2626: > This PR lets newly-added torrents skip the full verify step if the torrent fulfills _all_ these conditions: > > * The torrent has metadata...

> I would assume it's the last bullet point that fails and triggers the verification Is this something you can verify with a diff of your files that have this...

I think there might be a way to support this. I definitely like the idea of solution 3, but we also already have a flag that represents rechecking and adding...

I personally am not a fan of solution 1 after thinking it over - the configuration definitely belongs on cross-seed's side, not Transmission's side.

this really feels like a daemon-reload issue or something similar. Maybe you have multiple unit files, and you're editing the first one and running the second? I was able to...

looks like I forgot to close this. We did this in February or so

Transmission support has been added in the `next` branch! Use `-A inject --transmission-rpc-url http://user:pass@host:port/transmission/rpc` on the command line, or you can use `action: "inject", transmissionRpcUrl: "http://user:pass@host:port/transmission/rpc"` in the config file....