it’s qbittorrent, not gbittorrent. that’s really why.
transmission has been the default on so many gnome-based distributions for a very long time because of its gtk frontend… it also has a qt frontend, curses cli, daemon, windows qt build, and native mac versions…
qbittorrent also runs on more than just linux, but is qt. only qt. how many qt-only applications find their way into the default package set for gnome or gtk desktops released by debian, ubuntu, mint, fedora, redhat, suse, etc, etc.
Yeah, I much prefer cli front ends over web ones as all my torrent boxes have been headless. I realize with most client server archs I could connect via gui but still I prefer cli.
It does what it used to do 15 years ago and it does it well. The arr-stack tried to make me use qBittorrent. I said no and did it with Transmission anyway.
Bonkers that its the default on many distros instead of qbittorrent
it’s qbittorrent, not gbittorrent. that’s really why.
transmission has been the default on so many gnome-based distributions for a very long time because of its gtk frontend… it also has a qt frontend, curses cli, daemon, windows qt build, and native mac versions…
qbittorrent also runs on more than just linux, but is qt. only qt. how many qt-only applications find their way into the default package set for gnome or gtk desktops released by debian, ubuntu, mint, fedora, redhat, suse, etc, etc.
Yeah, I much prefer cli front ends over web ones as all my torrent boxes have been headless. I realize with most client server archs I could connect via gui but still I prefer cli.
It does what it used to do 15 years ago and it does it well. The arr-stack tried to make me use qBittorrent. I said no and did it with Transmission anyway.
Qbt likewise has been doing it for 20 years and doing it well 🤷
Works great in my friends arr stack