[Web] WebSocket reconnection needs exponential backoff with jitter

[Flegma]

Summary

WebSocket reconnection uses a fixed 1-second delay with no backoff, jitter, or max retry limit.

Findings

• Socket.ts — setTimeout(() => this.connect(), 1000) on every close event. No backoff or retry limit.

Impact

During outages, all clients hammer the server every second. Thundering herd on recovery. Battery drain on mobile.

Suggested Fix

Implement exponential backoff (1s, 2s, 4s, 8s... up to 30s) with random jitter. Add max retry limit with user notification.

---

Related Issues (WebSocket/Networking Pattern)

• [API] Harden match events gateway authentication and message validation #371 — [API] Harden match events gateway
• [Web] WebSocket reconnection needs exponential backoff with jitter #387 — [Web] WebSocket exponential backoff
• [Web] WebRTC connection lifecycle — missing timeout, aggressive cleanup, orphaned connections #388 — [Web] WebRTC connection lifecycle
• [Connector] RCON connection corruption, Redis silent failure, missing send timeout #408 — [Connector] RCON connection & Redis reliability

[Flegma]

Resolved by merged PR 5stackgg/web#263