Live data from Hacker News

Transmission 4.0.0 beta 1

github.com

141–150 of 262 posts

Re: Transmission 4.0.0 beta 1

#141
post #14

Earlier quoted context omitted.

I think Transmission works great. What's the v2 killer feature?

The protocol should be able to find same files in other torrents - you could be downloading a bunch of files (like a season of TV), but are able to find and download one file from another torrent that is better seeded (like one single episode torrent). But I don't think any of the clients implement that yet.

That's great!

I suppose they removed bittorrent's weirdness of allowing chunks to overlap multiple files. That was the original sin that caused all this

Re: Transmission 4.0.0 beta 1

#143
post #91

I'm really excited to see support for torrents v2. If only because transmission will stop chocking on hybrid torrent files, which should lead to more adoption across the board. I wish transmission supported mutable torrents (BEP46). It would allow completely re-thinking distribution: grab a torrent of your favorite distribution, and have it auto-update to the latest version. Or grab a "super-torrent" that lists isos…

> I wish transmission supported mutable torrents (BEP46). It would allow completely re-thinking distribution: grab a torrent of your favorite distribution, and have it auto-update to the latest version. That sounds horrible. My own expectation is that if I have a torrent file/magnet link and I download from it, I always get the same content. This is why I commonly keep the magnet link/torrent file around even if I de…

It doesn't unless your magnet does not contain an infohash and only contains the btpk.

Re: Transmission 4.0.0 beta 1

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

Re: Transmission 4.0.0 beta 1

#146

As a Chinese, I really need the anti leeching capabilities, as too many people here use Xunlei that only download but never upload. Sad to see that the maintainers skip this again.

In my country, noone will bother you if you download pirated content but they will bother you if you seed it.

Switzerland.

The birthplace of BitThief.

https://github.com/pmoor/bitthief

Re: Transmission 4.0.0 beta 1

#147
post #67

Love Transmission but went to picotorrent a few years ago, even smaller footprint https://github.com/picotorrent/picotorrent Sadly it’s Windows only

I stopped using clients on my computer as my NAS has a built in client that allows me to quickly download content straight to that device without using my computer as a middleman. Transmission was my go to for a very long time though!

NAS bittorrent clients are often based on transmission. For example, Synology's is.

Re: Transmission 4.0.0 beta 1

#148

Earlier quoted context omitted.

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

Depends on what torrent is about. For me, it is about watching shows that you can't officially watch where I live yet. Once I week, I hit up a site and, click a magnet link, and a couple of minutes later I can watch my favorite show. (The cost of the VPN is incidentally about the same as a streaming subscription. I think for this reason it is tolerated by the powers that be.) I don't expect torrents to be available f…

>(The cost of the VPN is incidentally about the same as a streaming subscription. I think for this reason it is tolerated by the powers that be.)

I really don't follow you there

Re: Transmission 4.0.0 beta 1

#150

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…

If you don’t trust yourself to not make a mistake with firewall config, why do you trust yourself not to make one when setting up an allow list? One wrong digit or dot and you’ll be in the same place.

Start with a default policy of deny and work from there, if you’re only creating rules for allowing traffic explicitly then there’s less possibility for error.

Post reply on HN