3 ms·
Why bake libtransmission into the app instead of just using the transmission daemon's RPC? What you've done actually makes it harder to use, because in order t
by stinkypeterson 3y ago
Why bake libtransmission into the app instead of just using the transmission daemon's RPC?
What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.
I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]
1: https://github.com/transmission/transmission/blob/main/docs/Editing-Configuration-Files.md https://github.com/transmission/transmission/blob/main/docs/...
1: https://github.com/jesec/flood https://github.com/jesec/flood
2: https://github.com/ronggang/transmission-web-control https://github.com/ronggang/transmission-web-control
- G-Ray 3y agoThis is a very good question. I preferred to bundle libtransmission to offer a plug'n play experience across all platforms. Regarding all the criticism here, I believe PikaTorrent should primarily focus on new or average torrent users. Advanced users might either modify the settings file manually for now (though guessing the path is not ideal), or perhaps PikaTorrent should expose a textarea to edit transmission settings (though this approach might be risky for average users). In the meantime, I plan to expose a lot more Transmission settings in the UI. Even for me, PikaTorrent is not mature enough to fulfill all my needs. However, with more features to come and potential feature requests from users on GitHub, it might become a suitable BitTorrent client for advanced users and server usages.