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

Contribute to the suborigin spec? #13

Closed
flyingzumwalt opened this issue Feb 7, 2017 · 0 comments
Closed

Contribute to the suborigin spec? #13

flyingzumwalt opened this issue Feb 7, 2017 · 0 comments
Labels
specs status/wontfix This will not be addressed

Comments

@flyingzumwalt
Copy link
Contributor

Background

@jbenet (2017-02-05)

Aside, I think there is a lot of power in the suborigin spec that may be constrained accidentally because people do not understand the IPFS or dweb use cases for it. IIRC, suborigin is not fully finished yet-- so maybe we need to get involved on this asap.

@Gozala (2017-02-06)

If you think sub-origins are a solution for IPFS you should definitely get involved ASAP. It’s really hard to change specs once they are in final stages.

I have actually being wondering how IPFS / IPNS would deal with sub-origin or other specs that utilize HTTP headers. I can imagine wanting to host different apps under same node that would not share same origin, domain names would not work neither would sub-origins as they require headers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
specs status/wontfix This will not be addressed
Projects
None yet
Development

No branches or pull requests

1 participant