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

Reach out to libtorrent, libtransmission, Vuze, Deluge projects #241

Closed
iShift opened this issue Jan 13, 2015 · 2 comments
Closed

Reach out to libtorrent, libtransmission, Vuze, Deluge projects #241

iShift opened this issue Jan 13, 2015 · 2 comments
Labels
meta

Comments

@iShift
Copy link
Contributor

@iShift iShift commented Jan 13, 2015

Webtorrent - cool project, but now project have Chicken and egg problem - people don't use them because traditional torrent clients don't support WebRTC torrent protocol.

I think, that to solve that problem we need to add new protocol to libtorrent, after that - all main torrent client start work with webtorrent.

(I talk about issue in libtorrent/tranmission/another_torrent_client_or_lib tracker) also we can help them with bounty program.

What do you think about that?
@feross

This comment has been minimized.

Sign in to view
Copy link
Member

@feross feross commented Apr 11, 2015

Yeah, I would love for libtorrent to support web peers. That would be huge! Then lots of other clients could really easily swarm with web peers.

Once the webtorrent hybrid client is in a bit better shape and the BEP is written up, the demo will be much more compelling and we should ask them about it.
@feross feross changed the title Chicken or egg problem Reach out to libtorrent, libtransmission, Vuze projects Jul 1, 2015
@feross feross added the meta label Jul 1, 2015
@feross feross changed the title Reach out to libtorrent, libtransmission, Vuze projects Reach out to libtorrent, libtransmission, Vuze, Deluge projects Jul 1, 2015
This was referenced Jul 1, 2015
Closed
Open
@feross

This comment has been minimized.

Sign in to view
Copy link
Member

@feross feross commented Jul 7, 2015

Now tracking this in #369
@feross feross closed this Jul 7, 2015
@feross feross mentioned this issue Jul 7, 2015
Closed
@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
meta
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@iShift @feross
You can’t perform that action at this time.