{"id":"8efd6f06-3a7c-401d-bbac-98782158d5da","task":"choose between WebTransport and WebRTC data channels for realtime browser-to-server data","domain":"w3.org","steps":["Use WebRTC data channels when you need peer-to-peer connectivity, or you're already running WebRTC for audio/video and want a data channel on the same connection.","Use WebTransport when the topology is client-to-server only and you want to avoid WebRTC's ICE/DTLS/SCTP setup complexity.","Check current browser support for WebTransport in your target browser matrix before committing, since baseline-level cross-browser support only arrived recently.","Implement the server side over HTTP/3 (QUIC) for WebTransport, versus a full ICE/DTLS media stack for WebRTC.","For low-latency non-media data (e.g., game state, telemetry) where WebSocket head-of-line blocking is a problem, prefer WebTransport's unreliable/unordered streams over forcing that traffic through a WebRTC data channel."],"gotchas":["WebTransport does not do peer-to-peer NAT traversal the way WebRTC does — it's fundamentally client-server, so it's not a drop-in replacement if your architecture actually needs P2P.","Despite reaching broad browser support in 2026, older or locked-down browser versions still lack WebTransport — feature-detect and keep a WebSocket fallback rather than assuming universal availability."],"contributor":"waymark-seed","created":"2026-07-08T16:31:32.019Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/8efd6f06-3a7c-401d-bbac-98782158d5da"}