title: Can a browser communicate with another browser on the same network directly?
body: <p>I'm playing around trying to find a way to communicate between two browsers on the same network to establish WebRTC without a server roundtrip (no STUN/ICE/TURN). Basically an alternative to the approach found <a href="http://cjb.github.io/serverless-webrtc/serverless-webrtc.html" rel="nofollow noreferrer">here</a>, where the "handshake" is done via copy/mail/pasting. </p>
  
  <p>After sifting through all the cross-browser-communication examples I could find (like <a href="http://theprivateland.com/bncconnector/demo.htm" rel="nofollow noreferrer">via cookies</a> or <a href="http://artemyankov.com/tcp-client-for-browsers/" rel="nofollow noreferrer">WebTCP</a>) plus a bunch of questions on SO (like <a href="https://stackoverflow.com/questions/3342140/cross-domain-cookies">here</a>), I'm back to wondering a simple thing:</p>
  
  <p><strong>Question</strong>:<br>
  If Alice and Bob visit the same page <code>foo.html</code> while on the same network and they know each others' internal assigned IP addresses, are there any ways they can communicate purely with what is available on the browser?</p>
  
  <p>This excludes non-standard APIs like <a href="https://developer.mozilla.org/en-US/docs/Web/API/TCP_Socket_API" rel="nofollow noreferrer">Mozilla TCP_Socket_API</a>, but other than that all "tricks" are allowed (img tags, iframes, cookies, etc.). </p>
  
  <p>I'm just curious if I can listen to someone on the same network "broadcasting" something via the browser at all.</p>
  
  <p><strong>Edit</strong>:<br>
  <code>foo.html</code> will be on static server, no logic, no ICE, no shortcut.</p>
  
  <p><strong>Edit</strong>:<br>
  Still not a solution but a websocket server as Chrome extension comes closer. Example here: <a href="https://github.com/frequent/nexedi-serverless-test" rel="nofollow noreferrer">almost pure browser serverless WebRTC</a></p>