I’m spinning up a new seedbox and wanted to know what is everyone using nowadays? I was using deluge via the thick client and rutorrent previously. Are they still king? edit: I should have also mentioned that I plan on running this server headless so I will need to be able to access it via a thin client or a web browser
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
QBITTORRENT
+1 qbittorrent
At least there’s one thing these Lemmy people agree with me on.
I use biglybt, i know the ui isn’t great but the features make up for it
I’ve been using Transmission for many years.
iblocklist and transmission name a better team
Deluge
I’m currently using Transmission again
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.
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.
qbittorrent on PC and libretorrent on Android.
Glad to see I’m not the only one who torrents on mobile
I usually do smaller things when on mobile, both due to Storage and Data Usage considerations. For bigger stuff I mainly use my PC and qbittorrent.
qbit on pc, flud on android
qBittorent for Windows and LibreTorrent for Android.
I use almost the same setup, except I don’t use Windows on Desktop.
Qbittorrent, Transmission and Ktorrent the Last two When some updates breaks Qbittorrent
qBittorrent here.
+1 for qBittorrent. I used to be a Deluge fan, but qBittorrent seems more performant and feature-packed.
Still qbittorrent. Docker container with web UI makes it trivial.
With Vuetorrent for a nice mobile ui
Did you try qBitController?
I was not aware of that. Thanks for sharing. I’ll probably stick to my current setup for now as its one app less on the phone and I access the rest of my services through the browser anyway .
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.
Do you use altstore? Have you tried livecontainer to avoid the 3 app limit?
I don’t think that applies when using the EU version and Apple’s new sideloading framework. But I don’t know, since I only have 1 app sideloaded right now.
