-
Couldn't load subscription status.
- Fork 237
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upkind/missing-specsA gap in specs for things already used in the real worldA gap in specs for things already used in the real world
Description
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 as ipfs:// and ipns:// in browsers with native, verifiable handler for these schemas.
Initial Scope Idea
- Should be at https://specs.ipfs.tech/web-pathing/ (very important)
- This is not "just" writing down UnixFS pathing. Web Pathing is about defining a MVP subset of IPFS and conventions to ensure interop with the web.
- This is not only about HTTP URLs for Gateways, but will also inform behavior of native
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.
hacdiasSgtPooki and 2color
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upkind/missing-specsA gap in specs for things already used in the real worldA gap in specs for things already used in the real world