SecureBit.chat - P2P Encrypted Messenger Files

Adds optional, advanced control over WebRTC connectivity for power and privacy-focused users. Public servers remain the zero-config default.

Added

• Advanced network settings panel — reachable from the header gear icon and the connection-creation screen — where users can supply their own STUN/TURN servers instead of the bundled public defaults.
• Allowlist-based validation of user input: only stun:/stuns:/turn:/turns: URLs with valid hosts are accepted; javascript:, data:, http(s):, ws(s):, control characters, and oversized input are rejected before anything reaches RTCPeerConnection.
• Optional on-device persistence, encrypted at rest with a non-extractable AES-GCM device key in IndexedDB, with an explicit save prompt and a "Forget saved" action.
• "Test servers" button that gathers ICE candidates against the entered configuration and reports STUN/TURN reachability.
• Privacy guidance in the panel: a TURN relay sees peer IPs and traffic timing (never message contents), so only a trusted or self-hosted relay improves privacy.

Changed

• Relay-only privacy mode now lives in the advanced settings panel; the standalone relay-only toggle was removed from the start screen to declutter the initial view.
• Server selection priority: user custom servers > operator override (config/ice-servers.js) > built-in public defaults.

Full changelog: https://github.com/SecureBitChat/securebit-chat/blob/main/CHANGELOG.md