This standalone JS file will eventually be the primary WebTorrent client that most users interact with. and also allow the programmer to get the data programmatically without UI too.
We'll have a good default "viewer" UI depending on the file type: PDF viewer, image viewer, audio/video tag (if the format allows for streaming), etc. torrent file) (or a magnet uri) and the WebTorrent script will do the rest. All they need to provide is the info hash (or a. We'll use this new protocol to ship a standalone JS file that webmasters can add to their site if they want to fetch files over webtorrent. This new protocol will be called "the WebTorrent protocol", or "WebTorrent extensions". The protocol obviously needs some modifications, but all the main concepts will remain intact. The second objective is to make the BitTorrent protocol work over WebRTC. I did this first to learn how existing clients work and because lots of this code will be reused by the WebRTC client. This is now finished, though we still need to add support for additional features and polish to bring it on par with other modern clients. The first is to develop a working JavaScript BitTorrent client as a Chrome App. To accomplish that goal, I have two objectives. The goal of the project is to build a browser BitTorrent client that requires no install (no plugin/extension/etc.) and interoperates with the regular BitTorrent network, though it uses WebRTC Data Channels for peer-to-peer transport. Let me try to clear up a little confusion about what WebTorrent is and how it works.