Endpoint for redirect-based navigator.registerProtocolHandler

[lidel]

ipfs:// URI support landed in Chromium:

• https://source.chromium.org/search?q=ipfs&ss=chromium
• https://www.chromestatus.com/feature/4776602869170176

For the time being registerProtocolHandler is limited to redirect-based handler, but its still exciting.

Idea: add Gateway endpoint that translates URI to IPFS content path:

https://dweb.link/ipfs/?uri=%s

HTTP GET → https://dweb.link/ipfs/?uri=ipfs%3A%2F%2Fbafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi
   → HTTP 301 → https://dweb.link/ipfs/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi

[lidel]

/ipfs/?uri= was implemented in ipfs/kubo#7802 and is already live at dweb.link
Remaining work here is to document the endpoint after go-ipfs 0.8.0 ships and switch Companion to it.

[olizilla]

Noting here as well, Firefox no longer supports calling registerProtocolHandler with ipfs as the scheme. arewedistributedyet/arewedistributedyet#23 (comment)

Nudging is occuring in bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1631446

[lidel]

Small update based on Chromium bug 64100: New Extension API: protocol_handlers and w3c/webextensions#317:

• positive signal from Safari (Get clicked registerProtocolHandler (protocol_handlers) links in background w3c/webextensions#317 (comment))
• some additional designs for Service Worker approach

[lidel]

This is now part of subdomain specs (which provides Origin per root CID):

• ?uri= https://specs.ipfs.tech/http-gateways/subdomain-gateway/#uri-request-query-parameter
• URI router https://specs.ipfs.tech/http-gateways/subdomain-gateway/#uri-router