4 ms·
Why not just use qbittorrent? Has RSS, has search in the client, has paths based off categories...
by gfrecvh 2mo ago
Why not just use qbittorrent? Has RSS, has search in the client, has paths based off categories...
- dawidpotocki 2mo agoAs someone that only very recently switched to qBittorrent from Transmission after using it for few years - the lack of non-Web UI remote clients.
- Trung0246 2mo agoYou can probably just use VueTorrent or qBitController android app for headless mode.
- dawidpotocki 2mo agoVueTorrent is a web client. I currently use the official Web UI in an isolated Chromium instance and made an automatic log in page so that I don't have to type in the password every single time I open it. I add torrents to the qBittorrent instance using a Firefox addon. It's all a bit jank. I started some work to make my own qBittorrent client for desktop; I don't care about mobile that much.
- davkan 2mo agodeluge is probably the best for native gui. It doesnt have the amount of integrations as qb and it struggles with many thousands of torrents (or at least it did 10yrs ago), but otherwise a great client. Otherwise there’s qui for qb which, while still a webui, is great.
- sapphyrus 2mo agoI'd recommend checking out qui - still web-based but extremely well made.
- nottorp 2mo agoI run transmission on a headless box and only open the remote GUI for it once in a while. Can other bittorrent clients do that out of the box?
- franga2000 2mo agoYes, probably most of them
- nottorp 2mo agoNames? :)
- supriyo-biswas 2mo agoqbittorrent has one, https://wiki.archlinux.org/title/QBittorrent https://wiki.archlinux.org/title/QBittorrent (search “web interface”)
- franga2000 2mo agoDeluge, QBittorrent, rTorrent, uTorrent have web UIs. Deluge also has a remote mode in the desktop app.
- nottorp 2mo agoWell when you say "web UIs" i think of another tab that will expand to 4+ G ram if left open long term...
- BoingBoomTschak 2mo agolibtorrent-rasterbar has (had?) a lot of problems stemming from its complex C++ codebase and Boost dependency. The painful and protracted v1 -> v2 migration was the main visible consequence. No proper client/daemon (thus core/GUI, code is Qt-ware) separation with a clean transmission-like RPC.