Not really. WebRTC is explicitly designed to allow arbitrary data to be sent peer-to-peer, with things like encryption, NAT busting, etc. built in; layering fi

Not really. WebRTC is explicitly designed to allow arbitrary data to be sent peer-to-peer, with things like encryption, NAT busting, etc. built in; layering file transfer on top of it isn't a hack. It's not compatible with existing protocols, unfortunately, but raw UDP (and TCP) sockets are unlikely to be allowed on the web anytime soon due to security concerns; there are various efforts by browsers to provide APIs for this for use cases like the Chrome Web Store and Firefox's Open Web Apps, where security can be relaxed (e.g. [1] [2]) - and there are in fact torrent addons for both browsers - but on the actual web, you need an additional layer. In lieu of the web being able to speak BitTorrent, it would be nice if native BitTorrent clients started to speak web - that is, support bridging over WebRTC themselves. That is, in fact, what the author of instant.io is attempting, according to [3], with "WebTorrent.app". [1] https://developer.chrome.com/apps/sockets_udp https://developer.chrome.com/apps/sockets_udp [2] https://wiki.mozilla.org/Security/Reviews/TCPSocket https://wiki.mozilla.org/Security/Reviews/TCPSocket [3] https://github.com/feross/webtorrent https://github.com/feross/webtorrent