-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish dweb: URI spec draft and documentation #28
Comments
I have the skeleton of a draft here: https://github.com/ipfs/specs/tree/doc/fs-paths/fs-paths Should I just make that a PR so we can discuss inline? (Sorry for my super-slow last week.) |
I wanted to propose something silly, just to make sure we can also take it into consideration:
However, while I am writing this, it is aesthetically really ugly! |
@lgierth please do make a PR. Also - how can we decide whether to stick with fs: vs dweb: ? I think dweb is more accurate/appropriate, and it also seems to be getting more traction (I hear people mention it more than fs:) |
I haven't heard dweb: anywhere before this sprint :) I don't have a strong opinion what it should be, dweb: is certainly less generic than fs:, and has less historical baggage. This is likely a matter of gathering feedback from externals and friends, who are interested in the future of the project but have less of an internal perspective. |
... and sounds less like ipFS, this potentially being more inviting to others. |
Also, when it is about "data", |
If we're all confident with dweb: that's cool :) @jbenet @diasdavid what do you think? |
I have offered a full spec on ipfs: and ipns: - short and easy to implement for everybody. Where is the spec on dweb? |
@pawal let's get the IANA registration for ipfs:// and ipns:// rolling based on ipfs/specs#152 (comment) |
@lgierth Not entirely sure what changes are needed based on the background material. Perhaps change the word multihash to hash? |
fs:
or dweb:
URI spec draft and documentation
Publish URI spec draft and documentation for
fs:
ordweb:
protocolPrerequisites: #3, #4, #6
The text was updated successfully, but these errors were encountered: