This repository has been archived by the owner on Apr 16, 2021. It is now read-only.
Explains the Files API a little bit more #43
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
|
lgtm |
|
LGTM |
|
This still needs to be published. i'll do it tomorrow. unless @lgierth gets to it first |
|
actually @whyrusleeping can you review too? |
|
Published: https://ipfs.io/ipfs/QmWQ5BwExewgJ6SkJoTjhfD1Z17EhyjvsFERmUoifd79LZ/ I can publish-to-domain if I can get an auth token. |
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.
A big connection I really wanted to make sure people made was that the Files
API produces a sequence of immutable snapshots of a filesystem, and that each
snapshot can be extracted and used like any other IPFS object. Hopefully I've
illustrated this here!