Use normal base64 encoding for RTC backend identities#5129
Merged
robintown merged 2 commits intomatrix-org:developfrom Jan 9, 2026
Merged
Use normal base64 encoding for RTC backend identities#5129robintown merged 2 commits intomatrix-org:developfrom
robintown merged 2 commits intomatrix-org:developfrom
Conversation
MSC4195 has been updated to specify that normal (non-URL-safe) base64 is the correct encoding for LiveKit participant identities.
BillCarsonFr
approved these changes
Jan 8, 2026
Member
BillCarsonFr
left a comment
There was a problem hiding this comment.
I think that in the spec we should also says that it is unpadded as per https://spec.matrix.org/v1.17/appendices/#unpadded-base64
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.
MSC4195 has been updated to specify that normal (non-URL-safe) base64 is the correct encoding for LiveKit participant identities.