docs(exploration): sharing non-doc-room nodes (channels, workspaces)#463
Open
crs48 wants to merge 1 commit into
Open
docs(exploration): sharing non-doc-room nodes (channels, workspaces)#463crs48 wants to merge 1 commit into
crs48 wants to merge 1 commit into
Conversation
…spaces) Signed-off-by: xNet Test <test@xnet.dev>
Contributor
|
Preview: https://xnet.fyi/pr/463/app/ |
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
1 participant
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.
Exploration 0298 — designs the real fix for the channel/workspace share bug found today: shared channels open an empty 'untitled' channel because channels/messages/workspaces are plain NodeStore nodes that sync only in a per-author DID room, while share grants only authorize per-doc Yjs rooms (
xnet-doc-<id>).Captures requirements (ongoing message sync, comment/write role semantics, revocation, DM exclusion, owner's channel list, workspace transitive content) and compares three transports — (A) per-resource share room, (B) server fan-out/grant pull, (C) container room generalizing the 0179 Space cascade — recommending A, phased and generalized toward C. Includes root-cause diagrams, example code sketches, and implementation/validation checklists.
Doc only; no code changes. Follows the decision to design before building.
🤖 Generated with Claude Code