Experiment with image payloads in playground#142
Draft
marcus-pousette wants to merge 11 commits into
Draft
Conversation
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.
Summary
@treecrdt/content, a small app-layer content protocol for TreeCRDT payload bytes: raw UTF-8 text stays compatible, while images use a compact binary envelope with JSON metadata plus raw bytes.+ Addmenus for text nodes, image nodes, random images, and bulk fanout experiments.Why This Shape
TreeCRDT core still only stores
Uint8Arraypayloads.@treecrdt/contentis the reusable meta-protocol above that layer, so future text/file/image/video handling can evolve without making core media-specific. This PR intentionally proves the simple inline path first; chunked or external blob-backed content can extend the same package later.Example