7/28/2023 0 Comments Webtorrent![]() ![]() Yes, there are probably a lot more people working on fixing bugs in the browser, but there are also a lot of people adding/modifying features and thus creating new bugs. That's even worse for the browser: you have to trust several orders of magnitude more code implementing a massive set of interdependent features. If we account for complexity by using a metric like "(man-years of battle-testing)/(magnitude of attack surface)", a well-tested specialized client that hasn't had many recent bug reports is a much safer choice than anything running in a browser. Resource webtor.io is a fully automated platform, that makes it possbile for the users to stream content online, transmitted through the BitTorrent protocol. webtorrent facilitates streaming over torrents including magnet URIs, but does not afaik support playlists. You don't have to wait for it to finish downloading. Whether it's video from the Internet Archive, music from Creative Commons, or audiobooks from Librivox, you can play it right away. If you only consider the number of man-years an application has been battle-tested, you imply that design complexity and attack surface doesn't matter. WebTorrent Desktop is for streaming torrents. A specialized client that only implements one protocol without any connection to the "web" is far easier to reason about and debug. In node.js, this module is a simple torrent client, using TCP and UDP to talk to other torrent clients. They also have a monstrous attack surface because they are "web-facing". Browsers are far more battle-tested than just about any other web-facing application on your computer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |