> Simply put, it allows anyone to utilize our powerful technology to create completely fresh and new experiences for users with just a couple lines of code.<p>Worst use of "simply put" I've seen in a while. This page actually puts it simply: <a href="http://torque.bittorrent.com/labs/" rel="nofollow">http://torque.bittorrent.com/labs/</a><p>> Turns all torrents links into regular downloads. No torrents to manage. Just content.
I don't know why, but I had a visceral reaction to the browser prompt to install the extension in the paddleover demo. This is despite the fact that I'm a developer, and I'm well familiar with bittorrent. Maybe it has something to do with the fact that I feel like I have to be keenly aware of what my BT client is doing at any given moment. The thought of letting a BT client run unchecked in my browser is disconcerting ... am I completely off base here?
Can you translate to me what this is about?<p>Is it a javascript bittorrent client? Access to local bittorrent client? Access to remote bittorrent client?<p>I don't want to sound ignorant, I am just confused :(
> OneClick: Turn your torrent downloads into normal in-browser downloads.<p>This has been possible in Opera out-of-the-box for half a decade.<p>Apparently with Torque I have to manually install a third-party plug-in, and that plugin only works on Windows. Great progress there. It's like replacing HTML5 with Adobe Flash: from native browser support back to a proprietary plug-in.
Pretty awesome. I can see this technology displacing CDNs in the future... everybody is a edge node!<p>The plugin downloader is still a large barrier to entry, though.What I'd really like to see is a parallel protocol to BitTorrent that's basically BitTorrent over WebSockets. Consider an update to Vuze, uTorrent, Transmission, and all the other clients, that added a simple WebSocket server. Now, Alice's web browser will never be able to connect to Bob's web browser directly (at least in the foreseeable future), but they could conceivably both connect to Charlie's full client if Charlie was running this server. And the trackers would need to be updated to serve Charlie's address to Alice and Bob (or HTTP proxies to the trackers would need to be developed), but then Alice and Bob could start building the DHT in their LocalStorages. I'm sure I'm missing a lot of technical challenges, but I think this might be feasible.
This is crazy, crazy good. And, it would be nice if it were javascript only; you could then get people to upgrade for better features. I wonder if packaging it for site admins rather than browser users is the right plan?
As soon as WebRTC hits, it will be possible to do pure-JS bittorrent clients (and there's already some projects on github)<p>I'm not sure why they spent the time on a plugin
Hmm, so I can create a web app that runs without a server... I can just post a link to a simple JS page that will start downloading the app and execute it in the background.<p>I don't see a use for this, though. It's not much different from just downloading the code and running it, although it'll be much simpler to install.