181–190 of 262 posts
15.7 MB binary on macOS, in an age where it's usual to deliver a 400 MB Electron package. I kneel.
edit: ok, size is ~4.5M on my Debian, of which transmission-gtk accounts for 3.6. Maybe graph libs are bigger on mac ?
A long time ago I was a user of transmission, then they moved to c++ and it was over. I would use other now.
Over 10 years ago I've worked on a very custom BitTorrent-related application for an ISP. Roughly, it was a piece of software that acted like caching proxy but for torrents, intended to lower upstream congestion. Legal questions aside, it was a success - but, anyway, back to Transmission.
I needed a very custom client, and libtransmission was (in my personal opinion) hand-down the sanest and powerful option. I liked the design of the API, how there are only a minimum number of hoops to "just" get a torrent running, and yet how one can gradually expand. Honestly I don't remember any details beyond the overall impressions - it was very long time ago - but I liked it. And what I remember is that one of the features I valued was that it was written in C - because I wanted to use it from Python. I mean, C ABIs are generally quite significantly easier to work with in any language that has FFI, compared to C++ ABIs.
CFFI had improved since then, of course, and I haven't looked into v4 library at all so maybe they have an interface without any C++ nuances... But in general, the point is that libraries written in C are typically easier to interface with.
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.
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 openwr…
Still no support for webtorrents, making it impossible to use it for helping to lighten the load of my favorite peertube VODs :(
Earlier quoted context omitted.
How would your client know what other clients have uploaded to other clients?
Obviously you wouldn't (the network is decentralized, you can't know other peers communication) but also you don't care (peer A B might be able to upload/download, but peer B C can only download in one direction). The important part is to keep track of what's happening with your own connection to others, not what other peers are doing.
99%+ of the time any pair of peers has unidirectional traffic. The situation where two clients will have incomplete torrents and are exchanging data with each other is rare, like the first few hours after a brand new torrent hits the network.
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…
We need an open protocol for establishing tunnel/VPN connections. Apps implement the protocol, which lets you enter your tunnel provider and go through a quick OAuth flow to establish a tunnel. This would be a big win for VPN providers as well because people would be sending only specific traffic through them instead of everything.
15.7 MB binary on macOS, in an age where it's usual to deliver a 400 MB Electron package. I kneel.
I wonder how much stuff its including there. I use the alpine package for transmission and its 1mb https://pkgs.alpinelinux.org/package/edge/community/x86/tran...
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 openwr…
Sounds pretty awesome. I've not dabbled with PBR on home equipment. We did use it in prior employment to force all PCI traffic over a dedicated physical network between datacenters.
Earlier quoted context omitted.
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?