-
Notifications
You must be signed in to change notification settings - Fork 232
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
Add specification for Web Pathing #432
Labels
kind/missing-specs
A gap in specs for things already used in the real world
P1
High: Likely tackled by core team if no one steps up
Comments
lidel
added
need/triage
Needs initial labeling and prioritization
kind/missing-specs
A gap in specs for things already used in the real world
labels
Aug 14, 2023
lidel
changed the title
Gateway: specification for Web Pathing
Gateway: add specification for Web Pathing
Aug 14, 2023
lidel
added
P1
High: Likely tackled by core team if no one steps up
and removed
need/triage
Needs initial labeling and prioritization
labels
Nov 12, 2023
lidel
changed the title
Gateway: add specification for Web Pathing
Add specification for Web Pathing
Nov 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/missing-specs
A gap in specs for things already used in the real world
P1
High: Likely tackled by core team if no one steps up
This is a placeholder for writing a specification on how
/ipfs
and/ipns
paths are intended to work on HTTP Gateways and other Web contexts, such asipfs://
andipns://
in browsers with native, verifiable handler for these schemas.Initial Scope Idea
ipfs://
andipns://
(e.g. Brave, ipfs-chromium), which is expected to be the same on both.Things the specs MUST cover
Moved to #453 ← please comment on the PR.
The text was updated successfully, but these errors were encountered: