Also, good disk I/O scheduler needed, or you can thrash even stripped NVMe disks, not to mention spinning rust. Good multi threading without any global locks i

Also, good disk I/O scheduler needed, or you can thrash even stripped NVMe disks, not to mention spinning rust. Good multi threading without any global locks is a must or your UI/remote control become unresponsive on big number of active torrents. Also, it needs daemon mode, which can be compiled & installed without any GUI libs (like QT, GTK, Waynald, libx11, anything like this) and fast responsive remote GUI for all platforms which allows to manage thousands of torrents simultaneously (I'm looking at you, <any-existing-torrent-client>). It could be Web UI, but for now I didn't se usable one. Only thing that semi-works is Transmission + Transmission-Remote-GUI written in Pascal. But it is effectively abadonware and works worse and worse with each Transmission update. And be scriptable to allow automate change of torrent on tracker, for example (you need to detect it by "Torrent not registered" tracker-specific error answer and re-download torrent building URL from, for example, "comment" field of torrent, again in tracker-specific way).