-
-
Notifications
You must be signed in to change notification settings - Fork 673
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
peerflix does not seed a torrent after the file finished downloading #159
Comments
why would you want it to seed after the file has been downloaded? |
This is a great feature, though not as a default behavior. This would both help sustain the torrent community, and also make the less popular films accessible at a much more consistent speed. I know that most people don't want to share bandwidth, which is why i suggest it should be disabled by default. if we want torrents to remain available, and for etc popcorn time(which I heard are using peerflix) to remain a viable alternative to netflix, then it would be wise to give back to the community where possible. |
I aggree! While openned, peerflix should seed by default. That's the main feature of torrents. |
+1 |
2 similar comments
+1 |
+1 |
+1 |
+1 for a flag |
+1 |
+1 |
Not having this would kill the torrent system. |
+1, I actually thought this was already already integrated? |
+1 |
1 similar comment
+1 |
I don't even see any code where it gives you an option to seed a torrent in the first place? I thought this at least had the capability to already? |
+1 |
It is immoral to leech from swarms without giving back at least what you've taken. Projects like this are responsible for constantly degrading torrent swarms. Why did the developer think it was a good idea to not seed the files at all? It should've been the default behavior of this client, at least a 1.0 ratio. |
A 1.0 ratio should be the default |
i think this should be default behavior to continue seeding the torrent file and stop only after the user explicitly end the peerflix download..
The text was updated successfully, but these errors were encountered: