pirate / webrtcchat

:lock_with_ink_pen: Pure Browser To Browser Chat (STUN & ICE Servers optional)

Serverless WebRTC Chat

NOTE: This project was done in the early days of WebRTC and is no longer working as well as it used to, the methods within may be outdated or broken.

Click here to Chat Now.

Pure Browser To Browser Chat, (STUN or ICE Servers optional, it should work without them if don't have a super strict NAT).

Features

• encrypted chat, with no history stored on refresh
• bi-directional file sharing
• bi-directional video and audio sharing
• optional typing notifications
• optional setup without STUN/ICE servers for true serverless chat

Links

• https://nicksweeting.com/scan.html
• https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection
• https://www.html5rocks.com/en/tutorials/webrtc/basics/
• https://github.com/webrtc/samples
• https://webrtc.github.io/samples/
• https://www.webrtc-experiment.com/
• https://github.com/Mahabali/BonjourWebrtc
• https://getkey.eu/blog/5862b0cf/webrtc:-the-future-of-web-games
• https://www.twilio.com/blog/2014/12/set-phasers-to-stunturn-getting-started-with-webrtc-using-node-js-socket-io-and-twilios-nat-traversal-service.html
• https://github.com/beefproject/beef/wiki/Module:-Get-Internal-IP-WebRTC

---

MIT License | Nick Sweeting 2014
An enhanced & rewritten fork of: https://github.com/cjb/serverless-webrtc

webrtcchat's Issues

Unable to connect when running from two different laptops on the same network

webrtc_internals_dump-host.txt
webrtc_internals_dump-join.txt

Thanks for this excellent work. It helped me get an idea on how to connect 2 WebRTC channels without using a server / backend. I am however facing a very basic problem. I am able to use the JS application when I open 2 browser instances on the same laptop.

However, surpringly I am unable to to get the JS application to work when I use the applications from 2 different laptops even though they are on the same network. I tried this multiple times and of the many attempts, I was able to get the 2 instances to communicate only once. I am therefore assuming this is some kind of a timing issue.

The client joining the conference (not the one hosting the conference) complains that the "Chat partner disconnected". I am not an expert in WebRTC or JavaScript but I debugged this a little further and found that the client joining the conference receives a "oniceconnectionstatechange" event twice after the offer / answers are exchanged. It first receives "Disconnected" and eventually "Failed".

I am using chrome Version 88.0.4324.104 (Official Build) (64-bit) and am on Windows 10 OS. The behaviour is same even if I use Edge.

I have attached the chrome://webrtc-internals/ logs. Anything else that might help you help me. I am willing to debug the problem further but am unable to figure out how to take this forward.

multiple connections and/or persist connection init info?

I tested this out, looks pretty useful. I wonder how hard the 2 things I mentioned in the title would be to achieve[they may be impossible, input please]?

to clarify:

1. what would be some paths of least resistance to having more than 2 people connected together? Would it even be possible for more than one person to use the same session-init-credentials? or would that cause interference?

2. after a successful 'handshake'/session-init, is there any chance some credentials could be persisted - so that the next time the html was fired up, a connection can happen more automatically?

signaling doesn't work on safari

hi thanxs for sharing, i tested on safari and the signaling popups (exchanging the offer) don't work.

so is it just a demo for firefox or something we can use on all platforms?