<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rawnlq</author><text>The underlying concept behind this isn&amp;#x27;t much different from &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;webtorrent.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;webtorrent.io&amp;#x2F;&lt;/a&gt; (I am pretty sure this could&amp;#x27;ve been built on top of the webtorrents protocol). I don&amp;#x27;t believe there are any insurmountable problems. Security, reliability etc have all been solved before.&lt;p&gt;But there&amp;#x27;s still no way you can make this faster than traditional CDNs (at the minimum you&amp;#x27;ll need an extra round trip to check for peers). As a matter of fact if my torrenting speed is any indication, it will be abysmally slow.&lt;p&gt;You probably won&amp;#x27;t be penny pinching over bandwidth cost when every 100ms of page load time costs you 1% in sales. &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;blog.gigaspaces.com&amp;#x2F;amazon-found-every-100ms-of-latency-cost-them-1-in-sales&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;blog.gigaspaces.com&amp;#x2F;amazon-found-every-100ms-of-laten...&lt;/a&gt;</text><parent_chain><item><author>zer0gravity</author><text>So many problems.&lt;p&gt;Security : how do you guarantee that a client peer is not tinkering with the code it distributes further?&lt;p&gt;Unreliable: browsing sessions come and go. Before forwarding the app maybe the browser is already closed..&lt;p&gt;Bandwidth: nobody loves bandwidth thieves&lt;p&gt;And so on...</text></item></parent_chain></comment><story><title>Viral.js – Peer-to-peer web app distribution</title><url>http://pixelscommander.github.io/Viral.JS/#.V5tY1ZN97UI</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>0x6c6f6c</author><text>This is an idea I&amp;#x27;ve had for websites such as Wikipedia where consumer funding is the main source keeping it alive.&lt;p&gt;This could be great for a small niche of applications, but even for those, these points are still important.&lt;p&gt;Particularly on the consumer end, turning my device into a provider as well as a consumer of data is typically not my intention. It&amp;#x27;s forced seeding on all clients in a torrent sense, which not everyone wants to be a part of. Or for that matter, can be. In a world of data caps, turning my phone, tablet, or hotspot connected devices into a CDN has moral and fiscal implications that have to be considered.</text><parent_chain><item><author>zer0gravity</author><text>So many problems.&lt;p&gt;Security : how do you guarantee that a client peer is not tinkering with the code it distributes further?&lt;p&gt;Unreliable: browsing sessions come and go. Before forwarding the app maybe the browser is already closed..&lt;p&gt;Bandwidth: nobody loves bandwidth thieves&lt;p&gt;And so on...</text></item></parent_chain></comment><story><title>Viral.js – Peer-to-peer web app distribution</title><url>http://pixelscommander.github.io/Viral.JS/#.V5tY1ZN97UI</url></story>