transmission VS flood

Very nice feature that one. Its RPC allows for other interfaces for control, it's great.

It'll shrink if you only use it for programming, but if you start using it for file management, email, NNTP, music, torrenting, etc, then individual sections might shrink as your understanding grows and you refine them, but more will be added as new use-cases are covered.

For eshell and other commands yeah that works but that's the usual fallback, not a first-class Emacs UI like transmission.el (which doesn't require super-user shenanigans since its RPC supports authentication and can be reverse-forwarded with SSH).

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

https://flood.js.org/ ?

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood

Finally NPM exposes flood (with authelia auth) at http://flood:3001

Have you tried flood? Lacks a few features, but overall very pleased with it as a frontend on my phone.

If you're ok with using a webUI, then throw Flood onto whatever your favourite client is - https://flood.js.org/

Easiest thing to try would be qbittorrent-nox with either the web UI or a different web UI like Flood

I'm not very experienced with unraid yet. How would I go about making a Container for Flood UI? (https://flood.js.org/). I know how to use and connect it to, but can't find a way to install it on unraid.S