feat: introduce webxdc.isAppSender and webxdc.isBroadcast#137
Open
feat: introduce webxdc.isAppSender and webxdc.isBroadcast#137
Conversation
This allows apps to behave differently, dependeing on the sending context.
…ared state chapters
adbenitez
approved these changes
Apr 18, 2026
r10s
approved these changes
Apr 18, 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
3 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.
see explanations for isAppSender/isBroadcast across spec and shared state chapters.
discussed with @r10s who also worked on the core PR of #136 and it turns out that this original two-flag approach appears clearer and simpler than the the latest iteration on that PR, where multiple people agreed to go for it, but it turned out it was lost to be able to determine if you are in a broadcast channel. Sorry, no senderAddresses here :)