Whoever designed that seems like they have something against transmission lol.
For me personally: it gets the job done, is allowed by most private trackers, fast and responsive, has a functional webui, and a very vast selection of third party apps (in addition to the cross platform first-party offering)
It's simplicity is kind of its selling point. Only real criticism I have is that it's unfortunate some of the supported features aren't accessible in the first party apps, and especially from the lightweight web interface
Transmission is good precisely because it does one thing and one thing really well - download torrents. No other crap, spam and non-related garbage required.
Transmission is probably one of the best clients to use in a headless setup. I think it usually ranks lower because it doesn't do a lot of things for you. What it does it does well, but nothing beyond that. Technically there is network binding, but by IP address and not interface. That means you have to script it which I know most people aren't going to want to do. As far as searching, again you have to rely on other services that probably do it better anyway. Still I rank it alongside qbittorrent. It just takes a less user or beginner friendly route.
Everyone sleeping on qBittorrent with the search plugin enabled. I never have to go to websites ever again, I can just pull from various domains with one search built into the program.
I think quite a few of us use torrents on a remote server, so the thin app / remote client combo mode that deluge/transmission support puts them ahead of any other for consideration.
Transmission does have network binding. At least, i'm pretty sure it does. At least on Linux. It also has a cli interface and is a "full" client so it should at least be on par with rTorrent in that sense. It's not a great cli interface but it works.
Used qBittorrent for a long time now. No complaints. Ever since I've set up a home server, I almost exclusively use qBittorrent-nox now. Its qBittorrent, but headless! Runs all the time. Just use a web ui to access it. I can even run a reverse proxy and access it from afar!
I'll never understand the FOSS mentality of "There's already a quality project out there with active development and most of the user-share. Perfect, so I'll utilize my off-time to create my own inferior competitor and fragment the users instead of contribute to the existing one".
I mean, I get it if the existing project maintainers start acting with shady interests - the threat of the fork can be a powerful tool. But it seems like many of these alt projects do it right out of the gate. Meanwhile, it took linux desktop how long to get a functional wifi driver out of the box??
I switched from Transmission to qBittorrent a while ago, and I have some regrets: mainly that the qBittorrent web ui is extremely hard to navigate on mobile. Everything is tiny, and I can't zoom in and navigate around the page without right-click menus popping up
I am still using the last (ancient) version of Azureus (Vuze) because it has great plugins. I have the plugin to allow it to use the Mainline DHT, and I use the i2p plugin too (because the default i2p torrent UI is bad). Azureus is (was) the only client that can download/seed a torrent on clearnet and i2p at the same time.
Having said that, I didn't know that BiglyBT has i2p support, so I need to check that out.
Good list. Honestly, if it doesn't have network interface binding it's not a even an option for me. It's so important to keep your IP from leaking, it should be a priority feature.
Is there a docker container for BiglyBT that handles java and has a webUI, similar to qBittorrent? And can it integrate with the *arrs in the same way?
I want to use qbittorrent, but my Mac won't let me install it - says it's too old for the operating system and/or that it can't be verified.
I've just installed bigly bt, and I have three questions: 1) is it possible to set the seeding ratio 2) do we really need to confirm the deletion of every torrent via the pop up? (I have RSI, and the less popups or clicking the better) and 3) why does searching for a torrent via the internal search engine result in a captula.?
Does anyone have recommendations on configuration for qbit? I'm a casual user and I have been using out of the box for years now, but I've been wondering how it could be improved.
It's completely overkill for pretty much everyone but I have been thinking about building a kubernetes native client for months now.
Like the torrent should be treated as a normal resource with a Torrent CRD. It should be scheduled onto whichever node has available capacity and rescheduled onto a different node if it goes down. If allowed by the tracker, multiple instances could be run. You could set resource limits programmatically, easily configure block storage, build dashboards, export logs/metrics.. It would be open ended enough that you could have interfaces built as browser extensions, web ui, mobile app, tui, cli and be unopinionated so much that the method for torrent ingestions could be left up to the used. HTTP request, watch directory, rss client, download manager.. You could even do stuff like throw magnet links into a queue.. etc, etc..
I keep thinking it would be a great project but I just do not have the spare time to dedicate to it.. I imagine it could be used for large scale deployments for something like the Internet archive or whatever.
I really like biglybt, but why is it so... slow to add torrents or shut itself down? It seems as if the app does so many different things simultaneously that it doesn't do them seamlessly or instantaneously. I mean, why does it need 'up to twenty seconds' to close after you've downloaded something? Is it bloat? Is there a way to streamline its running?
Can someone help me with qbittorrent? After a couple of days of running the docker container all my torrents get stalled until I restart the container.
I am interested in some of the features of BiglyBT, but don't love the .sh installer for Linux - they should have rpms and debs IMO. I'm a little concerned they don't end up in EPEL or whatever like qbittorrent is.
I have some custom scripts which kinda do what the *arr apps do.
I download torrent files into a folder. My script picks it up, identifies whether it is movie, TV, music, Games, ebooks, or something else. Based on this it selects the right folder. Then calls Transmission API and adds the torrent with the relevant path.
In case of movies and TV shows, it then calls the transmission APIs to rename the files properly. This way I can have my folders well organised and continue seeding without the need of creating duplicates.
This setup works quite well. The only fear I have is the transmission remote GUI for Windows hasn't been updated in 4 years. It works quite well, but it's only a matter of time before it stops working.
I'm not in any private trackers so it doesn't really matter, but why is tixati banned? I use it because it's the only client that worked on the crusty old computer I use to run my torrents. Is it evil or something?
I've tried most of these clients, but I keep going back to the old uTorrent 2.2.1 (the newer versions are indisputably awful). I find that it still has the best UX to date. On nix machines I use qB.
Edit: Warning: newer versions of uTorrent are malware. I recommend people pick a different client, as uTorrent actively tries to trick people into downloading the newer versions.
I don't understand why everyone shits on uTorrent. Maybe new versions are bloated with miners and ads, but for example on Rutracker a custom version of uTorrent 3.2.3 is the most popular one and i've been using it for like 3 years without any problems. The only downside of it is that it has no dark mode, but that's it.
When i tried using qBitTorrent i couldn't set it up to use 100% of my traffic, it was very abrupt. So i just stick to uTorrent. Am i missing out on something?