Webtorrent support

[faddat]

Does this client by any chance support webtorrent?

If no, anyone know of a go torrent solution that does?

thanks!

---

IssueHunt Summary

anacrolix has been rewarded.

Backers (Total: $250.00)

• steelbrain ($50.00)
• $200.00 have been anonymously funded.

Submitted pull Requests

• #393 Webtorrent support

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[anacrolix]

Do you refer to https://github.com/feross/webtorrent ? Can you link to a spec on bittorrent clients interacting with webrtc clients?

[faddat]

Not offhand, but I'm happy to google for it....

To leverage existing WebRTC implementations a dedicated instance of a Chromium browser is used. This 'bridge' mediates communication between Vuze and WebTorrent peers.
For the original implementation see https://webtorrent.io/

....ouch.

Maybe I can find better in the node.js?

[anacrolix]

That's as much as I found. If you found specifics in the node.js code, that may expedite adding support for this.

[faddat]

@feross

[feross]

Hey! We'd love to help make WebTorrent support happen here. We're working on a spec. I'll share here when it's complete. At the moment you can check out the following files, to see what's going on:

• client: https://github.com/feross/bittorrent-tracker/blob/e5812fdd29eef06e240e2522464a25098e394b52/lib/client/websocket-tracker.js
• server: https://github.com/feross/bittorrent-tracker/blob/e5812fdd29eef06e240e2522464a25098e394b52/server.js#L444-L573

To sum up what it would take to support this:

• webrtc library or bindings in Go
• websocket library

When a ws:// or wss:// tracker is detected, create a websocket connection to that server. There are a few extra announce message types to facilitate establishing webrtc connections "offer" and "answer", but everything else is essentially the same.

Once connected to a peer over WebRTC, you can treat the remote peer exactly the same -- the wire protocol is exactly the same.

[faddat]

Referenced in:

https://github.com/dawn-network/glogchain/issues/#10
https://github.com/dawn-network/glogchain/issues/#11

[mattlepacek]

Webtorrent support here would be amazing. The current node.js implementations are limited by chromes implementation of webrtc causing cpu time to multiply with each torrent being seeded. I'm interested in sponsoring Webtorrent support

[anacrolix]

I'll revisit this when there's a spec.

[KeizerDev]

Any updates on this?

[anacrolix]

No progress. There's no spec, and WebRTC is abysmal to work with.

[Sean-Der]

Hey @anacrolix !

I have been working on Go native WebRTC https://github.com/pions/webrtc and would love to get it to the point that you could use it!

It currently has full support for Audio/Video (send and recv) and I am maybe two weeks out from finishing DataChannels. We have ~5 developers involved, so things are moving pretty quick! If you are interested would love to chat/figure out what is most important to you. All the devs are on the Gophers slack in the #pion channel