WebSocket Test - wss.getlost.ovh

This page connects to a public, free signaling WebSocket server at wss://wss.getlost.ovh. It is provided strictly for testing. There is no authentication and no persistence: it is a thin relay used to exchange WebRTC descriptors (SDP/ICE) and to maintain a per‑room roster of peers.

The server code is in examples/server/ws-server.mjs. Here is exactly what it does:

• Connection and rooms: upon receiving the first JSON message with a roomId, the socket is attached to that room (created if missing). For each room the server tracks the set of sockets and a roster (list of player identifiers).
• Presence announcement: if a message contains announce: true and a from (your Player ID), that ID is stored for the connection and added to the room roster. The server then broadcasts to everyone in the room a roster update of the form { sys: 'roster', roomId, roster: [...] }.
• Message routing:
  • If a to field is present, the JSON payload is relayed as‑is to the targeted recipient (same room, playerId === to).
  • Otherwise the message is broadcast to all other clients in the room (excluding the sender).
• Stateless: the server keeps no message history. Newly connected clients do not receive past messages.
• Disconnect: when a socket closes it is removed from the room; if a playerId had been announced it is removed from the roster. Empty rooms are deleted; otherwise a fresh sys: 'roster' is broadcast.
• Security and limits:
  • No authentication: anyone who knows a roomId can join that room.
  • No schema validation or sanitization: the server simply relays JSON. Do not send secrets.
  • Transport is WSS (TLS) but there is no end‑to‑end encryption: the server sees the JSON it relays.
  • Test‑only, best‑effort service: availability is not guaranteed; no quotas, no SLA.
  • Signaling only: your actual game data should go P2P over WebRTC DataChannels.
  • No explicit rate limiting; abusive traffic may be blocked at any time.

Connect to the WebSocket Signaling Server