docs: move kubo-specific docs #10226
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
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.
This is part of ipfs/specs#439.
The idea is to move Kubo-specific specs out of our
ipfs/specsrepository to avoid confusions. I glanced at this specifications, and especially the keystore one seems to be horribly out of date (especially the commands section). I updated the key command stuff, but we don't have aipfs crypt.I'm not sure if we'll want to clean it up fully, or just trim down the parts that are outdated. They are marked as WIP - as they were before - so I think it should be fine to merge them, or at least cut down some parts.