Headless Mac OS X Support

[nhelke]

I would like there to be a Mac OS X version which one could install as a daemon (perhaps configurable through the Sharing System Preferences pane) with a Clutch web interface. The daemon would use the current authentication directory for all remote connections (RPC, Clutch…). The default behavior would be everyone has access. Optional white lists could limit use to specific users or groups configureable through the web interface by admin users (just like CUPS lets admin users access advanced features through its web interface). My belief is that these white lists are a low priority as I imagine this feature would mostly be used by families with few users all of whom are trusted.

In an ideal world the Transmission application should have a mode in which it can connect a daemon and control it. When in this mode opening a .torrent file locally would prompt Transmission to upload the file to the selected daemon for download.

In this context one can also imagine an iPhone remote control application being written.

[Inuyasha]

It would be helpful if the CLI edition had the option of loading the Mac GUI build's configuration and session info, along with Clutch compatibility.

That's the simplest way to make Transmission fit your needs - you could create an account on your OS X machine for the user, configure Transmission using their account and the Mac Transmission GUI, then run the CLI independent of an actual loginwindow session. You would only need limited terminal skills to do this.

It would make it easier to set up a multi-user system, because you could easily create separate configurations and instances of Mac Transmission on different user accounts.

TorrentFlux WOULD be the perfect solution here but it only supports an extremely dated, branched version of transmissioncli, and runs a separate instance of it for every running torrent. Stupid!

[Jordan]

It would be helpful if the CLI edition had the option of loading the Mac GUI build's configuration and session info, along with Clutch compatibility.

Not going to happen. The GTK+ client uses settings.json, The Qt+ client uses settings.json, the daemon uses settings.json, and transmission-cli uses settings.json... if anything's going to change, IMO the Mac client should adopt the same configuration file format all the other apps are using.