> I think the problem lies with the browser vendors, who aren't implementing the bittorrent protocol in the browser.
browser vendors shouldn't have to implement it. they should expose posix-like APIs (bsd sockets, file IO) or process management+ipc via plain pipes (talk to native bittorrent client) so it could be provided through an extension.
The problem with browsers is that they create a backwards-incompatible API stack. This is understandable for web content. Not so for extensions.
browser vendors shouldn't have to implement it. they should expose posix-like APIs (bsd sockets, file IO) or process management+ipc via plain pipes (talk to native bittorrent client) so it could be provided through an extension.
The problem with browsers is that they create a backwards-incompatible API stack. This is understandable for web content. Not so for extensions.