Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SUGGESTION] Add option to enable outgoing connections while seeding #366

Open
officiallor opened this issue Dec 5, 2024 · 4 comments
Open

Comments

@officiallor
Copy link

officiallor commented Dec 5, 2024

I saw an option in an android client called outgoing connections for seeding. As far as I understand, when the download is finished, then it just waits for other peers to initialize a connection to the seeder (in this case me).
This is good when you have forwarded the port and everything but it makes it harder for someone not having the option to port forward, for example while using data or behind a VPN.
It could be very useful to add a toggle for this option as well. I am not sure how is the property called in libtorrent.
I can provide the link to the FOSS android torrent client if can be helpful.

@XITRIX
Copy link
Owner

XITRIX commented Dec 6, 2024

I could check, if you'll provide example from Android app it will be very useful

@officiallor
Copy link
Author

I could check, if you'll provide example from Android app it will be very useful

https://github.com/proninyaroslav/libretorrent

I tried to understand what property it is in libtorrent without cloning but couldn't.
The option is called outgoing connections for seeding in the app's settings.

@XITRIX
Copy link
Owner

XITRIX commented Dec 9, 2024

Could you send a screenshout with exact setting from this app you want me to implement? It will be easier for me to find it in source code

@officiallor
Copy link
Author

Sorry for the late reply. Here it is
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants