Michael Goodnow

You might even be able to shorten it to `ExecStart=/usr/bin/cross-seed daemon` but only if systemd can find where node is. Otherwise, the other way is perfectly fine.

would it be crazy to automatically create a category that's just "$CURRENTCATEGORY".cross-seed that's a duplicate of $CURRENTCATEGORY except for the name?

I feel like that might solve for the main pain point (sonarr trying to import cross-seeds) with less user effort.

For anyone interested, I just opened #257 which implements the solution I proposed earlier: https://github.com/mmgoodnow/cross-seed/issues/254#issuecomment-1133807963

Feedback is very welcome.

It'll tag it as well, but I recommend not using separate pre-import and post-import categories. There's more discussion in the discord but basically the point of this is so that...

The new automatically generated categories should be able to stay out of Sonarr's way so that you don't run into import problems if you add cross-seeds from qBittorrent on finished...

## Constraints - As long as you're changing categories with different during the lifecycle, cross-seed needs to be triggered by the program which changes the categories. - As long as...

still gonna do cat filtering

I would consider it in the long term; though I'd expect a feature like this to be 2+ years away. I think there would be significant complexity in the configuration...