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

Getting seeders/leechers from webtorrent? #298

Open
akhilcacharya opened this issue Apr 19, 2015 · 2 comments
Open

Getting seeders/leechers from webtorrent? #298

akhilcacharya opened this issue Apr 19, 2015 · 2 comments
Labels
accepted enhancement help wanted

Comments

@akhilcacharya
Copy link

@akhilcacharya akhilcacharya commented Apr 19, 2015

How would one get the number of seeders and leechers form a particular torrent?
@feross

This comment has been minimized.

Sign in to view
Copy link
Member

@feross feross commented Apr 20, 2015

There's no easy way to do this right now. PR welcome!

There are two possible ways to interpret this feature request:

  • How many peers that our client is connected to are seeders vs. leechers?
  • How many complete vs. incomplete peers are reported by each tracker that we are connected to?
@rom1504 rom1504 mentioned this issue Jan 7, 2016
Closed
@vankasteelj

This comment has been minimized.

Sign in to view
Copy link

@vankasteelj vankasteelj commented Dec 8, 2016 •
edited

I'm interrested in this feature too, to know if and how many of the peers I'm connected to at some point are 'peers I can download from', if the speed is at 0 (are we all trying to get a file that nobody seeds? or is the connexion only taking some time? this kind of info is useful)

There is the wire.isSeeder api, can't that be used?
@feross feross added accepted and removed accepted labels May 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted enhancement help wanted
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@akhilcacharya @feross @vankasteelj
You can’t perform that action at this time.