What does HackerNews think of transgui?

🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.

Language: Pascal

#159 in Hacktoberfest
#14 in P2P
That UI may make some sense on mobile where a finger, which is bigger than a mouse pointer, must operate bigger controls comfortably; but on desktop? Nope, old interfaces win over "modern" ones any day. For example, down that page there's a Transmission remote GUI screenshot (I use it as Transmission here is a daemon on my headless XigmaNAS server).

https://github.com/transmission-remote-gui/transgui

What would be wrong with it or anything similar? Every information is just there, no need to swipe left and right to read information that has been either hidden elsewhere or, worse, taken away. The same applies to many "old" clients such as QBittorrent and others.

I understand that design is important, but it should never ever win over functionality.

Related: the Transmission Remote GUI that allows to control the client from elsewhere. I use it with the Transmission client contained in the XigmaNAS NAS software which I run headless.

https://github.com/transmission-remote-gui/transgui

If someone asks me to install a Torrent client on a single machine, my favorite would be QBittorrent, however at home I use XigmaNAS' Transmission client extensively, and operate it from other machines in the LAN using the Transgui interface (also available on Windows and MacOS). This allows me to turn off everything but the NAS, which with all RAID disks spun down and a TDP of 15 Watts makes for some good energy savings.

https://github.com/transmission-remote-gui/transgui

There's also the Transmission Remote GUI, which is a nice GUI for remotely controlling the Transmission daemon, on say, a NAS: https://github.com/transmission-remote-gui/transgui

It's great for keeping downloads going overnight without having to leave all the power-hungry devices powered on.

Support in the browser would require the browser to stay on the whole time, along with the computer. Bittorrent clients are better run on small less power hungry boards (RPi, etc.) or on hardware that is meant to be running 24/7 anyway. For example, I run the Transmission daemon on my XigmaNAS home file server. The NAS is headless, but I can control the daemon through its remote GUI, so as soon as I click on a torrent or magnet link on the browser, it calls the local Transmission GUI which sends the info to the client on the NAS which starts the download freeing the browser and the PC of any further work.

https://xigmanas.com/xnaswp/

https://github.com/transmission-remote-gui/transgui

so instead of native like https://github.com/transmission-remote-gui/transgui

I get "electron" cross-platform, "only available for MacOS"

I think you should "sell" it more...

You mean https://github.com/transmission-remote-gui/transgui or another gui? You should be able to connect remotely, that is pretty much the entire idea behind transmission. A torrent daemon with various UIs that use the API.
Though I use Transmission on my NAS4Free box, which I control remotely through the excellent transgui program (https://github.com/transmission-remote-gui/transgui) I also install qBittorrent to all Windows/Linux users asking for a client for it being very stable and consistent among platforms, the latter very important for newbies, but I see now they're porting Transmission to Windows as well. Good!

I don't consider closed source clients for security reasons, or bloated ones (Vuze etc.) because I'd rather use a spare GB of RAM to make a filesystem more snappy than to load a Java environment that eats alone half the resources of a small server.