view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
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