From 228f1f4fb3706ef2e6f0ca15b9201ea1f34ae1a4 Mon Sep 17 00:00:00 2001 From: rainbow napkin Date: Wed, 28 Oct 2026 21:58:10 -0400 Subject: [PATCH] Updated streaminfo --- src/views/streamInfo.ejs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/views/streamInfo.ejs b/src/views/streamInfo.ejs index 8d8cbaa..b1f910b 100644 --- a/src/views/streamInfo.ejs +++ b/src/views/streamInfo.ejs @@ -47,7 +47,7 @@ along with this program. If not, see . %>

Pros/Cons of WebRTC:

- WebRTC connections come in two flavors, STUN and TURN. STUN uses an intermediary server, to make a connection through your firewall, to another established peer. For certain connections, some users, suchas those on a CGNAT, will require a TURN server to relay the connection. At the current moment, ourfore.st only supplies STUN servers, however we do plan on looking into TURN relay servers in the future. + WebRTC connections come in two flavors, STUN and TURN. STUN uses an intermediary server, to make a connection through your firewall, to another established peer. Some users, such as those on a CGNAT, will require a TURN server to relay the connection.

This means that each viewer uses up part of a streamers bandwidth, comparitively to HLS, in which the streaming-server takes the load of multiple connections off of the streamers connection (assuming they're it's not hosted on the same connection.) Furthermore, WebRTC's video-chat roots prioritizes real-time communication over video/audio quality. That being said, WebRTC requires no extra setup, and no extra software other than this website and your browser.