Re:GitHub reinstates Popcorn Time code
by londons_explore on Monday May 25, 2020 @05:56PM
(#23305372)
> The problem arises when all leechers request the beginning of an old and/or obscure torrent from one or few leechers.
If the sending client prioritizes data to clients requesting rare blocks, that problem is solved. It will also give clients an incentive to download the rarest blocks first to keep the swarm healthy.
Are there any VPNs that support the throughput speeds many consumers have access to these days? I have my client set to a 10:1 ratio, but rarely will a file actually reach that because I don't want to leave my slow VPN online for that long degrading my performance for other online tasks.
I've used commercial VPN with acceptable (think ~100Mbps) but not amazing throughput.
But for BT I just set up a secondary on-demand network interface on my Linux server specifically for OpenVPN (just need a shell script to add a couple ip(8) rules, and stick that shell script into the up command of ovpn config). Then I bind my transmission-daemon to that specific interface (bind-address-ipv4 option). This way all BT traffic goes through OpenVPN, but other traffic is not affected. Works for any OpenVPN provider.
This sounds fantastic, thanks for the idea and explanation!
Re:GitHub reinstates Popcorn Time code
by CaptainMarvel on Monday May 25, 2020 @05:35AM
(#23299501)
You can use split tunnelling or linux network namespaces to keep the VPN running at all times, but with only your torrent client‘s network connection going through it.
Some VPN companies also provide apps with the feature built-in.
> there isnt anymore the "everyone wants to download far more than they can be bothered to upload" issue.
There’s the “people quit their BT client as soon as they finish their download” problem which faster internet doesn’t solve.