If it could offer a transmission-compatible API-layer, I bet it would receive much more interest.
Edit: apparently not written in python. My bad.
11–20 of 73 posts
If it could offer a transmission-compatible API-layer, I bet it would receive much more interest.
Edit: apparently not written in python. My bad.
For automation software, transmission (BitTorrent-client written in python, slow) seems to be the standard. If it could offer a transmission-compatible API-layer, I bet it would receive much more interest. Edit: apparently not written in python. My bad.
For automation software, transmission (BitTorrent-client written in python, slow) seems to be the standard. If it could offer a transmission-compatible API-layer, I bet it would receive much more interest. Edit: apparently not written in python. My bad.
So, if I understand this correctly, Rust would be a good fit for bittorrent, right? Handling lots of stuff simultaneously, peers, trackers etc, to me a bittorrent that actually does more than download and quit always seems like something quite heavy...
Don't forget to seed!
For automation software, transmission (BitTorrent-client written in python, slow) seems to be the standard. If it could offer a transmission-compatible API-layer, I bet it would receive much more interest. Edit: apparently not written in python. My bad.
Your wish is satisfied: https://github.com/SirCmpwn/broca
(Also, what great irony this proxy is written in python, eh?)
Earlier quoted context omitted.
Your wish is satisfied: https://github.com/SirCmpwn/broca
Nice. Appreciated. Now I clearly have a weekend project. (Also, what great irony this proxy is written in python, eh?)
It's written by a different person (me). Also Transmission is written in C FYI
Not that I'm not always eager to see something get rewritten in Rust , but I'm curious whether web browsers have advanced to the point where a bittorrent client could exist as a webapp rather than requiring native installation. Could the bittorrent protocol operate over WebRTC?
Synapse is not designed for people who want this use-case. It's primarily designed for seedbox users who want a daemon to control remotely. It's also designed to efficiently work at scale, and takes advantage of native features like mmap to download quickly. Also, it wasn't rewritten in Rust from some other language, it was written in Rust in the first place.
So, if I understand this correctly, Rust would be a good fit for bittorrent, right? Handling lots of stuff simultaneously, peers, trackers etc, to me a bittorrent that actually does more than download and quit always seems like something quite heavy...
>a bittorrent that actually does more than download and quit always seems like something quite heavy... Don't forget to seed!