Add talk on IPLD in gateways to data agony track #55
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
aschmahmann
requested changes
Jun 30, 2022
Collaborator
aschmahmann
left a comment
aschmahmann
left a comment
There was a problem hiding this comment.
Looking forward to it. Left a formatting edit to get CI to be happy
Co-authored-by: Adin Schmahmann <[email protected]>
aschmahmann
approved these changes
Jul 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Gonna talk about IPLD on gateways and IPLD URLs.
We'll be looking at the proposed spec for IPLD on gateways, how it relates to URLs, and will be collecting feedback on the direction it should take and ideas for how it could be used.
Related: ipfs/specs#293