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