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

Clientside can't find seeder from webtorrent-hybrid #356

Closed
afshinm opened this issue Jun 12, 2015 · 4 comments
Closed

Clientside can't find seeder from webtorrent-hybrid #356

afshinm opened this issue Jun 12, 2015 · 4 comments

Comments

@afshinm
Copy link
Contributor

@afshinm afshinm commented Jun 12, 2015

Recently I've developed http://www.peopledrivenweb.com/ which is a cms based on torrent. Here is the Github repo: https://github.com/peopledrivenweb/pwjs

The issue is, sometimes it takes too long to find a seeder from webtorrent-hybrid but sometimes it works really fast. I monitored resource on the server-side but I didn't find anything special.

What is the problem? Is this related to browser or serverside codes?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jun 12, 2015

Seriously cool site! All sites should be powered this way! Peer-assisted delivery!

Not sure what the issue could be, based on your description. If you learn anything new, please share.

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Dec 14, 2015

@afshinm Any updates?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jan 1, 2016

Looks like his site is down now. Also, I expect that webtorrent-hybrid will undergo some big changes soon once we switch the webrtc implementation that's used, so this issue will be irrelevant.

@feross feross closed this Jan 1, 2016
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 5, 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 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.