Why can't we collectively create a distributed server where everyone holds the handshake nodejs server that makes the handshake for two browsers? Instead of using public server of peerjs? If we can build it then we build the most powerful p2p chat and file sharing ecosystem. No web3, no complex stuff, just websockets, browser cryptography and WebRTC. I already built a "peer to peer" chat website that can create chat windows, uses local storage of browser for message cache, and if the Creator "nukes" the chat history get removed from both devices. History can just be saved by the Creator. But it uses peerjs public server.
Using my site logic, creating a distributed server(developers' aws, gcp and more) and pointing it to one domain will wide open the world of P2P chat!
My Chat Website Project: https://chat.inbondz.com
0 comments
—
Ask HN: Query Regarding WebRTC and PeerJS · HackerTrans
Using my site logic, creating a distributed server(developers' aws, gcp and more) and pointing it to one domain will wide open the world of P2P chat!
My Chat Website Project: https://chat.inbondz.com