Repository navigation
Set the transport through hyper.video's transport setting - #16
Merged
Merged
Conversation
jlnstrk
force-pushed
the
jlnstrk/layered-settings-hooks
branch
from
October 23, 2026 14:23
bfbe1cd to
9e9f96d
Compare
jlnstrk
changed the base branch from
jlnstrk/layered-settings-hooks
to
jlnstrk/layered-settings-client
October 23, 2026 14:40
jlnstrk
force-pushed
the
jlnstrk/transport-setting
branch
from
October 23, 2026 14:46
97a3735 to
8537f90
Compare
hyper.video #6101 removes hyper.settings.sessionDebug.forceWebrtc and makes the transport a layered setting, transport, which takes automatic, webTransport or webRtc. Its default, automatic, connects over WebTransport where the browser has it, and over WebRTC elsewhere. The transport takes "default" next to webtransport and webrtc, and defaults to it, as the other settings that hyper.video decides do. "default" unsets the participant's transport, so that an admin's value for the session applies, else automatic. webtransport sets webTransport, and webrtc sets webRtc. The state reads webRtc as WebRTC, and automatic and webTransport as WebTransport.
jlnstrk
force-pushed
the
jlnstrk/transport-setting
branch
from
October 23, 2026 14:58
8537f90 to
0b43287
Compare
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today, the simulator forces a Hyper Core participant onto WebRTC through
hyper.settings.sessionDebug.forceWebrtc. hypervideo/hyper.video#6101 removes that hook and makes the transport a layered setting,transport, which takesautomatic(the default),webTransportorwebRtc. Once it deploys, the simulator's transport edit fails, and its participants lose their transport choice. Since #17 applies each setting on its own, the other settings and the microphone and camera state still apply.webrtcsets the participant'stransporttowebRtc, andwebtransporttowebTransport, which has no fallback to WebRTC.defaultunsets it, so that an admin's value for the session applies, elseautomatic, which connects over WebTransport where the browser has it, and over WebRTC elsewhere.webRtc, and WebTransport forwebTransportandautomatic.--transport, thetransportconfig key and--participantJSON takedefaultnext towebtransportandwebrtc, and default to it, as Edit Hyper Core settings throughhyper.settings.client#17's other settings do. The TUI lists it too, and Cloudflare participants still use WebRTC whatever the transport says.A
config.yamlthat the TUI saved namestransport: webtransport, which now asks for WebTransport only. Set it todefaultto let hyper.video choose.hypervideo/hyper.video#6101 runs on latest.dev, where the old
forceWebrtcpath does nothing, so this PR restores the transport choice there. A deployment without it, such as meet.hyper.video, drops thetransportedit, so--transporthas no effect there.