Skip to content
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

Closed
flyingzumwalt opened this issue Feb 9, 2017 · 11 comments
Closed

Publish dweb: URI spec draft and documentation #28

flyingzumwalt opened this issue Feb 9, 2017 · 11 comments
Assignees
Labels

Comments

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented Feb 9, 2017

Publish URI spec draft and documentation for fs: or dweb: protocol

Prerequisites: #3, #4, #6

@flyingzumwalt
Copy link
Contributor Author

@jbenet @nicola is it going to be possible to work on this, or any of its prerequisites, this week?

@ghost
Copy link

ghost commented Feb 20, 2017

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.)

@nicola
Copy link
Member

nicola commented Feb 20, 2017

I wanted to propose something silly, just to make sure we can also take it into consideration:

  • rename (or create a symbolic link) /ipfs to /ipfs:
  • so that we can justify ipfs://hash, without loosing the original juan's idea, assuming the dweb

However, while I am writing this, it is aesthetically really ugly!

@flyingzumwalt flyingzumwalt added the status/in-progress In progress label Feb 20, 2017
@flyingzumwalt
Copy link
Contributor Author

@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:)

@ghost
Copy link

ghost commented Feb 20, 2017

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.

@ghost
Copy link

ghost commented Feb 20, 2017

dweb: is certainly less generic than fs:, and has less historical baggage.

... and sounds less like ipFS, this potentially being more inviting to others.

@nicola
Copy link
Member

nicola commented Feb 20, 2017

Also, when it is about "data", fs might not be the best name!
fs/dweb is basically the scheme for the content addressable web (and actually a bit more)

@ghost
Copy link

ghost commented Feb 21, 2017

If we're all confident with dweb: that's cool :) @jbenet @diasdavid what do you think?

@pawal
Copy link

pawal commented Mar 3, 2017

I have offered a full spec on ipfs: and ipns: - short and easy to implement for everybody. Where is the spec on dweb?

ipfs/specs#139

@ghost
Copy link

ghost commented Mar 7, 2017

@pawal let's get the IANA registration for ipfs:// and ipns:// rolling based on ipfs/specs#152 (comment)

@pawal
Copy link

pawal commented Mar 7, 2017

@lgierth Not entirely sure what changes are needed based on the background material. Perhaps change the word multihash to hash?

@ghost ghost added status/ready Ready to be worked and removed status/in-progress In progress labels Mar 28, 2017
@ghost ghost changed the title Publish fs: or dweb: URI spec draft and documentation Publish dweb: URI spec draft and documentation Mar 28, 2017
@flyingzumwalt flyingzumwalt removed the status/ready Ready to be worked label Apr 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants