matched with another visitor via the relay's matchmaking, same as the pong/tic-tac-toe/screenshare demos. the relay only carries the WebRTC handshake (SDP offer/answer + ICE candidates) as ordinary opaque messages - once connected, files go directly peer-to-peer over a WebRTC data channel, not through this server at all. back to docs
uses a public STUN server plus a TURN relay for NAT traversal, so most strict/symmetric NAT pairs now connect peer-to-peer (through the TURN relay if a direct path isn't possible - note the browser's WebRTC stack still end-to-end encrypts the data channel with DTLS even when a TURN relay is in the path, so the relay operator can't read it either). if a connection still doesn't come up within 8 seconds, this page falls back to Pipe - a raw byte-stream tunnel this relay speaks natively (open_pipe/pipe_data), no longer private from the relay's view but fast and simple since it leans on the WebSocket connection's own guaranteed in-order delivery instead of reimplementing acks. If even that can't be set up (the one remaining failure mode: the peer disconnects in the handoff window), it falls back once more to the original relay-tunnel method - chunked, acked, retried over plain send/deliver - as the last resort. files are sent in chunks with no resume support - if either side reloads mid-transfer, start over.
connecting...
|
sending idle |
received |
log:
byte console - every blob that actually crosses the data channel, live: