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
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.
I’ve had email communication with the devs and again, I’m a biased donor. They are just starting afloat on donations. Respect your closed source concerns completely, but it’s a superior piece of software imo and I see no signs of malificence. If you are an open source purist I get it, there are other options. If you are using any closed source software at all though, it would seem to me hypocritical to show a bias against this particular app.
I don’t use that client either - But to be fair the dev (Kevin Hearn) has a long history with P2P software e.g. depending how old you are you may have used his WinMX software back in the day. He isn’t known for sticking spyware/malware into his software so I sort of trust the software he puts out in that sense. He also maintains other non-torrent P2P file sharing software outside of Tixati.
Of course it would be better if it was open source but he’s never been an open source coder AFAIK.
Deluge always seems so underrepresented, but as far as I know it’s never had a version compromised with malware like some of the other popular clients. It also performs great when you are seeding over 1000 torrents as long as you upgrade to version two.
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 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 .
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?
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.
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.
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?
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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.
I keep recommending Tribler and I don’t know why it’s not more popular. Anything wrong with it?
I appreciate the ability for the tor-like layered routing with tribler. Getting the headless UI set up is annoying, though.
The most recent release is headless and only has a web front end.
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’ve had email communication with the devs and again, I’m a biased donor. They are just starting afloat on donations. Respect your closed source concerns completely, but it’s a superior piece of software imo and I see no signs of malificence. If you are an open source purist I get it, there are other options. If you are using any closed source software at all though, it would seem to me hypocritical to show a bias against this particular app.
I don’t use that client either - But to be fair the dev (Kevin Hearn) has a long history with P2P software e.g. depending how old you are you may have used his WinMX software back in the day. He isn’t known for sticking spyware/malware into his software so I sort of trust the software he puts out in that sense. He also maintains other non-torrent P2P file sharing software outside of Tixati.
Of course it would be better if it was open source but he’s never been an open source coder AFAIK.
Deluge is always my goto.
Deluge always seems so underrepresented, but as far as I know it’s never had a version compromised with malware like some of the other popular clients. It also performs great when you are seeding over 1000 torrents as long as you upgrade to version two.
Better to use the underrepresented torrent clients. They have the least chance of enshittification.
looks at µTorrent
qBittorrent and rtorrent are very popular.
I hear people use the search function of QBitTorrent tied to VPN tunnel. Basic, but it works
If you add jackett and set it up it will search all of your indexers at once.
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.
deleted by creator
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 .
There’s also qBitControl for iOS btw. But you have to sideload it using AltStore (which is pretty easy if you’re in the EU).
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
Not at all! Using the one provided by LinuxServer.io, found here
Deluge on desktop, Flud on mobile. 😃
Flud looks proprietary and has ads.
Libretorrent works just as well and is open source.
qBittorrent. With a quick UI switch to vuetorrent for the tablet. LXC bound to a bridge thats VPN connected.
The is the way
transmission
Fragments
qBittorrent here.
+1 for qBittorrent. I used to be a Deluge fan, but qBittorrent seems more performant and feature-packed.
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.
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.
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.
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.
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.
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.
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.