Add DWeb Addressing intro and table of contents #167
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
ghost
self-assigned this
lidel
reviewed
Nov 12, 2017
addressing/README.md
Outdated
| - Network addressing | ||
| - Interoperability | ||
| - DWeb Addressing with HTTP | ||
| - URL schemes |
There was a problem hiding this comment.
I would explicitly put names here ("URL schemes: ipfs:// and ipns://"), just like we have dweb: below.
It is what people usually ask about, and it makes sense to have these names pop.
whyrusleeping
approved these changes
Nov 13, 2017
ghost
|
@lgierth are we able to create shared branch and a PR from it so that multiple people can work on this spec document? or should I just fork the repo and create a PR from my fork? Edit: I'll just continue in https://github.com/lidel/specs/tree/dweb-addressing Edit 2: See ipfs-inactive/docs#91 (comment) |
This pull request was closed.
# for free
to join this conversation on GitHub.
Already have an account?
# 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 a table of contents and intro for the addressing spec. (Some of this can surely be pulled out into a blog post or so later on.)
Please take a look and give some early feedback, I have a bunch more which isn't as coherent yet. A simple LGTM is sufficient too :)
cc @diasdavid @lidel @kyledrake @Stebalien @whyrusleeping @Kubuxu @flyingzumwalt