Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

BiglyBT for manual dls on desktop, qBittorrent with the arrs

Deluge

QBITTORRENT

qbittorrent on PC and libretorrent on Android.

I’m currently using Transmission again

qbit on pc, flud on android

Random semi-related thought. I'm going through the comparison of BitTorrent clients page on Wikipedia and it's amazing how many clients end up as Adware.

qBittorent for Windows and LibreTorrent for Android.

Qbittorrent, Transmission and Ktorrent the Last two When some updates breaks Qbittorrent

I keep recommending Tribler and I don't know why it's not more popular. Anything wrong with it?

qBittorrent here.

Still qbittorrent. Docker container with web UI makes it trivial.

transmission in docker container on NAS, with dedicated IP that gets forced through VPN on my router

qBittorrent is probably the most commonly used client. Transmission is another popular option, especially among macOS users, since it has a familiar design and feels more native.

rTorrent is great if you want a CLI app, and ruTorrent offers a web frontend. Another option that you can run on a server is Deluge.

You can control qBittorrent from Android using qBitController or from iOS using qBitControl (you can get it from AltStore after adding the Michael-128 repo). Transdroid supports other clients as well, and it's my personal favorite. If you want to torrent on the Android device itself, check out LibreTorrent. For iOS, use iTorrent (also available on AltStore).

If you already plan on self-hosting, or have root access on your seed box (or some other way of installing applications/deploying Docker containers), I also recommend setting up bitmagnet. It's basically your own torrent indexer and search engine. It can also integrate with your *arr applications.

qBittorrent and rtorrent are very popular.

arch-qbittorrentvpn docker container, because it was the easiest to set up on my TrueNAS home server.

I've had a poor experience with Deluge, a bug report completely disregarded years ago as I wasn't able to provide (very technical) details to the developers without some assistance, which they smugly refused to provide (I don't act entitled). I then stumbled upon a post where one of them discussed the reason why they wouldn't add workarounds in the installer as qBittorrent did (firewall exception and a couple of other things I can't recall right now), their reasoning and their wording struck me as strongly ideological, and it made me uneasy. I've had a similar experience with Affinity developers who (again, by way of ideology) refused to add an "interface scale" parameter to their programs, adamant on letting the OS handle the scaling, even though I couldn't change my OS scale because it messed up other programs. Their response was "it's the other program's fault". Very helpful. 👍🏼

Anyway, I was trying to say I don't like Deluge. To answer your question I know it runs via a variety of interfaces so I wouldn't be surprised it's your best bet. I personally use qBittorrent .

Deluge is always my goto.

qBittorrent. With a quick UI switch to vuetorrent for the tablet. LXC bound to a bridge thats VPN connected.

On a headless seedbox Deluge/ruTorrent/Transmission are still reliable, most of the paid seedbox services still default with those.

qBittorrent is hugely popular on the desktop front and has been getting more popular as a headless client now that the web ui has improved, also look into qbittorrent-nox if you don't have a gui to do initial setup with.

Tixati

transmission

I used transmission for years, but the larger my library got the more issues I had. Currently using Qbit and loving the categories for easier management, especially with the *arr suite.

I'm a much bigger fan of the deluge thin client, personally.

I hear people use the search function of QBitTorrent tied to VPN tunnel. Basic, but it works

rTorrent with Flood front end.

My only complaint so far is being unable to reach the rTorrent TUI when it's running headless. It otherwise works great.

Fragments