This repository was archived by the owner on Jun 17, 2026. It is now read-only.
reorder Next steps: Client then Server - #3
Merged
Merged
Conversation
markbackman
approved these changes
Oct 21, 2025
markbackman
left a comment
markbackman
left a comment
Contributor
There was a problem hiding this comment.
Good idea! Mind adding a changelog entry?
Mic Off -> Mic is Off
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
New folks might get confused by a frontend url being offered by the runner with smallwebRTC transport in addition to a separate client url. My suggestion is to give instructions for Client next steps first, then Server next steps. It still might be confusing to see the url from the Server, but I think this instruction order will help.