Live data from Hacker News

Transmission 4.0.0 beta 1

github.com

231–240 of 262 posts

Re: Transmission 4.0.0 beta 1

#231

Earlier quoted context omitted.

Please, don't call copyright infringement 'piracy'. Piracy is a penal crime that involves violence, theft of property and is often accompanied by murders. Torrenting is just copying data.

we had literal pirate parties as fairly legitimate political actors, I think the term has long been reappropriated

You should probably learn the difference between 'literally' and 'figuratively'.

Literal pirate parties exist in Somali and prey on nearby shipping lanes.

Re: Transmission 4.0.0 beta 1

#232
post #144

Good to see it being in active development. But the one feature I'm waiting for is a network whitelist. For example, it should never connect over my home or office network, but only via anonymous VPN. (Edit: I know you can do this already with firewall rules, or containers, but I don't trust myself to not make a mistake. Ideally this should be part of the OS. You should be able to right-click somewhere in the window…

Under Linux you can run transmission as another user and have an iptables rule to only allow outbound traffic through a specific interface.

Or just uidrange based policy for a separate routing table that just routes to the VPN. Just one thing to set up.

Re: Transmission 4.0.0 beta 1

#233
Is it still single-threaded and the UI chokes when doing a blocking operation like moving a large torrent to a different hard drive? I didn't find any mention of parallel/threads/concurrent in the release notes.

I've been torrenting since the early 2000s and using torrent clients on Mac and Linux for over ten years, and there have been various issues in both Transmission and qBittorrent for as long as I can remember. I'm not sure if rTorrent is better, but lots of people seem to like it.

QBT has a tendency to break on upgrades and then it tries to rename files and do re-checks and all sorts of messy stuff - maybe due to my configuration since I have "append !qB" to incomplete files - but I personally don't think a client should ever rename a file from 'video.mp4' -> 'video.mp4.!qB' unless the checking is complete and it has already determined the file needs to be partially re-downloaded. Also, checking torrents is basically a broken feature since v4.4 - according to a bunch of people on the internet. I'm on the latest version, but going back to a working version could be a nightmare with hundreds of torrents on multiple hard-drives.

I used to use Transmission exclusively but pretty much stopped using it because of the single-threaded limitation. Also, Transmission on linux didn't support categories or labels like the Mac GUI version did, which I required for organization.

I'm not sure how much goes into a Torrent client, though I did read [madreyels]https://mandreyel.github.io/posts/rust-bittorrent-engine/> post on writing a bittorrent engine in Rust. I'm not saying rust is the answer, but I would welcome a new and improved bittorrent client meeting my requirements in any language if it works better than the existing options.

Re: Transmission 4.0.0 beta 1

#234
post #144

Good to see it being in active development. But the one feature I'm waiting for is a network whitelist. For example, it should never connect over my home or office network, but only via anonymous VPN. (Edit: I know you can do this already with firewall rules, or containers, but I don't trust myself to not make a mistake. Ideally this should be part of the OS. You should be able to right-click somewhere in the window…

Under Linux you can run transmission as another user and have an iptables rule to only allow outbound traffic through a specific interface.

you don't even need the extra user: use a network namespace.

- ip netns add vpnonly # create an empty namespace

- ip netns exec vpnonly wg quick ... # connect to your VPN

later, launch transmission inside this namespace:

- ip netns exec vpnonly transmission

has the nice property that as long as you do that exec step right (or even half right), the failure mode is no connectivity rather than accidentally sending traffic in the clear.

Re: Transmission 4.0.0 beta 1

#235

Good to see it being in active development. But the one feature I'm waiting for is a network whitelist. For example, it should never connect over my home or office network, but only via anonymous VPN. (Edit: I know you can do this already with firewall rules, or containers, but I don't trust myself to not make a mistake. Ideally this should be part of the OS. You should be able to right-click somewhere in the window…

I have to agree with them, it’s antithetical to what torrent is about.

Superseeding (and whatever you would call it from the client point of view) allows for peer-to-peer broadcasting.

Re: Transmission 4.0.0 beta 1

#236

When I first came to Linux I adopted Transmission. It seemed less featureful than others but now I like its simplicity, does everything it needs and it is also very reliable. It is not very known but there actually is a transmission-cli for common torrent operations that may come in handy some time.

FYI, transmission-cli is considered deprecated by the Transmission developers. Using both transmission-daemon and transmission-remote is the recommended approach. Actually, transmission-cli uses transmission-daemon internally and they share the same configuration. transmission-cli is still useful for one-off downloads, but I still prefer the recommended way because I'd like to seed older torrents some more time.

I'm not a user of transmission-cli in general, but transmission-create (part of transmission-cli) is indispensable for me.

Re: Transmission 4.0.0 beta 1

#237
post #53

Earlier quoted context omitted.

There's also the Transmission Remote GUI, which is a nice GUI for remotely controlling the Transmission daemon, on say, a NAS: https://github.com/transmission-remote-gui/transgui It's great for keeping downloads going overnight without having to leave all the power-hungry devices powered on.

FWIW, qbittorrent also has a built-in web interface. It's also one of the most feature-rich BitTorrent clients. https://github.com/qbittorrent/qBittorrent

And you can install it with just the web interface as qbittorrent-nox.

Re: Transmission 4.0.0 beta 1

#238
post #223

Earlier quoted context omitted.

Simply seeding for the 1+ hour you are watching the movie is typically enough to keep a torrent swarm healthy now that the majority of users have 10 Mbps+upload speeds. In that time, you can easily upload more data than you downloaded, meaning you are a net benefit for the swarm. In a general sense, any video content where the bitrate is lower than the typical users upload bitrate could work for a webtorrent only swa…

Even if you seed for a very short time is speeds up the process. No need to consume their data.

Only if they seed more than they leech. It has little to do with time. If you take a year to seed more than you leeched, you're a positive contribution to the swarm.

Re: Transmission 4.0.0 beta 1

#239

Earlier quoted context omitted.

Streaming services are increasingly going over cable TV route and screwing customers over. The age of piracy is back.

Please, don't call copyright infringement 'piracy'. Piracy is a penal crime that involves violence, theft of property and is often accompanied by murders. Torrenting is just copying data.

Koptimism is the practice of the religion of Kopimi.

Re: Transmission 4.0.0 beta 1

#240

Earlier quoted context omitted.

we had literal pirate parties as fairly legitimate political actors, I think the term has long been reappropriated

You should probably learn the difference between 'literally' and 'figuratively'. Literal pirate parties exist in Somali and prey on nearby shipping lanes.

If your political party documents and registration are under the name "The Pirate Party," you're quite literally the pirate party.
Post reply on HN