> That means the "servers" hosting it are distributed across a wide network.<p>This is a strange way of saying "you're looking at this site through one centralised server hosted at ipfs.io".<p>Don't get me wrong, IPFS is great. I have released an application that works over IPFS. But I don'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.
> 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's nothing IPFS-specific about this. It's the hosting for a webapp and a use of browser-based code.<p>In short, this isn'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't find it.<p><a href="https://beakerbrowser.com/" rel="nofollow">https://beakerbrowser.com/</a>
> We can't expect each client to have an ipfs client installed.<p>Couldn't they serve [js-ipfs](<a href="https://github.com/ipfs/js-ipfs" rel="nofollow">https://github.com/ipfs/js-ipfs</a>)?<p>AFAIK that would make every user of the web app run an IPFS node.
How did "Serverless" 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://github.com/cjb/serverless-webrtc" rel="nofollow">https://github.com/cjb/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 "LimeWire" 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 ;)
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.