Live data from Hacker News

Transmission 4.0.0 beta 1

github.com

131–140 of 262 posts

Re: Transmission 4.0.0 beta 1

#131

After Netflix and others streaming services, I stop using Transmission. What’s the current usage of BitTorrent?

Some TV series aren't available everywhere. As an example, I'm currently watching "Dark", a wonderful 2017 German series (think about a grittier, darker, Stranger Things) that was dubbed in English but still doesn't seem to be available in other parts of Europe. There are also other more legit usages of BitTorrent: I use it often to download Linux install images so that the network load is distributed among users and…

I remember Dark having a pretty large mainstream following as it was getting released. I was under the impression that it was funded by Netflix and as such it would be available everywhere that Netflix is available (and by extension assumed Netflix was available everywhere in Europe).

Where in Europe is it not available on Netflix? Or is it the case of Netflix being unavailable?

> There are also other more legit usages of BitTorrent: I use it often to download Linux install images so that the network load is distributed among users and I do not tax excessively the servers.

Yeah, personally I use it to grab Path of Exile updates. The team release a torrent earlier so that people with bad internet connections can grab it early, it works great.

Re: Transmission 4.0.0 beta 1

#132
post #106
post #105

> The project is much more responsive to bug reports and code submissions than it has been in the past. Cool to see community listed as a feature up there with the tech stuff

If I die I want to be deprecated in the changelog

"He was deprecated doing what he loved... sniffle"

Re: Transmission 4.0.0 beta 1

#133
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…

> This change would break that expectation, for what benefit? This could be implemented as a HTTP call instead

The main benefit is not having to rely on a centralized HTTP server and repository, as well as the associated infrastructure: DNS, TLS, CA, etc. One could host a blog over torrents (more or less what IPFS is doing).

We already have RSS feeds for what you describe (though not supported natively by transmission).

> My own expectation is that if I have a torrent file/magnet link and I download from it, I always get the same content.

That wouldn't change significantly. The mutable torrent content is basically a .torrent that points to whatever the current version is; so just save that instead.

The good thing with mutable torrents (or mutable content in the DHT, as pointed out in another comment) is that instead of the hash (content-addressing) being stored in the DHT, a public key is retrieved. Once you got a torrent ("trust on first use" of sorts), you can verify that the new version is from the same uploader (or at least, one that knows the private key).

I would present it with a new set of checkboxes in the torrent client: "download new versions", then if checked "delete previous version after downloading updated content" and for more granularity "download new files", "download updates to existing files". Of course, for ease of use it would be better to have a historical view. I think the main use-cases would be to archive every intermediate version, or to just grab whatever is latest. There's infinite variations in-between. One thing I would like to stress, and that I didn't point out enough in my original comment is that this goes extremely well with v2 torrents and their de-duplication feature: if the same file exists in multiple versions of the torrent, peers with any version can contribute to the swarm.

It's not as good for deduplication as a rolling hashes could be, but you could host whole distribution repositories with mutable v2 torrents.

Re: Transmission 4.0.0 beta 1

#134
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…

First it needs to support BEP44 "Mutable DHT", which is arguably a much more useful feature than mutable torrents. It is also a much simpler feature. http://www.bittorrent.org/beps/bep_0044.html

I agree that's a dependency, but I am not sure how much more useful it would be comparatively?

Re: Transmission 4.0.0 beta 1

#135

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…

I believe the previous commenter meant that sequential downloads are orthogonal to the design of Bit Torrent.

Re: Transmission 4.0.0 beta 1

#136

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’ve got a home lab with proxmox as the hypervisor. I’m running openwrt (x86) for my household router (in a qemu VM) and I’ve got transmission running in a (lxc) container. When the transmission container boots up, it gets its IP address via DHCP (server in openwrt). I configured dhcp to allocate the same lP address to the container every time. You could also just use a static ipconfig in the container.

Within openwrt, I’ve installed WireGuard and OpenVPN for accessing different vpns.

Finally, again in openwrt, I installed the policy based routing package[1]. This package makes it super easy to route all traffic from the transmission container to the VPN network.

There are probably many ways you could do this, but this setup is great for me!

1: https://docs.openwrt.melmac.net/pbr/

Re: Transmission 4.0.0 beta 1

#137
post #30
post #27

My biggest problem with BT / Transmission is that they dont work well with DNS Ad blocking solution. As the BT client will quickly swamp and use up all available DNS quota for torrents. I am wondering if anyone has a solution to that?

I can't say I've noticed this, and I'm a little surprised DNS gets much use in bittorrent at all, is the client doing rDNS on peers or something?

Probably just resolving tracker IPs.

Re: Transmission 4.0.0 beta 1

#138
post #29

Why use this, when there's qBittorent?

Does qBittorrent support a web UI with headless access? That is the reason I use Transmission over anything else.

It does, actually, yes:

https://www.addictivetips.com/ubuntu-linux-tips/set-up-qbitt...

Mentioned on homepage, too:

https://www.qbittorrent.org/

> Remote control through Web user interface, written with AJAX

>> Nearly identical to the regular GUI

Re: Transmission 4.0.0 beta 1

#139

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.

I quite like embracing the word personally, I suspect it dates back to pirate radio in the 1960s which in parts of Europe actually did come from ships anchored just outside of territorial waters. Another interesting example of people embracing the pirate image was British submarines in WW1. The First Sea Lord of the day saw them as ungentlemanly and called for all German submarine crews to be hanged as pirates, this…

It's much older than that, from etymonline:

pirate (n.)

Meaning "one who takes another's work without permission" first recorded 1701; sense of "unlicensed radio broadcaster" (generally transmitting from a ship outside territorial waters) is from 1913.

pirate (v.)

"to rob on the high seas; commit piracy upon," 1570s, from pirate (n.). By 1706 as "appropriate and reproduce the literary or artistic work of another without right or permission; infringe on the copyright of another."

-- https://www.etymonline.com/word/pirate

sadly it doesn't explain the how of the word coming about.

Re: Transmission 4.0.0 beta 1

#140

Earlier quoted context omitted.

> Downloading it from a side channel means you can buy it on your favourite platform and actually keep it on your computer. That would give the distribution platform the idea that what they are doing is OK. In this case, just download it and don't pay for it, if they are not actually providing you of any service. Vote with your wallet.

How are the producers reimbursed in your example?

"Voting with your wallet" means reimbursing producers who can provide content in the way I prefer.
Post reply on HN