qBittorrent here.
this post was submitted on 21 Jan 2025
26 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
55872 readers
411 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
+1 for qBittorrent. I used to be a Deluge fan, but qBittorrent seems more performant and feature-packed.
qBittorrent and rtorrent are very popular.
QBITTORRENT
+1 qbittorrent
I like that they were using ALL CAPS and you're using all lowercase.
qBittorrent
At least there's one thing these Lemmy people agree with me on.
Deluge is always my goto.
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.
Transmission is my favorite design-wise on macOS but I wish it had i2p support.
I never even realized that Transmission doesn't support it. I just have I2P set up on my seedbox (but it typically requires root access, so unfortunately not everyone can replicate this). I would imagine it's pretty flaky on macOS though? I'm pretty sure the vast majority of I2P users run Linux, so the macOS client probably doesn't get as much development and attention.
I don’t know why i2p would be flaky on macOS. I run i2pd (hate Java) on Linux and macOS and it’s functionally the same.
I don’t know why i2p would be flaky on macOS.
That was just my assumption, because the modern macOS network stack is not exactly similar to Linux, so some changes would be required, and since it's not that widely used (at least in the I2P community) it wouldn't get tested and developed that much. But again, that was just my assumption.
I run i2pd (hate Java)
As a former Java dev: Completely understandable. i2pd is the only I2P implementation I will ever touch, the Java client is just a buggy mess with bad performance.
A lot of the macOS networking stack (at a lower level) comes from FreeBSD. People have argued that the BSD network stack is superior to Linux whereas Linux runs applications faster. At a low level, I think this is still accurate.
I’m a Ruby developer but I tried to port a Linux application written in C to macOS before and it was mostly rearranging positional arguments to system API calls; however there’s probably a lot more going on that I’m not aware of too.
A lot of the macOS networking stack (at a lower level) comes from FreeBSD.
Yeah, but they added a bunch of high-level abstractions on top over the years. Nowadays it's much closer to the way you do networking on mobile operating systems like iOS and Android.
I’m a Ruby developer but I tried to port a Linux application written in C to macOS before and it was mostly rearranging positional arguments to system API calls
But I imagine the Ruby standard library also takes away a lot of the complexity, right?
That’s right, but I was talking about a C project.
Oh sorry, I misread that
qBittorrent. With a quick UI switch to vuetorrent for the tablet. LXC bound to a bridge thats VPN connected.
arch-qbittorrentvpn docker container, because it was the easiest to set up on my TrueNAS home server.
Qbittorrent via a container and web UI on my NAS, lets me use it as a backend for *arrs as well as anything else, just have tag based directories for it so Software goes into one folder and TV movies etc in their respective folders.
I personally like the setup a lot since I can always be a seeder even well after my ratio is hit.
slskd hooked up to this as well to share everything music wise, gives me a nice way to reconcile stuff Lidarr can't find and shares it all back for anyone to browse so hopefully helps someone downloadv something they're searching for a FLAC of
nzb360 on Android for management as needed, it hooks into Qbittorrent easily and gives me a nice place to do some quicker tasks for my overall infra
I'm a much bigger fan of the deluge thin client, personally.
This is what I used in the past but I had issues with the Deluge thin client when using a Deluge docker image. Did you experience the same thing as well?
Nope! My deluge server is hosted in a docker network with gluetun, and I access it from both thin clients and the web interface.
Mind me asking which docker image you are using? I was never able to get the thin client to work through docker
Deluge on desktop, Flud on mobile. 😃
Flud looks proprietary and has ads.
Libretorrent works just as well and is open source.
I’ve been using Transmission for many years.
I've got Transmission on my NAS and use Transmission-remote(Linux and android) for the client. Simple, easy to setup and it just works.
iblocklist and transmission name a better team
Tixati
Not sure why it's not more popular. I use and donate. I've had better performance with this than qbittorrent.
Closed source, and their prominent "contains NO Spyware" disclaimer doesn't quite instill confidence. I have also never even heard about it until now.
I use biglybt, i know the ui isn't great but the features make up for it
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.
Fragments
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.
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.
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.
Deluge
Good ol' rtorrent never dissapoints. For when I want something with a webui, I have a qflood container that I extracted from its old *arr setup to more generalistic usage.
qBittorent for Windows and LibreTorrent for Android.
I use almost the same setup, except I don't use Windows on Desktop.
I hear people use the search function of QBitTorrent tied to VPN tunnel. Basic, but it works
qbittorrent on PC and libretorrent on Android.