Route traffic thought other peers.

[jimmywarting]

WebTorrent is awesome since it uses WebRTC for peer-to-peer transport. It works without browser plugins, extensions, or any installations. And i believe that have been the solo purpose of building WebTorrent in the first place. But the big bottleneck is that there isn't enough hybrid or WebTorrent clients out there to make it somewhat useful in the browser. (not until other torrent clients start supporting WebRTC transport)

One way to solve this could be to route traffic thought other hybrid peers that are able to establish a TCP/UDP connection on behalf of WebRTC clients out there. At least until there is enough WebRTC peers in the swarm. I have seen some torrent client doing this... One example is Tribler. (they don't support WebRTC but traffic go thought other peers before it comes to you) so a middle man is download pieces for you but don't keep the content for themself.

Would this be something of interest?

[KayleePop]

This is discussed here #325

[jimmywarting]

Hmm, didn't quite feel like the idea i had in mind? did look more like a proxy... A think you need to install to make it to some sort of WebSeed? then it still comes down to having too install something locally on every machine?

The problem i'm seeing with this comment:

The bridge downloads the torrent file from the bittorrent network using webtorrent and exposes the file('s) as an WebSeed, accessible via http(s) using the http module ... The adding and downloading of the file from the bittorrent network is done on demand when a client requests it from the webseed

...is that not any peer can't access the WebSeed sense it probably just be a local address (localhost)

what i'm after is something more of a WebRTC-Seeder (same thing like a WebSeed but with hybrid peers instead)

[DiegoRBaquero]

You could setup a server with webtorrent-hybrid that is asked to add certain hashes so that they become available to WebRTC networks. But again, this is out of the scope of the library and webtorrent-hybrid itself.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.