Hacker News new | ask | show | jobs
by RektBoy 1356 days ago
Why use this, when there's qBittorent?
6 comments

Why wear a blue shirt, when there's yellow shirts available?
So no functional differences?
I would say Transmission has simpler UI. Outside of UI, it's also packaged differently, compared to Qbittorrent, Transmission can be installed completely headlessly without dependencies to QT/GTK+X.

In terms of actual features, Transmission is more lightweight. It doesn't support super-seeding, broadcatching, native SOCKS support and doesn't have built-in search engine integration.

"qbittorrent-nox" is the name of the headless package.
It only provides a web ui which is inferior to the standalone ui version.

If you want to go that route you might as well use Deluge, which is built on the same libtorrent library, has a proper daemon-client architecture with fully featured native clients for all major platforms.

> I would say Transmission has simpler UI

This is true but for me this is a disadvantage. qBitTorrent allows to fine-tune a lot of settings. Not as many as Tixati but still.

What settings would the average user find useful beyond adding a blocklist (which Transmission supports)? Genuinely curious as someone who used Transmission back in the day and appreciated the simplicity.
For some people, qBittorrent is unusable on macOS because of this bug: https://github.com/qbittorrent/qBittorrent/issues/14360 Transmission on the other hand works perfectly.
Why use qBittorrent, when there's this?
Does qBittorrent support a web UI with headless access?

That is the reason I use Transmission over anything else.

It does, actually, yes:

https://www.addictivetips.com/ubuntu-linux-tips/set-up-qbitt...

Mentioned on homepage, too:

https://www.qbittorrent.org/

> Remote control through Web user interface, written with AJAX

>> Nearly identical to the regular GUI

Transmission used to handle more simultaneous torrents. Looking at the changelog, seems like 4.0 should handle even more.
qBitorrent UI is fugly.