Nice! And fortunately this was a harmless mistake... one you wouldn't want to make with dd or shred instead, trust me.
Printable View
Nice! And fortunately this was a harmless mistake... one you wouldn't want to make with dd or shred instead, trust me.
I have this use case:
- ~40 torrents need to be seeded at 0 kb/s (to avoid Hit and Run warnings)
- 1 torrent needs to be seeded at 100 kb/s ( a popular torrent with a big swarm)
since joal does not support per torrent speed control, what would be the easiest way to achieve that ?
2 side by side docker instance ? Whould that be noticable by the torrent tracker ?
Your scenario is difficult to handle with a single instance. If those 40 torrents have zero leechers and you're completely sure this will always remain so, you can effectively ignore them as JOAL will never fake upload on torrents no one else is downloading, but that's a big if.
Running two separate Docker containers is a good idea as long as your emulated client uses an individual peer_id and key. Since it's possible for programs in different containers to use the same listen port(s), this would render each one's activity indistinguishable from the other as far as trackers are concerned (but do check the logs on both to ensure this).
Note your Docker bindings must account for the facts that 1. ports on the host (for accessing the Web UI) cannot be shared, 2. either instance must be reachable from the Internet at all times on the port it reports to the tracker if you want to show up as connectable.
@anon,
thanks,
I abandonned this route, 2 java applet would lead to an heavy computionnal burden.
Here is a modified version which will set a weight of 0, thus a speed of 0, for torrent whose filename starts with "HR".
https://github.com/lkjasdfoi/myjoal/...69b06c2d38170a
Be the change you want to see in the world =] Nice work!
@anthony-joal - Can you increase the variance of the torrent speeds. I'm noticing multiple torrents with the same upload speeds. I can send a screenshot in pm if you want it.
Is there a Transmission 4.0.0 or 4.0.1 client released yet?
Sorry I do not have the knowledge to create it by myself.
Thanks in advance.
To all client file writers, make sure to double-check Transmission's peer_id generation policy from here onwards...
Has been changes in the peer_id formation?
PD: Damn, 4.0.2 is out already...
Is this app safe to use as it seem to be very old and not updated for along time?
JOAL doesn't need a memory reader since (as described in the first post under "How to use it safely") it's not meant to be used simultaneously with a torrent client.
Not sure how you derived that conclusion from my post or why you'd bring up RM+. I suggest doing a little research on what the memory reader is and does first, it's well-documented.