WebRTC Chat on IPFS

&gt; That means the &quot;servers&quot; hosting it are distributed across a wide network.<p>This is a strange way of saying &quot;you&#x27;re looking at this site through one centralised server hosted at ipfs.io&quot;.<p>Don&#x27;t get me wrong, IPFS is great. I have released an application that works over IPFS. But I don&#x27;t think obscuring the difference between a gateway and a node is beneficial. I think the difference needs to be highlighted front and centre, at least until we reach a point where every user is running an IPFS node without realising it.

&gt; To that end, this demonstration requires you to transfer your offering using some other means, like an email or instant message.<p>While I appreciate the effort that went involved, the effort is identical to serving the app over S3. Without solving this problem with something like IPFS pubsub, there&#x27;s nothing IPFS-specific about this. It&#x27;s the hosting for a webapp and a use of browser-based code.<p>In short, this isn&#x27;t WebRTC over IPFS.

I wanted to write that there is another similar project based on Beaker Browser (P2P) browser, that uses dat protocol and direct streaming to another browser... but I can&#x27;t find it.<p><a href="https:&#x2F;&#x2F;beakerbrowser.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;beakerbrowser.com&#x2F;</a>

&gt; We can&#x27;t expect each client to have an ipfs client installed.<p>Couldn&#x27;t they serve [js-ipfs](<a href="https:&#x2F;&#x2F;github.com&#x2F;ipfs&#x2F;js-ipfs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ipfs&#x2F;js-ipfs</a>)?<p>AFAIK that would make every user of the web app run an IPFS node.

What is used as STUN-Server for WebRtc?

How did &quot;Serverless&quot; become the term for things hosted on servers all over the place?<p>And we already had DHT before serverless became a thing... <i>sigh</i>

i get an empty offer to copy and the following js error: Error adding stream to pc1: NotFoundError: The object can not be found here. (FF + local ipfs gateway)

Please do head over to <a href="https:&#x2F;&#x2F;github.com&#x2F;cjb&#x2F;serverless-webrtc" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;cjb&#x2F;serverless-webrtc</a> to make issues and PRs! The most painstaking part for me is how long it takes to get the offer in the first place without a useful dialog.

This has potential. In peer brokering at scale, its the individual state of each peer that has to be mediated. The classic &quot;LimeWire&quot; problem. Just wondering as a peer, how much of my metadata gets leaked? Simply determining when or where I am chatting may be enough to de-anonymize me ;)

the problem is signaling, i wanted to use ethereum for signaling but there is to much back and forth to establish a connection for it to be viable.

As a browser author, are there any alternate implementations of WebRTC besides the one all of the browsers use?<p>From my research I was kind of shocked that the answer might be no.

Is there a version implementing video connections?

Can we stop calling everything &quot;serverless&quot;? It&#x27;s a stupid name. I assume it means peer-to-peer here right?

Interesting, why there is still no chat-on-blockchain thing. Sounds like an obvious idea for an ICO.