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

Support for desktop torrent clients #162

Closed
iadj opened this issue Oct 23, 2014 · 6 comments
Closed

Support for desktop torrent clients #162

iadj opened this issue Oct 23, 2014 · 6 comments

Comments

@iadj
Copy link

@iadj iadj commented Oct 23, 2014

Webtorrent support for desktop torrent clients would be great as it'd allow for continuous seeding from desktop torrent client users to web users, therefore making files shared through WebTorrent apps way more sustainable for longevity .

From the WebTorrent documentation:
"We hope established torrent clients (uTorrent, Transmission, Vuze, etc.) will add support for WebRTC and the WebTorrent extensions so they can swarm with peers from both the normal and web networks."

Something I feel could speed up this process and allow projects to use WebTorrent along with desktop clients is to integrate WebTorrent support into an open source Torrent client (as a plugin) such as Deluge (http://deluge-torrent.org/), which is written in Python.

Would love to hear ideas!

@yipperr

This comment has been minimized.

Copy link

@yipperr yipperr commented Oct 23, 2014

if u bothered reading properly webtorrent repo is a torrent client written from the ground up packaged as an app using nodewebkit and angularjs. the lines u quoted is a means to allow existing torrent clients to expose there swarms over the new protocol. which is a different question altogether

@iadj

This comment has been minimized.

Copy link
Author

@iadj iadj commented Oct 23, 2014

However you're still unable to seed from any desktop torrent client to a user downloading with Webtorrent. I was hoping to discuss ideas on how to make this possible.

@yipperr

This comment has been minimized.

Copy link

@yipperr yipperr commented Oct 24, 2014

sorry i din't quite understand what u where saying added more to the fact that the both the desktop client and the web based torrent client have the same name (webtorrent). and torrents downloaded over the webtorrent app will serve as the first seeds for the webrtc torrent clients.

since webrtc requires signalling,implementing in all the torrent clients as a plugin seems trivial

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Oct 24, 2014

@iadj Integrating WebTorrent support into an open source client like Deluge, libtorrent, Transmission, etc. is a great idea. That would help WebTorrent adoption greatly!

@yipperr The term WebTorrent is overloaded – you're right. There are at least 4 uses already:

  • WebTorrent, the project/movement
  • webtorrent, the npm module (runs in node.js and the browser)
  • webtorrent, the command line node.js app (npm install webtorrent -g)
  • "WebTorrent extensions" to the BitTorrent protocol (this term indicates support for WebRTC peers)

In January, I'm planning to raise some funding (through donations) to pay contributors (like you or me) to develop these features since some of it is non-trivial. Stay tuned :)

@iadj

This comment has been minimized.

Copy link
Author

@iadj iadj commented Oct 25, 2014

Would love to raise some funds! Let me know!

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 1, 2015

This is a duplicate of #241, let's move discussion there.

@feross feross closed this Jul 1, 2015
@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.
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.