This repository has been archived by the owner on Sep 21, 2024. It is now read-only.
Implement orb sync subcommand
#107
Merged
Conversation
This file contains 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
jsantell
previously approved these changes
Oct 24, 2022
jsantell
approved these changes
Oct 24, 2022
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This change implements the
orb syncsubcommand, which represents the first plausibly end-user-accessible path to accessing the Noosphere across multiple of their own devices.I recorded an end-to-end demo of multi-device synchronization in action last week:
Note that the demo was recorded against work in progress, and should not be considered a full-fidelity representation of the change in this branch.
In addition to the enhancements in this change, I also ran
cargo clippy --fixas a one-off to clean up our outstanding warnings and lint infractions.Follow-on work is captured as issues in ucan-wg/rs-ucan#37, ucan-wg/rs-ucan#32, #102, #103, #104, #105 and #106.
Fixes #87
Fixes #75