Skip to content

/ webtorrent

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

Jump to bottom

Implement strategy to detect non seeded torrents #384

Closed
ericwooley opened this issue Jul 21, 2015 · 5 comments
Closed

Implement strategy to detect non seeded torrents #384

ericwooley opened this issue Jul 21, 2015 · 5 comments
Labels
enhancement good first contribution help wanted

Comments

@ericwooley
Copy link
Contributor

@ericwooley ericwooley commented Jul 21, 2015

As @feross suggested in gitter, one possible solution is to emmit event 'no-peers' when there are no peers available on a torrent.
@rom1504 rom1504 mentioned this issue Jul 24, 2015
Open
@feross feross mentioned this issue Jul 27, 2015
Closed
@Stiveknx

This comment has been minimized.

Sign in to view
Copy link
Contributor

@Stiveknx Stiveknx commented Jul 29, 2015

+1
1 similar comment
@eliooses

This comment has been minimized.

Sign in to view
Copy link

@eliooses eliooses commented Nov 3, 2015

+1
@harperj

This comment has been minimized.

Sign in to view
Copy link

@harperj harperj commented Apr 27, 2016

#775 Adds this 'noPeers' event whenever an announce occurs, but the resulting swarm contains no peers. I think this doesn't quite solve the problem of detecting "non seeded torrents" though. We might also look at all of our peers and see if the set of desired pieces is available before emitting a "notSeeded" event.

Thoughts?
@feross

This comment has been minimized.

Sign in to view
Copy link
Member

@feross feross commented May 5, 2016

Done in #775
@feross feross closed this May 5, 2016
@lock

This comment has been minimized.

Sign in to view
Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.
@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement good first contribution help wanted
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
@ericwooley @Stiveknx @eliooses @harperj @feross
You can’t perform that action at this time.