Transmission has been forked as "ReTransmission" | Hacker News Reader

Transmission has been forked as "ReTransmission"

github.com

Astonished by the volume of issues and PRs for this project, they've really felt "complete" for the years I've been using it.

As a long time transmission user, I've felt exactly the opposite. They have been slowly falling behind other clients. They still don't have torrent v2 support even![1] It took them many years to implement sequential downloading.[2]

1: https://github.com/transmission/transmission/issues/458#issu...

2: https://github.com/transmission/transmission/pull/4795

Same. I never have issues with Transmission and actively avoid other feature-rich clients but I guess I'm not a super user

Transmission was stable with no updates for a long time, and a few years back it started adding in more recent bittorrent features.

First update went ok (IIRC), next one had a feature that few users spotted - a bug caused it to hammer tracker servers with update status requests.

The result of that was that many tracker operators started to ban Transmission - the careful ones banned the specific version number, a good many banned either Transmission or the major base release number (4?)

To this day, recent Transmissions version that do "play nice" with trackers are penalised and get fewer to no peers and seeds from a torrents tracker pool.

I still like Transmission for the tight headless mode and remote control aspects .. but maybe two out of ten torrents stall up and I transfer control to a qBitTorrent instance.

Try a really big torrent (several hundred GB - note that it's common to only download some files from such a torrent). It doesn't work in Transmission. At that point, I switched to qBittorrent, which has some nice extra features, too.

What didn't work for you? This is one of my main uses, getting episodes from only one season, out even just the first couple to see if I like it. Worked since forever for me.

Changing which files are 'active' doesn't always take effect correctly until the client is restarted, which can lead to 'stalled at 0kb/s' downloads from all possible peers even if the torrent is stopped and then started without restarting the full app.

IIRC it failed to download anything.

Why not just use qbittorrent? Has RSS, has search in the client, has paths based off categories...

I 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?

Yes, probably most of them

Names? :)

Deluge, QBittorrent, rTorrent, uTorrent have web UIs. Deluge also has a remote mode in the desktop app.

Well when you say "web UIs" i think of another tab that will expand to 4+ G ram if left open long term...

qbittorrent has one, https://wiki.archlinux.org/title/QBittorrent (search “web interface”)

As someone that only very recently switched to qBittorrent from Transmission after using it for few years - the lack of non-Web UI remote clients.

deluge 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.

I'd recommend checking out qui - still web-based but extremely well made.

You can probably just use VueTorrent or qBitController android app for headless mode.

VueTorrent 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.

libtorrent-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.

As someone following its development closely, Transmission botched its v3 -> v4 transition by underestimating the difficulty of keeping regressions under control when doing a simultaneous C -> C++ rewrite and adding features.

My advice? Continue to use Tr3 via https://github.com/stefantalpalaru/transmission-og with spoofed PeerID and keep an eye open on the other clients.

PS: not convinced by rtorrent's "recent" revival, the general trend in its issue tracker screams "not stable" to me; and still no clean client/daemon, like Qb. I say that as an old rtorrent-pyroscope user that still remembers the horrible config format that made customizing Quake 3's CVARs intuitive.

Reply on news.ycombinator.com